Read the statement by Michael Teeuw here.
mmm-nest-status unresponsive after 12hours
-
@michael5r after 12 or so hours the nest module fails to update the status of the thermostat instead just displaying what was it’s state at the time of going unresponsive have you had this issue/problem?
-
@dazza120 are there any errors in the terminal window or developers window console?
-
@sdetweil Unsure mate I’ve changed the update intervals so i’ll see how that works first, Ive never been able to get on that dev console with buster its just white when you get into it and says it needs to reload then does nothing
-
@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
-
@sdetweil can you offer any help on how to track down the problem with this be unresponsive after awhile
-
@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! -
@sdetweil cheers mate I’ll wait till your all good
-
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 …
-
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 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
thengit 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.’;