mmm-nest-status unresponsive after 12hours

[dazza120]

@sdetweil yeah it still freezes after a while, when the magic mirror is restarted or reloaded it works, so I’ve setup a cron job every 12hours to reload MagicMirror

[dazza120]

@sdetweil can you offer any help on how to track down the problem with this be unresponsive after awhile

[sdetweil]

@dazza120 I need to.look at that code. I am away til tomorrow.

I have been fighting a similar crash
on one of my mirrors… Which seem to be error related. They didn’t run for 6 hours, now w no changes, been running for 5 days!

[dazza120]

@sdetweil cheers mate I’ll wait till your all good

[costascontis]

had the same problem with this module…had to restart my mm to keep it running so i gave up.Its a pity cause its so nice good looking module but after some hours it gets unresponsive …

[rts58]

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.

[sdetweil]

i think this is an api redirect issue, which the current code doesn’t cover…

please try my updated module

rename your folder to some other name
then

git clone https://github.com/sdetweil/mmm-nest-status

nothing else has changed

there is an api call limit… roughly once per minute… doesn’t say if it ever recovers from reaching the limit

looks like it might recover after 1 hour… SINCE THE LAST CALL… but the app keeps trying every 10 minutes
but you should see this on the UI…

‘The Nest API rate limit has been exceeded.
This module will try to load data again in 10 minutes.’;

[dazza120]

@sdetweil said in mmm-nest-status unresponsive after 12hours:

git clone https://github.com/sdetweil/mmm-nest-status

Yeah when I changed it to every 10seconds it showed the limit exceeded will try again in 10min so I think it does recover. But it’s never showed this when I put it to every 1min as per nest api. I’ll have a go with yours thanks very much mate.👍🏾

[sdetweil]

@dazza120 cool. I think it should enforce 1 minute minimum…

[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.

[sdetweil]

@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