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.5.2), MyNextTstatV2 (v2.3.5), MyNextAlarmV2 (v2.4) and MyNextSensorV2 (v2.1.5) may be for you.
The Nest protects 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.
You can also use the motion capability in your WebCore scenarios.
You can now download the new major version at my store:
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.5.2: able to process structure,rcs (sensors), and track data, optimization for faster queries to the Nest web APIs.
- MyNextTstatV2.3.5: added presence capability, corrected scale issue in new Samsung connect app, made some changes to thermostatOperatingState to take into account the fan schedules.
- MyNextAlarmV2.4: Added motion capability based on the attribute auto_away. Now the Protect can detect motion and can report it in the UI (ST classic mobile app)!!
_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: