I’m not exactly sure what that means 
I will think about adding some sort of indicator that shows that the change to auto but is still in the last mode.
I meant to say, technically it’s not a bug, it’s the way Nest defines Auto Away.
2 Likes
what an excellent release! thanks very much for finally adding the Nest support we were hoping for.
1 Like
The best part of this release is the built in polling so your Activity feed isn’t clogged anymore by Pollster 
1 Like
I doubled checked and this should not happen. Did anyone else get alerts from protects on install?
Can you double check the device settings, under edit device and make sure testing mode is blank?
No, but when setting up my Protects awhile ago with other device type’s I did experience this which lead to the wife texting me asking if I was up to date on my life insurance policy payments.
1 Like
I will review initialization of protects today to see if there might be a wonky first state.
Technically it is auto, it has a cool and heat set points. I thought it was weird at first, but it does make sense.
1 Like
I just fixed a bunch of bugs that were missed with the temp button tiles. They work great now. I decided to try and fix this confusion with auto and away.
There is not much that I can do to eliminate this confusion. In order to stay compatible with ST thermostat standards I’m only limited to (heat, cool, auto, off) as ‘thermostatMode’ values.
I will provide a preference toggle in the app that will prevent this from changing the mode to auto on away. The only side effect is that it will not allow Low/High temp adjustments while the location is ‘Away’
yes it is blank. Not that I could have gotten to it at the time it all went off, as I had just clicked done on the initial configuration.
Hmmmm, what made me different? I did not remove the others first, could that be it?
I think that makes sense. Most people won’t want to make changes when the location is in away mode anyway. I just logged into my IDE and noticed you didn’t commit to Github yet?
No, I didn’t remove my others either and didn’t experience this.
Not yet. Within the next 15 minutes it will be up.
When I do update. I will post here.
Also if you enable notifications in the App it will check every 30 minutes for a new version and send a notification with whatever the new updates are for.
trying it now… looks nice…
Just making sure there was not some weird on initial install it was set to a test mode.
Has everything been running smooth since?
I am re-working the preferences slightly. My best guess is that during initial setup something was defaulted to and caused this.
Since then everything has seemed fine. Not been home to check more.
1 Like
##Please update App and All Device Handlers
[Updated]: Manager App v1.0.0
- Updated: Bumped to v1.0.0
- Fixed: Issue #9 (API Info Duplicates in the SmartApp)
- Fixed: Added Device preference setting in App to disable switching thermostat mode to Auto when the location is Away
[Updated]: Thermostat v1.0.0
- Updated: Bumped to v1.0.0
- Updated: Code Optimization
- Fixed: Issue #8 (Setpoint not changing for Auto)
- Fixed: Heat/Cool Temp control tile did not work when in auto.
- Fixed: Issue #10 (Added Device preference setting in App to disable switching thermostat mode to Auto when the location is Away)
[Updated]: Presence v1.0.0
- Updated: Bumped to v1.0.0
[Updated]: Protect v1.0.0
- Updated: Bumped to v1.0.0
- Fixed (Maybe): @desertblade made some changes to hopefully prevent false alarms on install.
1 Like
I cannot adjust the temp from within the DH or via Keep Me Kozy I am getting these errors in the Nest Manager in IDE
Awesome!! You guys are awesome for building this! Thanks.
PS I was able to update without false alarms.
