[REMOVED] Nest Manager

[tonesto7 (Anthony S.)]

Wow we just hit 100 Installs!

[Benji]

Once the platform stability resides, I’m jumping in! Currently when I set ST to ‘away’ I just set the temps to 51 degrees and 85 degrees so it will never come on, because the other SmartApp I tried to use to sync the ST status to the Nest status was quite unreliable.

You’re ENTIRE SmartApp looks solid!

[penguin22 (David Evans)]

I suspect the 1000 will be surpassed sooner than you might imagine. This is a really awesome functionality you have added. Out of curiosity, have you loaded the client on Windows Phone? Wondering if you see the same large icons.

[tonesto7 (Anthony S.)]

Thanks…

@penguin22

Out of curiosity, have you loaded the client on Windows Phone? Wondering if you see the same large icons.

I haven’t yet. It’s the same way for android. I’ve added a toggle under app preferences to disable them in the app if you like.

[penguin22 (David Evans)]

I see the option, but funny enough, it appears that the toggle is off screen to the right and cannot be selected.

[tonesto7 (Anthony S.)]

New scheduler (Codename: Ticker) being rolled out

Hey fellow community members and developers! We’re doing it! The new scheduler (Ticker) is being rolled out to everyone as of now. We wanted to give you a quick note as to what to expect, what the new scheduler is, and what it isn’t. What is ticker? Ticker is our new scheduling architecture for SmartApps and Device Type Handlers. It has been built to be much more robust and scalable than the Cassandra scheduler we have been using for the last couple of years. We are really confident in it’s ability to improve scheduled actions on the platform. How do you know it will be more reliable? We first went back to the drawing board and really thought through this one and we are confident in the architecture. With ticker we have compensation jobs that check for any cron schedules that may have…

[Stroh (Michael Stroh)]

Installed from Github today. Looks great. Couple of things I noticed.

1. To install from Github you have to sign up for a Github account. No big deal, but spent a while trying to follow the directions and couldn’t find the settings button. Eventually signed up for a Github account (free) and was able to continue from there.

2. Got notification of smoke on all of my Nest Protects on install in the SmartThings app. There was a red “An unexpected error occurred.” message during the install but hitting done again cleared it. App is running on Nexus 6P if it matters.

3. I already had my Nest thermostat and 5 Protects installed with other device handlers. I deleted the previous Nest devices that were installed with the old device type. I have all the Nest Protects are showing up in my list of things. Nest Presence Device shows up in list of things. There is no Nest Thermostat in my list of things. I went back to the SmartApp and rechecked the Nest Thermostat and now it is showing in the list of things.

4. Nest Thermostat installed as Off. (Thermostat is idle) Toggled to Auto mode and tried to change the set point. After a minute or two went back to Off and reset back to old set point without ever coming on. This repeats with each attempt. Not able to use this at all to change the set point.

(Edit: looks like the official Nest app isn’t working either. Resetting system to see if that resolves it.)
(Edit2: Reset thermostat and now official app is working but Nest Manager thermostat is not updating or allowing changes.)
(Edit3: Changing to old device handler and no response there either. Might be a SmartThings issue not a device handler issue.)

[desertblade (Ben W)]

@Stroh

Got notification of smoke on all of my Nest Protects on install in the SmartThings app. There was a red “An unexpected error occurred.” message during the install but hitting done again cleared it. App is running on Nexus 6P if it matters.

You are the second person to report this. The majority of users don’t so I am not sure how it got in the state. It may have to due with having old and new protects overlapping. Will continue to see if we can make this better.

@Stroh

I went back to the SmartApp and rechecked the Nest Thermostat and now it is showing in the list of things.

I have had this happen a few times during testing. It started recently and I believe its ST related, not saving state correctly when going in and out of configurations.

@Stroh

Nest Thermostat installed as Off.

This was a bug last week and should be resolved. Sounds like it may not be getting data or has some cached data. Try doing a force poll (pressing play next to the smartApp). If that does not fix it, turn on debugging in the app and look at live logging to see if data is coming through.

edit: spelling

[Stroh (Michael Stroh)]

@desertblade

This was a bug last week and should be resolved. Sounds like it may not be getting data or has some cached data. Try doing a force poll (pressing play next to the smartApp). If that does not fix it, turn on debugging in the app and look at live logging to see if data is coming through.

Turned on debugging. Forced poll with the play button. Watching the live logging in the IDE shows the polling but the information returned is inaccurate. My thermostat AC set point is set to 78 and displaying a leaf. The log data shows a set point of 76 and no leaf. Button presses on the device do not show is the log. (pressing up or down on the set point shows nothing in the app or the log.)

Did you see my third edit above that it does not seem to be limited to Nest Manager. When I changed the device type to the old handler there also is no response. May be a SmartThings issue and not Nest Manager?

[desertblade (Ben W)]

Impossible, ST never has issues.

