Read the statement by Michael Teeuw here.
mmm-nest-status unresponsive after 12hours
-
I tried to open the console via remote but wasn’t able to. Sorry.
-
@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
-
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.
-
@rts58 cool… I just pushed a change to my repo for this error…
if using my repo version, git pull to get the updated node_helper.js
-
@sdetweil just got the update, I’ll let you know what I find. Thanks!
-
@sdetweil updated! 👍🏾
-
It’s been 24 hours and still working fine! Thanks!
-
is the issue solved?How?
-
@costascontis bug in the original repo, use mine
git clone https://github.com/sdetweil/mmm-nest-status -
@sdetweil thanx mate.I use your repo ,it works fine but after a day or so i get a "Nest API Error:[object Object]