@sean Look I am using many modules and hard refreshing with zero problems.
Tell me what your module is and what it is supposed to do under a hard refresh and what error it will cause.
I already know the answer none, but hey will test it and see.

Every module I install on config change auto restarts the server which takes seconds. The connection between browser and server is broken.
Browser waits for server to say hey port 8080 is ready then browser hard refreshes.
It takes 10 - 20 seconds 10 for server and the browser still holds the last screen then on ready hard refresh, browser dumps its cache and its the same as first time connection to the site.
Yes you can hard refresh and its vastly quicker than killing a browser for absolutely no apparent reason apart some misunderstanding of actual use.
Its vastly faster than killing and reloading the browser and its seemless without any horrid white screens oh awe snap or whatever it says.
Install my guide on a Pi and watch it do as I am trying to say.

https://github.com/StuartIanNaylor/MagicMirror-Install-Guide-Raspberry-0-to-3

@sean Your Module is being restarted as the server is reset.
If your module causes problems with hard refreshes then its non compatible with any browser as when a browser cache is cleared its cleared.
If refreshing after that causes problems then its bad programming with your module.
Its doesn’t cause problems with a hard refresh though as the cache is cleared, there is no dom as it starts a fresh and the page its pulled in as if the browser had just been started.

Do you understand the difference between a hard refresh and soft refresh?
Name your module and I will tell you if its causes problems when hard refreshed?

guess you could just add it in the code header.style.background = “gray”; just have it before the wrapper code and set it there.
But think you can just add a style class in config.js

@sdetweil Seems a bit of a over kill when node restart and browser hard refresh is a matter of seconds and does exactly the same. Who wants this constantly full restart thing on the wall, on the pie zero on server restart I get no white screen at all stays as back ground and maybe 10 secs to fill again with content so for Pi2/3 you could blink and miss it.

I will prob have some further system log monitor actions but the pi watchdog will force a restart if seizes.

Cron is a really bad way to do it as it quite simple to get a notification exactly when its ready and also not just do it on a time loop when its not so you end up with the horrid white chromium refresh screen.

Tail and log monitoring is where linux excels.

( tail -f -n0 ~/.pm2/logs/MagicMirror-out.log & ) | grep -q 'Ready to go! Please point your browser to:'
sh xdotool.sh

Thats it job done.

PM2 only tests that MagicMirror is loaded and running as ‘Ready to go! Please point your browser to:’ comes on my lowly zero quite a bit after PM2 says MagicMirror is running.

Also as I say with when the browser and server (Magic Mirror) become disconnected they stay that way with Pi0/1 Electron will launch again but actually its not necessary as all that is needed is a hard refresh.

You can test this on a Pi2/3 with the setup I did for zero but it will work for 2/3 and also uses Stretch lite which has always confused me why the relatively pointless desktop load is used for a mirror.
Just change three lines and use chromium instead if you follow https://github.com/StuartIanNaylor/MagicMirror-Install-Guide-Raspberry-0-to-3

Really electron / server should be 2 PM2 processes as this would work more seamlessly as its an assumption but electron is just Chromium in a java wrapper with the selenium webdrivers so expecting it takes time to reload after being killed and likely that it wasn’t really required.
When this Banana stops twisting my melon as if I can not get I2C running on it then its destined for the bin, but if I do I will have look if I am wrong about the speed of killing electron each timeinstead of just doing a hard refresh.
As of course you can do a refresh as long as its a hard refresh ctrl+F5 and not ctrl+r or F5.
https://www.getfilecloud.com/blog/2015/03/tech-tip-how-to-do-hard-refresh-in-browsers/#.XHcXXIj7SUk

Guess it depends on what Pi you have, as can not say for 2/3 installs with electron.

I have refresh (ctrl+F5) auto from detecting the ‘Ready to go! Please point your browser to:’ of PM2 so on config change as soon as MagicMirror is ready Chromium does a refresh.
I also have a chromium log script to catch errors and provide the same but since the introduction to MagicMirror I seem to have an obsession with tinkering with it.
So if i manage to get a mirror up and running for several days I guess I could capture those errors and just do a refresh only on disconnection or error.
But noticed when I was putting together various modules that F5 refresh would sort of jam up after a while but ctrl+F5 doesn’t and is always like a clean start without having to reload the browser.

