I have had to reset our Nest token several times now in the last 24 hours. Is anyone else having a problem with NST Manager staying connected to their Nest account?
Mines stoped responding yesterday around 6 pm. Uninstalled app and deviced and re-installed it to see if it worked and no luck. I also have a device handler from a diferent source and its also not working, so it could be from nest.
Alll my Nest Devices are working fine: cams, tstats, protects under the ST platform. No issues whatsoever…Could be Nest account related…
NEST Protect:
[f0d16f75-1506-4c8f-9df6-0569c602f28d 12:54:58: debug doRequest>done with get
[f0d16f75-1506-4c8f-9df6-0569c602f28d 12:54:58: debug getProtectInfo>done
NEST THermostat:
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug generateEvent>parsing data [thermostatMode:cool, thermostatFanMode:off, coolingSetpoint:17.5, coolingSetpointDisplay:17.5, heatingSetpoint:17.5, heatingSetpointDisplay:17.5, heatingSetpointRangeHigh:30.0, heatingSetpointRangeLow:10.0, coolingSetpointRangeHigh:30.0, coolingSetpointRangeLow:10.0], scale=C
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug refresh_thermostat>currentCoolSP=17.5,newCoolSP=17.5
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug refresh_thermostat>currentHeatSP=17.5,newHeatSP=17.5
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug refresh_thermostat>coolingSetpointRangeLow=10.0
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug refresh_thermostat>coolingSetpointRangeHigh=30.0
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug refresh_thermostat>heatingSetpointRangeLow=10.0
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug refresh_thermostat>heatingSetpointRangeHigh=30.0
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug doRequest>done with get
c957418a-b597-419b-84f7-3596bc773588 12:53:57: debug getThermostatInfo>done
NEST Cam:
3cee4165-96d1-4d75-afdd-5285c92e85cd 12:59:27: debug initializeStreamingContext>begin
[3cee4165-96d1-4d75-afdd-5285c92e85cd 12:59:26: debug snapPicture>found image
[3cee4165-96d1-4d75-afdd-5285c92e85cd 12:59:25: debug snapPicture>About to snap picture using URL https://www.dropcam.com/api/wwn.get_snapshot/CjZQNlBvREJJMnNEc3kybFJ1X3laQzFINHJiZGR3ckJ0TkZMMzZHcHQzcVBDTlJFRWNkajE5UmcSFk1meHBiMm9xbHpYV0FWTU5VTXJma0EaNnp2N3JWMHdpX0N4eHE3Wk1hb1BweTNad3dHUDY1SXhwOGtMdW1keGM2STFUblpob0RONXRiZw?auth=9464WalIvAxJjnvxm46VGvh-PkpXCKxTZsz5o9RmGEV_PCaH98uUi3nSbtUfiq_YqJjnCTyzyZyBKqRvhlsfNnT9p_hxrRsp8J5BZijUauvIxr0KZ1bUxV54sh1s0WbhMYuAJHals0Zkexqlo9YrXCWOMnY40EiDEUswMnzqWII76fRwmJR9R0c69w-roERdESAoEeqqKT1gm0
[3cee4165-96d1-4d75-afdd-5285c92e85cd 12:59:25: debug doRequest>done with get
Mine stopped working around the same time yesterday. I’ve been getting a handful of these in the logs from NST Manager:
error groovy.lang.MissingMethodException: No signature of method: physicalgraph.device.DeviceTypeExecutorBase$_closure5.doCall() is applicable for argument types: (java.lang.String, java.lang.NullPointerException) values: [generateEvent Exception:, java.lang.NullPointerException]
Possible solutions: doCall(), doCall(java.lang.Object), call(), call([Ljava.lang.Object;), call(java.lang.Object), findAll() @line 649 (processEvent)
As well as:
error java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 64656377701698 @line -1 (scheduler)
error java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 64755709903608 @line -1 (getAutoTypeLabel)
From automation.
I tried it with MyNextManager and its not recognizing my thermostat. When i get to the “select thermostat” page, my thermostat doesn’t appear. My cameras apear but not the thermostat.
The platform is having issues on schedule and runIn, over last 24 + hours.
There are threads here and in webcore of folks having platform issues, things not running, claiming to run then timing them out immediately.
Well, did you follow the installation steps? You have to use the primary Nest Account and make sure that your thermostat is under the right structure (if you have many).
Yup! I have only one account, and i have installed the app before without any issues, just today.
Something is going on…
@yvesracine
I have a question about your design…
Do you send the data to the devices as childDevice.sendEvent() or pass the object to the device like us using generateEvent method on the devices themselves?
I don’t use childDevice.sendEvent() or pass the object to the device. My child processes are not dependent on the parent (Service Manager) to get their own data… Only the (common) stucture data is managed by the Service Manager.
Totally different design from everybody…
yea we entertained that design idea about a year ago but it would require a restructure of the code base and didn’t have the ambition at the time. It’s definitely smart move when you start getting 10+ highly active child devices.
Oh well though… NST is still one of the most resilient integrations on ST
Sure, but with the timeouts happening on the platform due to rate limiting, the Service Managers with the usual design get hammered, and they fail quickly (after 20 s)…
The child processes (Device Handlers) have a larger timeout (40 s) hence the resilience…
P.S. Also, my devices don’t use any state variables to store data coming from APIs (so my code uses very few state variables which are subject to failure)…
Send me some logs… I sent you a PM on how to do it.
I still think that you should get paid for your work (as I told you before)…
The ST development platform is too sensitive for any serious open-source development!
Here are some of the errors that are showing up in the logs for one of our nest thermostats. I am also finding that logging into my online Nest account takes several attempts before it connects.
NEST THERMOSTAT
71942640-df24-4908-84c9-c72d0e7d5087 12:12:29 PM: error groovy.lang.MissingMethodException: No signature of method: physicalgraph.device.DeviceTypeExecutorBase$_closure5.doCall() is applicable for argument types: (java.lang.String, java.lang.NullPointerException) values: [generateEvent Exception:, java.lang.NullPointerException]
Possible solutions: doCall(), doCall(java.lang.Object), call(), call([Ljava.lang.Object;), call(java.lang.Object), findAll() @line 649 (processEvent)
71942640-df24-4908-84c9-c72d0e7d5087 12:12:29 PM: info fanon 0 fanauto: 43920 opidle: 43920 cool: 0 heat: 0 fanonly: 0
71942640-df24-4908-84c9-c72d0e7d5087 12:11:38 PM: debug Nest Thermostat - Upstairs (v5.4.0) | Sending changeSetpoint(Temp: 26.0)
71942640-df24-4908-84c9-c72d0e7d5087 12:11:38 PM: debug Nest Thermostat - Upstairs (v5.4.0) | UPDATED | Cool Setpoint is (26.0°C) | Original Temp: (25.5°C)
71942640-df24-4908-84c9-c72d0e7d5087 12:11:37 PM: debug Nest Thermostat - Upstairs (v5.4.0) | Sending changeSetpoint(Temp: 25.5)
71942640-df24-4908-84c9-c72d0e7d5087 12:11:37 PM: debug Nest Thermostat - Upstairs (v5.4.0) | UPDATED | Cool Setpoint is (25.5°C) | Original Temp: (25.0°C)
71942640-df24-4908-84c9-c72d0e7d5087 12:11:37 PM: debug Nest Thermostat - Upstairs (v5.4.0) | UPDATED | Pause Updates is: (true) | Original State: (false)
71942640-df24-4908-84c9-c72d0e7d5087 12:09:19 PM: error groovy.lang.MissingMethodException: No signature of method: physicalgraph.device.DeviceTypeExecutorBase$_closure5.doCall() is applicable for argument types: (java.lang.String, java.lang.NullPointerException) values: [generateEvent Exception:, java.lang.NullPointerException]
Possible solutions: doCall(), doCall(java.lang.Object), call(), call([Ljava.lang.Object;), call(java.lang.Object), findAll() @line 649 (processEvent)
71942640-df24-4908-84c9-c72d0e7d5087 12:09:19 PM: info fanon 0 fanauto: 43740 opidle: 43740 cool: 0 heat: 0 fanonly: 0
Did you run out of supporters on your own thread and now you troll others in an effort to gain a few more customers? Or you are just hungry? This is not playing nice nor helpful. If I remember correctly, you were offended when NST Manager users came over your thread…
2 Likes
If you look under my thread, @tonesto7 posted many times and the posts are still there today…
I was offended by some posts in my thread from other NST team members (one of them has since left the forum ), which were offensive for the work I’ve done for the community …
Ask @tonesto7 if he’s offended… we just exchanged about our respective design…
I do see that Firebase has been experiencing high latency issues since last night. I’m not familiar with the NST architecture and how Firebase is used - or if there is any relationship between the issues at all.
We do use firebase but only to collect anonymous exception data if the user opts-in for it.
But it was disabled as soon as I seen the platform issues start
1 Like
Hm, a quick glance shows these errors started around 9 PM Pacific when Firebase started reporting issues.
3 Likes