@SirVer
I’d see two options:

1. Disable the update notifikation by inserting

disabled: true, 

in the module config

{
module: "updatenotification",
disabled: true, 
position: "top_bar"
},

But then all update notifications will be disabled.

2. You fork the module into your own github repo, apply the changes you made, and install the module from your own repo. This might require to make also adoptions in the code for references, which point into the original repo.
   But then you will not have automatically update notifications, if the original module has been updated.

What I do is to document my changes in my private repo and to apply them if the module gets updated. That’s for me the easiest and quickest way.

I regularly apply OS updates to my RPi, which runs MM, like on all my other PCs and servers.

sudo apt update
sudo apt dist-upgrade -y

Two days ago I applied the latest Debian Stretch kernel updates which brought an unexpected surprise.
Apparently these updates contain also new configuration files for the screensaver and display control, which overwrite the current ones on the system.
A few hours after the update I went to my MM and it greeted my with the password prompt of the screensaver.
As I didn’t find the documentation anymore which options had to be changed and where, I chose the “lazy camper” route and simply installed xscreensaver.

sudo apt install xscreensaver

In xscreensaver you can not only adjust the screensaver and delay for blanking off, but you can completely disable the screensaver, what I did. Problem solved.
The display switches off as normal and switches on again when the sensor detects proximity as usual without the password prompt.

@oberfragger Congrats to your wonderful built! It’s very impressive how much effort you put into that! Wished I had knew a few years earlier about MM…that would have saved me lots of discussion with my better half about which mirror should have been installed in our new bathroom. :grinning_face_with_sweat:

@Lordy merry Christmas 🎄! We had recently a discussion about the same issue here. Maybe that helps you.

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

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,

@oli1204 There seems to be a problem with the DNS resolution. Just for curiosity… Could you try the MMM-Tankerkoenig Module? It basically does the same as MMM-Fuel.

Is the same error thrown?

BTW: The position is misspelled…it must be “bottom_left”

@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.

@MichMich that‘s excellent! Thanks so much!

@thedoorsfanatic Try to find a guide on youtube on how to disassemble a benq monitor. I just googled for “disassebmle benq monitor” and found a few videos on yt. Maybe your model is amongst them.