Read the statement by Michael Teeuw here.
Mirror turning black after a while
-
@retroflex probably we need some code to clear the ram periodically. I think my problem module is the MMM-Globe. But I will have to test it. (about 10 modules… So one module per day… Uff that’s a looooong way.
-
make two or three per day ;)
than it goes faster
-
Maybe this can be the cause?
-
@cruunnerr
I’m working 🙄 didn’t test anything yet 😅 -
@retroflex I also got the same issue. MMM-resrobot or something it depends on looks to be causing this. Has anyone found a workaround? Resrobot is one of the main reasons I have the mirror so not really happy about disableing it.
-
@Alvinger Do you know what could be the problem with ResRobot here?
-
@retroflex I can’t think of anythong off hand.
I am running an older version of MM myself so haven’t researched the electron issues.
Can anyone confirm that the issue started with the new MM version?As I am running my magic mirror on an original Pi 1 with 256MB RAM with no issues whatsoever I am a bit surprised that the module should cause this.
Edit: MMM-ResRobot has but one dependency and that is the unirest module.
Which version of ResRobot are you running? I did a rewrite to reduce the number of updates w while ago.
-
@alvinger In my case, the problem started after last MM update.
-
@cyberdie said in Mirror turning black after a while:
@alvinger In my case, the problem started after last MM update.
Same here. Running the latest ResRobot.
But I think others have reported the same problem but with a different module.
-
@binog @FredJ @cyberdie @schlachtkreuzer6
Looking through the unirest dependencies it looks like it relies on express which may or may not make it sus eptible to the issues with electron.
To resolve this I replaced unirest with node-fetch and pushed the new version of MMM-ResRobot to github.
To upgrade cd to your MagicMirror directory and run the following commands:
git pull npm remove unirest npm installPlease post results in this thread!
Hope this resolves the issue.
