Nest devices stopped updating at midnight last night (Sept 30 2018)

tracymckibben · October 1, 2018, 2:19pm

I have a Nest Gen2 thermostat and two Nest Protects connected to a ST V2 hub, running a variety of Webcore pistons. I noticed this morning that all three Nest devices seem to have stopped talking to ST at midnight last night. The “lastconnection” time shown for all three devices in the IDE are “Sun Sep 30 11:59:37 CDT 2018”, give or take a couple of seconds.

This smells strongly of “something” expiring at midnight, but what? I’m using a personal Nest developer account for the oAuth for my Nest devices, and everything in my developer dashboard seems to show all is well. There are no errors in ST that I can find, just nothing is updating from my Nest devices.

Help?

JDRoberts · October 1, 2018, 2:18pm

I’m sure that’s very frustrating. Since there’s no direct or official integration with nest, you can’t have those devices connected to your hub. You have to be using some kind of custom code to create a cloud to cloud integration.

So the first question is exactly which code are you using? Then you should probably check in the author’s thread for that code to see if other people are having the same problem.

Or is this something that you wrote for yourself?

sidjohn1 · October 1, 2018, 3:11pm

Looks to be a localized issue…

This is the code I’m using:

[RELEASE] NST Manager v5.0 Community Created SmartApps

#(The SmartApp Formerly Known as Nest Manager) We are very excited and proud of this this release. While it may not look like a giant update but this is the 'GREATEST NST Manager YET!!! PLEASE READ THE UPDATE NOTICE BELOW… Please open issues on GitHub for ANY issues you find because it’s very hard to track them using the forum. NST Manager SmartApp This is the SmartThings user-created SmartApp and Device handlers to integration Nest devices with SmartThings. The SmartApp and Device Handlers work together to provide integration to the SmartThings ecosystem using Nest’s published API. What’s New New: Name Changed to NST Manager New: Manager and Automations codebase has been split into two individual files. * There is an automated process to migrate your existing automation to this…

yvesracine · October 1, 2018, 4:57pm

There is a resilient alternative for your Nest devices.

[RELEASE] Resilient My Next Manager & My Next Devices for your Nest® products with native UI (for faster rendering on Android/iOS) & all ST standard capabilities + high refresh rates + No complicated developer account setup! Community Created Device Types

I’m happy to announce a new alternative for ST users who have Nest products at home. This new alternative leverages the standard ST UI (for faster rendering on both Android & iOS) & all ST standard capabilities plus new features from the Nest APIs for better synergy between the 2 ecosystems (ex. setETA for geofencing and comfort & energy saving tips with the NestGetTips smartapp and voice commands). With my code, there is no need to create a Nest Developer account and set up different permissions as Nest has authorized MyNextManager app for many users. This simplifies the Nest Setup process a lot for the end users and avoid subsequent errors/exceptions in operations. The code has been designed to work with an ecosystem of smartapps acting as “micro services”. The design is NOT a big m…

tracymckibben · October 1, 2018, 4:55pm

Apologies, I forgot this wasn’t supported integration. The issue was with NST Manager 5.0, and has been resolved.