mmm-nest-status unresponsive after 12hours

dazza120

@sdetweil seems to be working fine mate cheers 👍🏾

dazza120

@sdetweil its working a treat mate thanks

sdetweil

@dazza120 mine works, but original does not?

dazza120

@sdetweil no yours works well the original doesn’t

dazza120

@sdetweil it looks like its playing up again i had couple of days with it working on the button now its back to giving up after 12hours :(

sdetweil

@dazza120 ok. Can u look at the developers window console to see if any messages?

rts58

Bummer, mine has stopped as well.

rts58

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

dazza120

@sdetweil it’s literally just the seconds of the time I’m seeing which I might try to stop not seen any Nest process but I did restart it before this so that error has likely gone, as soon as it happens again I will dev console and check thank you

rts58

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.