@fox this doesn’t go within the whitelist section it has to go after the comma at the end of your whitelist section.

It is its own config parameter.

address:“0.0.0.0”,

Due to a change in one of the default configuration items since the latest version came out you need to put

address:“0.0.0.0”,

As a config item (not in your whitelist… This is a new line for your config)

Note, setting to 0.0.0.0 is telling the mirror to use any interface. If you want you could replace that with your mirror’s ip address.

@d3r said in After update to Mirror to 2.1.3 - no working Whitlist:

address:“0.0.0.0”,

Thanks d3r, this was indeed the solution.

@JoeFranz I had same issue (except for me it was the calendar.js file it didnt like… this was because I had manually edited that file to apply hotfix for 24h times).

You can run a git reset --hard which will ‘fix’ the readme.md file you must have edited… a word of warning though- this will also reset your custom.css (at least it seemed to for me) so make sure you take a copy 1st.

@knubbl I noticed mine was also displaying a lot more entries than it used to since I updated to 2.1.3.

Do you have more than 1 calendar showing? I have 2 calendars so by setting the parameter to ‘5’ it shows a total of 10 now.

@Sandy2503

Me too… my old WL settings don’t work & also using a blank whitelist (which the update description says should allow all hosts) also doesn’t work.

Should the font also look different? I realise the Roboto font was ‘moved’ but should it still apply (or do I have to define it in CSS?)

@invisible.inq OK, sounds like you confirmed it does work then (sometimes certain devices need a resistor wired in series with either gnd or the input pin so just thought it may have been a factor).

Only other obvious thing I can think of is to confirm pin no in your mmm-pir-sensor config is correct… Your script uses bcm numbering pin 17 so configuration needs 17 as well.

@invisible.inq can you confirm the input changes by using “gpio read (pin no eg 22)” before & after moving in front of the sensor? Is there a chance you need a resistor wired in?

@Sean I’m not using the screen controls so that’s fair enough. I just compared the temp from MMM-Tools to that from MMM-system stats and yes you’re correct the values are wrong if I set the type to ATB. Forgive my rambling :)

@invisible.inq

I was having problems with this before (using a PIR sensor though, but shouldn’t matter so long as you use “GPIO read” to confirm the pin changes state from 0 to 1 when your sensor is triggered). My problem was that the screen saver was still active so although the monitor was switched ‘on’ the screen was still blank. I had tried various different things to disable the screen saver, but it just kept causing me problems. I solved it by using Xdotool to simulate a spacebar press after the vcgencmd was fired.

1st thing to check is that the the vcgencmd does actually make the screen go on /off (you can just type the command in to putty and confirm the screen operates correctly.

Note that that the modification I made above is now no longer required for me… for other reasons I actually started from scratch with a clean Raspian install, MM install etc. This time round it all just works correctly so the xdotool fix is no longer required.