Haven’t tried P2/3 yet have one on my desk so will have to give electron a go.
All I know is that with chromium the server & browser become not connected and watchdog only restarts the server whilst the browser just sits as it was.
Its why I did the simple monitor scripts as now on a restart or config change Chromium & Server are always in sync.

So it might be the Pi version with no official support for Pi0/1 which I think is a shame as with the monitor scripts I have it seems to work great, so wondering why.
I am sort of having a short love affair with the form factor and price of the Zero and on a relatively low load project like this it works quite well.
In fact I am lying about the Pi2/3 as actually its a banana Pi zero same format practically no support but armv7.
Its on my desk because I2C has me completely scratching my head and the banana is twisting my melon.
Love the form factor though and why I think you should support as the Zero is cool and cheap.

I do agree that the modules should work and it should be that way round, but from short outages to plethora of problems I can not see why you shouldn’t refresh?
Guess its just not the supported way but not sure what the problem is with refresh as long as you do a hard refresh not a soft one.
https://www.getfilecloud.com/blog/2015/03/tech-tip-how-to-do-hard-refresh-in-browsers/#.XHcXXIj7SUk

Not sure about ctrl+r as think that is just refresh, if you do a ctrl+F5 it does a refresh that ignores cache so its pulled as if a new browser launch.

I have loaded and ctrl+F5 seems to work for me.
Dunno have a look at https://forum.magicmirror.builders/topic/9805/magicmirror-screen-goes-black/11

As just finished a bit of a write up on a guide that might help

https://github.com/StuartIanNaylor/MagicMirror-Install-Guide-Raspberry-0-to-3/tree/master/Magic Monitor

PS .
Add this into your css/custom.css

#NEWS .articleImage {
    filter: grayscale(100%);
}

Top tip from eouia

I gave you some bum steers on export XAUTHORITY=~/.Xauthority but prob was when I was using lightdm but for it to work omit that line.

I have 2 monitors running well 1 really as the Chromium one isn’t really doing anything as all is working fine.

xdotool.sh ended up just being

if [ -z "$DISPLAY" ]; then #If not set DISPLAY is SSH remote or tty
	export DISPLAY=:0 # Set by default display
fi
xdotool search --onlyvisible --class "chromium" key ctrl+F5  -v 2>&1 | logger &

chrome-log.sh is just

#Grep is a bit confusing as \| ie OR not AND so you get the following of Or + inline there is the other string
#grep -q '8080\|ERROR' would return true if either exist (OR)
( tail -f -n0 ~/.config/chromium/chrome_debug.log & ) | grep -q '8080.*ERROR\|ERROR.*8080'
sh xdotool.sh

Main one for me is the PM2 one that waits for MagicMirror to say all is finished and point your browser

( tail -f -n0 ~/.pm2/logs/MagicMirror-out.log & ) | grep -q 'Ready to go! Please point your browser to:'
sh xdotool.sh

Better explanation can be found on https://github.com/StuartIanNaylor/MagicMirror-Install-Guide-Raspberry-0-to-3/tree/master/Magic Monitor

@dæmoneyes Yeah I think they have different uses. I was actually wondering if with an old sumsung PC monitor that I was actually going to keep the case after appling the film and rehouse as a table mirror.
I guess there are different qualities of film and don’t forget to get external mirror film than the internal stuff where the adhesive and mirror are the wrong way round.

Just a 22" stand was pretty nice and the cost would of been a Pi-Zero W + Buck convertor + £10 Film and some bits and bats but yeah it would of been ok.
Pi was just going to get epoxied onto the back via some 10mm plastic standoffs.

Replied again cursed by that akismi bot troll thing.

PS still setting it up but just monitor your logs.

Create a shell script with something like

 tail -fn0 logfile | \
while read line ; do
        echo "$line" | grep "pattern"
        if [ $? = 0 ]
        then
                ... do something ...
        fi
done

Maybe with a --retry to the tail command, or use -F instead of -f

Tack it onto your electron log and do the above xdotool.

MMM-Pages I guess just change the page for on / off