In the smartApp you can see the raw response from Nest. I am wondering if you are having connectivity issues with Nest. if you log into Nest.com what does it say you are set to?

[Stroh (Michael Stroh)]

@desertblade

if you log into Nest.com what does it say you are set to?

It is accurate. 66/78 with a leaf.

[tonesto7 (Anthony S.)]

Thanks for the detailed feedback… I apologize for the issues you are seeing.
These types of one-off issues are very hard to troubleshoot because of the inconsistencies in ST.

[Stroh (Michael Stroh)]

@tonesto7

These types of one-off issues are very hard to troubleshoot because of the inconsistencies in ST.

I’m really thinking this isn’t a Nest Manager issue. None of the methods of updating from the SmartThings side is accurate on my thermostat. The Nest app and home.nest.com are accurate so I believe the breakdown is somewhere between Nest and SmartThings.

[tpip]

@tonesto7, @desertblade thanks for this. This is what I’ve been waiting for. Only problem is it isn’t working for me.

I followed the instructions to get the Smartapp and device handlers from IDE this morning. I only have the Nest thermostat, no Protect or Presence. Within SM app, Nest is showing my house to be at 67 degrees, heat setting at 66, cool setting at 83. In the Nest app and Nest.com, it is correctly showing at 73 house temp, 69 heat setting, and 82 cool setting.

When I try to adjust the temperature settings in the SM app, it reverts back to 66 heat and 83 cool within a couple of seconds every time.

At the bottom of the app, it shows Nest last checked in at Mar 21, 2016 08:54:35. That’s when I installed the app. It shows data last received at 20:08:09, but nothing has changed in the app all day. I tried to force it to poll by clicking the play icon. Nothing happened. I even tried to delete it in order to attempt a clean reinstall, I get an error message every time.

In the IDE event log, it shows when I attempted to changed the temperature settings and the heat/cool/auto mode.

In the SM app, I just changed it to heat only mode and the temp to 72. It seems to be holding like that and says it’s heating to 72; however, the house temperature (according to the app) is 67. The heater has not kicked in. NEST.com does not show any changes to the heat/cool/auto mode or the heat setting.

Debug is on.

Thanks again for this code. It would be nice if SM things was actually more usable and user friendly.

[tonesto7 (Anthony S.)]

@tpip @Stroh
If you goto My Locations > List SmartApps > Nest Manager and review the state data labeled deviceData. That is where the api data is stored after every poll.
Are you seeing any errors in the logs at all?

[Stroh (Michael Stroh)]

@tpip

Thanks again for this code. It would be nice if SM things was actually more usable and user friendly.

I don’t think this is a Nest Manager issue. I installed a completely unrelated SmartApp called Simple Device Viewer that displays data from whatever device you configure. I configured it to show data from my Nest and there was stale data displayed just like in Nest Manager.

Changing the device handler to each of the three types I have installed, Nest, Nest V2, and the Nest Manager (Nest Thermostat) device types all display the same stale data.

[tpip]

I found some errors in the exlog section.

I have changed it cool only setting & lowered temp and both held. I put it back into auto mode and raised the heat to 76 and the cool to 86. Both are now holding; however, the heater has not kicked in and the house temp (according to app) is still 67. Nest.com shows no changes.

Edited to indicate found errors. See below post.

[Stroh (Michael Stroh)]

@tonesto7

Are you seeing any errors in the logs at all?

Is this the same information displayed in live logging? I see no errors there.

I can post the deviceData information but it is long with a Thermostat and five Protects. I can also post log data if it will help you.

[tpip]

Under exlogs, I found some errors as log type.

[{logMsg=addRemoveDevices Exception: physicalgraph.exception.ConflictException: Device still in use. Remove from any SmartApps or Dashboards, then try again, logTime=2016-03-22T01:08:25Z, logType=error}, {logMsg=revokeNestToken Exception: groovyx.net.http.HttpResponseException: Not Found, logTime=2016-03-22T01:08:28Z, logType=error}, {logMsg=addRemoveDevices Exception: physicalgraph.exception.ConflictException: Device still in use. Remove from any SmartApps or Dashboards, then try again, logTime=2016-03-22T01:08:32Z, logType=error}, {logMsg=addRemoveDevices Exception: physicalgraph.exception.ConflictException: Device still in use. Remove from any SmartApps or Dashboards, then try again, logTime=2016-03-22T01:08:37Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:32:50Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:32:54Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:33:10Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:33:22Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:33:35Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:50:20Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:50:31Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:50:58Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:51:11Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:51:14Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:51:34Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:54:09Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:57:29Z, logType=error}, {logMsg=updateChildData() for 4pba68Pk3xuG680lNWg6Xcn7UfMulpEX after polling, logTime=2016-03-22T01:57:39Z, logType=error}]

[Opieos (Bryan Blake)]

Anyone seeing issues with NEST going into OFF mode.

It seems to have happened to me twice now since install on the ST connection. Got a might bit chilly in the house last evening! Didn’t bother me per se but the wife was non too pleased with me