Did anyone find a solution? I have the same problem. When I remove the MMM-GoogleMapsTraffic from the config.js the issue presists. First it is displaying “undefind” and then nothing at all.
P.S.: I reverted to the previous version of mvgmunich (sd card backup) which works again, but it has some dupicate stations entries. But this issues was from the beginning.
@thedoorsfanatic
That is a workaround for now. I wondering if this is a sole module issue or a config issue/problem with the MM or OS itself. Sooner or later we need update mvgmunich module though.
I am on the latest MM version, but something screwed up in the background.
I did load the backup with MM 2.16 and started over again. No success.
Eventually I loaded my oldest available backup with MM 2.9. Interestingly, all modules still worked in this old setup incl. MMM Fuel. From there I updated the MM to 2.17.1 and surprisingly MMM Fuel kept working. 
Apart from the fuel module 3 other module seem to be incompatible with latest MM version resulting in a black screen on startup. Most likely some required dependencies got removed in the MM core.
It would be great if we could introduce a community maintained compatiblity list of all 3rd party modules. I mean the status “maintained” or not gives a hint, but it does not necessarily mean it will not work any longer.
For now, I am happy.
tankerkoenig I am using from the beginning. In Germany there is no other API I could you I suppose.
I did update to latest MM version 2.17.1, but the MMM-Fuel just says loading (laden). My config hasn’t changed since months.
Any idea?
Thx, after fixing this the next lib is missing. I just give up using that module.
I have a vision for the future MM development. All modules should run in a separate container/sandbox or capasulated/isolated somehow. So when they fail for whatever reason, the MM stays alive and reporting a specific error message.
Don’t get me wrong I highly appreciate the work/effort of michmich and his team.
I screwed up my MM entirely. pm2 crashed randomly for an unkown reason.
When did “npm intall” on all modules after the update to 2.16, mostly npm complaints about some vulnerabilites. So I did “npm audit fix” on all them all. Maybe some dependencies broke rather than being fixed.
Another thing; npm complaint that 2.16 is uncompatible with node 10.x and npm version. So upgraded both to the latest one.
Mostly like all that ruined my MM.
Thus, I loaded back last working backup and just did “npm install” on all modules. Npm is still complaints about the node version, but all module run except MMM-MyCalender which seems to be uncompatible with 2.16.
made it with npm install -g npm@6.14.14.
I still have issues with the default wheater module. The old “currentweather” module works but new default “weather” module just says “loading”.
I got electron installed again with specifying a version (sudo npm install electron@6.1.12). No idea, why electron disappeared in the first place.
The MMM-MyCalender has indeed an issue with 2.16. causing a black screen. And MMM-Fuel is saying “undefined” for an unknown reason. Both modules are disabled for now.
My MM boots and shows the all other modules again.
With each MM update something crashes, mostly one of the 3rd party modules because one or more dependencies are lost/changed or deleted.
Thanks for your help. Great community!
I tried it again. Now the electron does not even start.
> magicmirror@2.16.0 start
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
sh: 1: ./node_modules/.bin/electron: not found
I tried to re-install electron with "sudo npm install electron@latest
", but no change.
Solved for now
I did:
sudo git fetch --all
sudo git reset --hard origin/master
sudo git pull origin master
My system is still very fragile. When do npm install after that, the screen turn black after reboot.