It’s been 24 hours and still working fine! Thanks!

@sdetweil just got the update, I’ll let you know what I find. Thanks!

Based upon the display, it stopped on me last night. I was running mm serveronly so I could see the dev output in browser. I couldn’t find any errors. It could have stopped when scheduler is set to hide all modules. I did see this in the console after this mornings schedule to show modules:

Whoops! There was an uncaught exception...
TypeError: Cannot read property 'statusCode' of undefined
    at Request._callback (/home/pi/MagicMirror/modules/mmm-nest-status/node_helper.js:20:25)
    at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:881:8)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?

In the past I don’t think I ever had a conflict between scheduler and nest status.

I tried to open the console via remote but wasn’t able to. Sorry.

Bummer, mine has stopped as well.

I also have been having the same issue with this module. It worked well for months. I’ve just been restarting and haven’t had time to chase down the errors.

I have 2nd gen echo’s

That changed worked for me. I also had issue of white screen on my phone. After the change above and restarting phone, works fine now.

@jrotondo I’m using AlexaOnOff which allows me some control over MM.

Here is the thread.

I’ve noticed recently that the new weather module in the develop branch stops updating. I got this error in the developer console:

2cors-anywhere.herokuapp.com/https://api.darksky.net/forecast/mykey/mylatlong?units=us&lang=en Failed to load resource: the server responded with a status of 503 (Service Unavailable)
0.0.0.0/:1 Failed to load https://cors-anywhere.herokuapp.com/https://api.darksky.net/forecast/mykey/mylatlong?units=us&lang=en: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://0.0.0.0:8080' is therefore not allowed access. The response had HTTP status code 503.

If the service is unavailable shouldn’t the weather module update once it is available?

If I restart MM, the module will update properly and work for about a day.