@sil3ntstorm you’re welcome!

@sil3ntstorm Yeah, Netatmo have changed the refresh token and access token mechanism.
This is the solution:

1. Disable or delete your current app with clientID, client secret, refresh token, etc. and create a new app.
2. There you’ll receive a new clientID and client secret, which you insert in config.js
3. In the section “Token Generator” you select the scope

read_station

and click on “generate token”.
4. Then you should receive a new access token and refresh token
5. Enter the new refresh token in config.js
6. And now the special “trick”: add the attribute accessToken in the module configuration, like that:

accessToken: "xxxxxxxxxxxxxx|yyyyyyyyyyyyyyyy",

Netatmo requires now a valid accessToken during authentication.

Save the config.js and restart the mirror. Everything should work now.

@GuestMirror Try this in bootconfig.txt

# Turn off PWR LED
dtparam=pwr_led_trigger=none
dtparam=pwr_led_activelow=off
 
# Turn off ACT LED
dtparam=act_led_trigger=none
dtparam=act_led_activelow=off
 
# Turn off Ethernet ACT LED
dtparam=eth_led0=4
 
# Turn off Ethernet LNK LED
dtparam=eth_led1=4

@sdetweil LOL…right, I do the same:beaming_face_with_smiling_eyes:
I tried to explain to @N6NG that the amperage the PSU delivers is not decisive for his problem, esp. for the RPi, which practically never reaches the max power spec of a PSU. It is the linearity and constancy of the voltage.
I see too many post e.g. on reddit, where people have similar problems with their 3D printers and attached RPis and unfortunatelly every time the get the advice to get a PSU with higher amps.

@N6NG : Oh, by the way…If you are using a USB extension cable, then remove it and plug the PSU directly into the RPi. Depending on the quality of the extension cable (which is commonly low), there might be a voltage drop of due to the resistance of the cable, which results in lower input voltage on the RPi.

@sdetweil Yeah, I see… When I setup calendar quite some time ago I remember that I had some trouble, too.
What I did -I cant’t remember why because it is undocumented- was to change
from

timeFormat: "absolute",

to

timeFormat: "HH:mm",

That is a shot in the dark, but might help, too.

@outlying Just for assurance:
The calendar URLs you’re posting are the real ones or just abbreviated for privacy here?

@Jack_Gregorski Are you using a free or premium account? The free account will not work. See https://github.com/skuethe/MMM-Spotify#restrictions

@N6NG The key is to have a power supply which provides constantly and reliably the specified VOLTAGE. Thus, the warning states “Low Voltage”. The amperage, which the power supply can provide is of secondary interest.
The PSU can deliver a much higher amperage than the 2.5A, but that doesn’t mean that the RPi will also draw them. This is the maximum amperage that the PSU could deliver. The RPi draws only as much current (amperage) as currently need (depending on attached USB devices, read/write cycles to SD card, processor loads, Wifi usage, etc.), while voltage remains constant. So, the power and amperage drawn from the PSU varies lineraly over time (at constant voltage).

For example:
Power = voltage x amperage, also known as P=U x I
The maximum deliverable power for the RPi is: 5V x 2.5A = 12.5W.
But as said before, the RPi doesn’t consume that much power. Usually it hovers something around 1W - 3W, depending on usage (or calculated in amperage 0.2A - 0.6A).

That said, amperage is sufficiently provided by the PSU, what you want is constant voltage at minimum 5V. Higher amperage will not solve the problem. You could also try to find a PSU which provides 5.1V or 5.2V for the RPi. That small increase in voltage can be handled easily by the RPi. A search on Amazon might be successful.

EDIT: And stay away from mobile phone chargers connected to the RPi with a USB cable. That will hardly work reliably.

@bhepler Your update for OpenWeatherForecast works with me! Thanks for your effort!

@sdetweil I updated with your script and had no issues at all. Everything is fine.

@sdetweil Yeah, I totally agree with that.
But it really depends on the modules. Thus, some sort of endurance test might be useful before shipping the mirror.

@sifuhall I’d second @sdetweil’s recommendation. If it works, it works. But I still would prepare some kind of remote access, just in case.
What I would add, too, is a cronjob that reboots the mirror once a day at night. Depending on number and sort of modules, you might get into RAM issues or crashes, which decreases the user experience.

That’s a really great build! Congrats!
I like the (physical) mail notification and pickup idea very much. So please keep us in the loop with how it works out,

@z0ki I got mine from here https://www.brigla-shop.de/

@jerryp Thanks so much! That solved my issue, too!

@hp246 hatte ich oben schon verlinkt, aber gern hier nochmal https://forum.magicmirror.builders/topic/15893/pir-sensor-not-detecting-2nd-motion-mm-stays-dark/5

@cheapdad Great build! Sounds like it won’t be your last mirror

@carstend Yeah, was just noted, too, about the update.
Some how I ran ino a problem when applying ‘git pull’, so I had to reinstall the module.
First the screen remained black. so I hat to install manually the ‘request’ library manually (see https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later). Now it works!

@jagsi I use MMM-Bring https://github.com/werthdavid/MMM-Bring
Have no problems with it

@karsten13 You are a genius! That worked for me, too! Thanks so much!