Module(s) causing MagicMirror to lock up?

brandongomez

Hi all. Newbie here and have built a MagicMirror with some really cool modules. However, I believe one or more of them is causing the mirror to lock up after around 4-5 hours. Is there a log where I can see where it might be happening?

I have the following modules installed:
default clock
default calendar
MMM-Instagram
MMM-MyCommute
MMM-pihole-stats
MMM-ping
MMM-Sonos
MMM-WunderGround
netatmo
iFrame

At first I thought it was something wrong with my Raspberry Pi 3 but that’s not the case. Then I thought turning off the display, coming back later and turning it on again was causing the Pi to halt or sleep, something like that but that doesn’t seem to be the case either. When I run my modified config.js file, it will run for around 4-5 hours and then the screen will freeze. I will be able to ping the IP but will not be able to ssh into it.

I have put the sample config.js file back on and it’s been running with no issues so I can only guess that a module is causing it to eventually lock up. Maybe something with API calls? Or is there a max number of modules you can have?

Really appreciate any help anyone can give. Thanks!

Chiumanfu

Comment out all the third party modules in the config.js then add them back one by one testing each. For me it was the iFrame module displaying an IP camera stream that locked up my pi.

brandongomez

Thanks for the tip! Interesting. I have two iFrame modules displaying and I thought that was the one module that wouldn’t be causing an issue.

Chiumanfu

@brandongomez I think in my case, it was a bad IP Camera stream rather than a bad module.

brandongomez

After removing some of the modules, it looks like my Pi-hole stats module was causing the problem. MagicMirror has been running fine for 24 hrs with that module commented out.

qu1que

I have the same problem with pi-hole-stats module. I’ve installed it on a raspberry pi zero mirror and on another raspberry pi3B mirror. And in both cases, the same problem. The screen turns black after a few hours working. The solution was the same: comment out the pi-hole-stats module. I don’t know why this happens