If you have lost your auth tokens from Nest and/or migrated to a Google Account, and your ST-Nest integration is not working anymore, then the new versions of MyNextManager(V2.6.3), MyNextTstatV2 (v2.4), MyNextAlarmV2 (v2.4.2) and MyNextSensorV2 (v2.1.6) may be for you.
The Nest protects and Nest Tstats can now detect motion. If you want to use that feature, I’d recommend changing the polling interval to 1 minute in MyNextManagerV2 for faster updates.
For the Nest Tstat, you’d need to activate motion detection. Make sure you have the latest firmware version for all your devices.
You can also use the motion capability in your WebCore scenarios.
If you are already a contributor, you just need to use the original sellfy download link to get the new minor versions. The zip file contains all the required files for update and some release notes.
MyNextManagerV2.6.3: added the fan_duty_end_time attribute for tstats
MyNextTstatV2.4: added setThermostatFanSchedule command based on fan_duty_start_time and fan_duty_end_time attributes, corrected fanActive() method. You can then specify a start & end time in hours (ex. 15-18) for scheduling the fan every day.
MyNextAlarmV2.4.2: added some protect attributes related to homelink and night hight
MyNextSensorV2.1.6: added some minor attributes
_MyNextManagerV2 (service manager for My Next devices) now uses the Nest Web APis (not the “official” APIs as they have ended since August 31, 2019). The Web APIs don’t have the strict rate limiting as the old APIs and they are as responsive as the native Nest application.
_ MyNextTstatV2 now natively supports the following commands:
setHotWaterBoost: in the device UI and as a command for WebCore users. This is useful for Nest users in Europe.
setTargetHumidity: to set a target humidity level (for the control of your humidifier/dehumidifier connected to Nest)
For the full list of attributes, capabilities & commands supported,refer to the ST community wiki:
If you have lost your auth tokens from Nest and/or migrated to a Google Account, and your ST-Nest integration is not working anymore, then the new versions of MyNextManager(V2.6.5), MyNextTstatV2 (v2.4.1), MyNextAlarmV2 (v2.4.3) and MyNextSensorV2 (v2.1.6) may be for you.
The Nest protects and Nest Tstats can now detect motion. If you want to use that feature, I’d recommend changing the polling interval to 1 minute in MyNextManagerV2 for faster updates.
For the Nest Tstat, you’d need to activate motion detection. Make sure you have the latest firmware version for all your devices.
You can also use the motion capability in your WebCore scenarios.
If you are already a contributor, you just need to use the original sellfy download link to get the new minor versions. The zip file contains all the required files for update and some release notes.
MyNextManagerV2.6.5: added hvac_fan_state attribute in tstats, changed cache parameter
MyNextTstatV2.4.1: corrected fanActive() method to use hvac_fan_state
MyNextAlarmV2.4.3: corrected is_online attribute
_MyNextManagerV2 (service manager for My Next devices) now uses the Nest Web APis (not the “official” APIs as they have ended since August 31, 2019). The Web APIs don’t have the strict rate limiting as the old APIs and they are as responsive as the native Nest application.
_ MyNextTstatV2 now natively supports the following commands:
setHotWaterBoost: in the device UI and as a command for WebCore users. This is useful for Nest users in Europe.
setTargetHumidity: to set a target humidity level (for the control of your humidifier/dehumidifier connected to Nest)
For the full list of attributes, capabilities & commands supported,refer to the ST community wiki:
Hi, migrated Google account for Nest thermostat here. I have gone through the steps a few times and have not been able to expose my thermostat to SmartThings. On the most recent attempt, I get an error message stating “MyNextManagerV2>login>error=[detail:No active session found., error:USER_LOGGED_OUT], your home.nest.com session is no longer active, need to get new issue_token_url & cookie from Google account login, exiting…”
I did not logout of my Chrome incognito home.nest.com session, so I’m not sure why it’s no longer active.
Just went through all of it, again logged into home.nest.com with using Chrome incognito tab. I split up the cookie evenly, which appeared to be successful on the smartthings website. However, I am getting the same error message stating no active session found. I am looking at my incognito session right now, which is logged in.
Trying to setup NestChangeMode. It can put my Nest into Eco but it cannot end Eco.
Also is there a way to do Away/Eco so that my whole Nest account goes into away mode. I have notifications setup on my cameras that only trigger if I am away.
Hi, I made some minor changes to NestChangeMode so that it triggers the Nest’s Away mode, which will enable the eco mode at the tstat as well. BTW, you can also call the away() and present() methods in the DTH via Webcore according to your own custom rules. Those 2 methods, which affect the whole structure, were recently added hence the reason for the change to NestChangeMode.
Now, to end the eco mode at the tstat, you need to create another instance of the NestChangeMode for the Home ST hello mode. Each instance must be dedicated to a single Nest structure’s change.
For this use case, and many other automation use cases, you may want to contribute to the ScheduleTstatZones at my store, which is based on the concepts of rooms/zones/schedules.
Updated to your new NestChangeMode 1.2 code and now neither away or home works. I understand making one instance for away and one instance for home; that is logical. I can see the two instances trying to do things in the logs but it looks like the commands are never sent to Nest.
If you have lost your auth tokens from Nest and/or migrated to a Google Account, and your ST-Nest integration is not working anymore, then the new versions of MyNextManager(V2.6.6), MyNextTstatV2 (v2.4.2), MyNextAlarmV2 (v2.4.4) and MyNextSensorV2 (v2.1.6) may be for you.
The Nest protects and Nest Tstats can now detect motion. If you want to use that feature, I’d recommend changing the polling interval to 1 minute in MyNextManagerV2 for faster updates.
For the Nest Tstat, you’d need to activate motion detection. Make sure you have the latest firmware version for all your devices.
You can also use the motion capability in your WebCore scenarios.
If you are already a contributor, you just need to use the original sellfy download link to get the new minor versions. The zip file contains all the required files for update and some release notes.
MyNextManagerV2.6.6: minor change to avoid null values in cookie
MyNextTstatV2.4.2: corrected away() and present() methods to properly set the Nest structure
MyNextAlarmV2.4.4: corrected away() and present() methods to properly set the Nest structure
_MyNextManagerV2 (service manager for My Next devices) now uses the Nest Web APis (not the “official” APIs as they have ended since August 31, 2019). The Web APIs don’t have the strict rate limiting as the old APIs and they are as responsive as the native Nest application.
_ MyNextTstatV2 now natively supports the following commands:
setHotWaterBoost: in the device UI and as a command for WebCore users. This is useful for Nest users in Europe.
setTargetHumidity: to set a target humidity level (for the control of your humidifier/dehumidifier connected to Nest)
For the full list of attributes, capabilities & commands supported,refer to the ST community wiki:
Small issue I noticed when I came home last night. Nest account switched to Home but the thermostat was still in Eco. How do I make the thermostat return to it’s previous mode.
