@sparkgap-code I have no Memory issues with this module. What I experienced a few times is that some modules don’t play well together and memory problems occur. I had that with MMM-Rain-Map and MMM-GoogleRoute. Each of the modules was fine alone. As soon as both were activated I ran into memory overflow. Lastly I gave up on GoogleRoute as I had no real need for it.

I’ve been a few days of and ran through my timelines and found this dispute here and on GitHub and must say I feel kind of sad and disappointed. Since the day I joint this community nearly a year ago it always felt like home. Everybody was helpful and patient, I always felt mutual respect and appreciation. Not to mention all those fantastic contributors with their modules and programming skills and those with various other knowledge they happily share. While I can understand @Bugsounet for waiting for @MichMich response quite some time and his engagement, I also see MichMich point which he laid out on GitHub. I don’t know what both have exchanged on other, private, channels but I can’t understand why such a dispute leads to such a extreme reaction. In the end it is the community that gets punished, when great modules are withdrawn and support is ceased. That’s sad!
As @Bugsounet is insistently not willing to contribute any more and to support, I have no other choice than to drop this module here and return to the old one. It is really a pitty and I do this very heavy hearted but travelers shouldn’t be halted.
I wish you all the best and great success with your own fork -I say this absolutely honestly- but still hope to see you here around again one day.

@thedoorsfanatic die Config hab ich für @kusselin erstellt und aus “Studienzwecken” für kusselin fast alle options nochmal explizit mit Kommentaren angegeben. Aber du hast natürlich recht, die defaults sind redundant.:thumbs_up_light_skin_tone:

@cowboysdude thanks, mate! Your new look is fantastic! I love the clean and structured layout where you get information at a glance. Which home automation system or sensors/actors do you use?

@earnestrichards here you find RSS feeds of the two major French newspapers.
Le Monde
https://www.lemonde.fr/actualite-medias/article/2019/08/12/les-flux-rss-du-monde-fr_5498778_3236.html

Le Figaro
https://www.lefigaro.fr/rss

Just choose the feed you’re interested in and add it to the config of newsreader module.

@kusselin said in a new problem with fhem:

yes than i can see the mirror again and i have the npm install in the fhem directory make.
but so the mirror is not show again

If the mirror is working again after deactivating the module, then remove the module from the /modules directory and re-install it from scratch.

$ sudo rm -R MMM-FHEM
$ git clone https://github.com/BenRoe/MMM-FHEM
$ cd MMM-FHEM
$ npm install

@j-e-f-f I have to thank YOU!!:folded_hands_medium_skin_tone:

@Clubjack I had recently exactly the same issue with MMM-ioBroker, where I needed 2 instances of that module running. Finally, after some research I found the solution and documented in my private Wiki. Here is the documentation I wrote. After setting up that 2nd instance you can configure each instance separately and declare it in MMM-pages.
Here we go:

Problem
In some cases you may need to run 2 or more instances of the same module in MM, e.g. for public transportation. Some MMMs can then be put into config.js just on a different position and parameterized as needed. Unfortunatelly, not all MMMs support that.
The reason is that all those instances will share the same node_helper and therefore get the same socketnotifications.

Solution
To solve this problem you can try to duplicate the MMM with a different name and call it in the config.js. There is no guarantee that it works, but worth to try.

Following steps have to be done:

1. Go to the modules folder and copy the whole module with a different name (in this example I’ll refer to MMM-ioBroker)

$ cd ~/MagicMirror/modules
$ cp -a MMM-ioBroker/ MMM-ioBroker2

2. Go to ./MMM-ioBroker2 and change the .js of the module script accordingly

$ mv MMM-ioBroker.js MMM-ioBroker2.js

3. Edit in MMM-ioBroker2.js the string to

Module.register('MMM-ioBroker2', {
…

4. In some cases it might also be necessary to change the .css file name, too, incl. any reference to the instance name in the file.

$ mv MMM-ioBroker.css MMM-ioBroker2.css

And then edit or replace all occurences of ‘MMM-ioBroker’ with ‘MMM-ioBroker2’ in MMM-ioBroker2.css.

@requiemmg Did I understand correctly that the display controller powers the Pi via its USB port? If so, I very strongly believe that this might be the source for the problem for two reasons:

1. The USB port does not provide enough power for the Pi
2. If the display controller goes in standby, then probably the power provided via its USB port might also be reduced.

I would always recommend to connect the Pi directly to a dedicated power supply, which can supply min. 2.5A.

Thats really awsome!

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