[RELEASE] My Next ManagerV2 for your Nest® products

Hi,

Please follow all the prerequisistes and installation steps in the readme at my github (as indicated at the store and in the zip file).

You’ve missed this step which asks you to copy & paste the code for the DTH,save & publish:

P.S. You don’t need to redo all the steps, after saving the DTH code, just go back to MyNextManagerV2, press Next till Done. The device should be created then.

Regards.

Perfect added the Device Handel now works great :slight_smile:

1 Like

previous_hvac_mode is always coming back null which makes it never switch out of Eco mode when using your smart app NestChangeMode does the smart app work for you or anyone else?

Hi, please download MyNextTstatV2.1.9 using the original sellfy download link that was sent to you made your contribution. A fix has been implemented.

Regards.

Hi,

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.3), MyNextTstatV2 (v2.1.9), MyNextAlarmV2 (v2.1.4) and MyNextSensorV2 (v2.1.4 ) may be for you.

You can now download the new major version at my store:
www.ecomatiqhomes.com/store

If you are already a contributor, you just need to use the original sellfy download link to get the new minor version.

  • MyNextTstatV2.1.9: corrected home() method to revert from eco mode.

_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 reponsive 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 full list of attributes, capabilities & commands supported,refer to the ST community wiki:

https://thingsthataresmart.wiki/index.php?title=My_Next_Tstat

https://thingsthataresmart.wiki/index.php?title=My_Next_Alarm

MyNestTstatP1

!MyNestProtect

Regards.

Hi,

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), MyNextTstatV2 (v2.3), MyNextAlarmV2 (v2.2) and MyNextSensorV2 (v2.1.5) may be for you.

You can now download the new major version at my store:
www.ecomatiqhomes.com/store

If you are already a contributor, you just need to use the original sellfy download link to get the new minor version.

  • MyNextManagerV2.5: able to process structure,rcs (sensors), and track data, minor optimizations
  • MyNextTstatV2.3.3: added presence capability, corrected scale issue in new Samsung connect app
  • MyNextAlarmV2.3: corrected status in new Samsung connect 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 reponsive 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:

https://thingsthataresmart.wiki/index.php?title=My_Next_Tstat

https://thingsthataresmart.wiki/index.php?title=My_Next_Alarm

MyNestTstatP1

!MyNestProtect

Regards.

Any details on how the new presence setting works?

I also noticed in the new SmartThings app that the following categories are duplicated with different options:

Hi, I don’t have much control over the UI in the new Samsung connect app.

You problem may be a cache issue, I’d recommend deleting your cache and restarting the app as I personally don’t have this issue under Android.

As far as the presence capability is concerned, you may want to use the ST classic app in parallel till SmartThings makes the new Samsung connect app more compatible with the ST classic.

You can use both apps (ST classic and new Samsung Connect apps) without any issues.
Regards.

The presence is available in both apps, its just the display that is the issue in the new app.

I assume presence is read only? Or can it be overwritten?

I was hoping to overwrite the presence value so that the thermostats would move from AWAY to HOME when I open my garage door.

Yes, with the new away() and present() methods, you can call them from Webcore according to your custom rules.

1 Like

Hi,

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.4), MyNextAlarmV2 (v2.3.2) and MyNextSensorV2 (v2.1.5) may be for you.

You can now download the new major version at my store:
www.ecomatiqhomes.com/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.4: added presence capability, corrected scale issue in new Samsung connect app, made some changes to avoid any null values during initialization
  • MyNextAlarmV2.3.2: corrected battery level for wired Protects

_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 reponsive 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:

https://thingsthataresmart.wiki/index.php?title=My_Next_Tstat

https://thingsthataresmart.wiki/index.php?title=My_Next_Alarm

MyNestTstatP1

!MyNestProtect

Regards.

1 Like

I deleted and reinstalled the iOS app, same issue in the new version of the app.

Sorry, but there is nothing I can do on my side. You’d need to contact SmartThings support as the code is not the problem here, it’s your UI display. It could be related to your iOS version.

Hi,

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:
www.ecomatiqhomes.com/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:

https://thingsthataresmart.wiki/index.php?title=My_Next_Tstat

https://thingsthataresmart.wiki/index.php?title=My_Next_Alarm

MyNestTstatP1


Regards.

1 Like

@yvesracine: with the new motion detection changes, any idea on why thermostats are returning 0/1 and the protects are returning true/false for the auto_away parameter?

Is this a Nest issue or a device handler issue?

Hi, it’s a Nest implementation issue. My Next devices just expose what’s available at Nest.

Does the Nest Tstat correcly show motion (based on auto_away) for you? I haven’t tested it yet.

I’m tracking that now to confirm with Webcore. I think it works fairly well, I am seeing random changes for both the Protects and the Thermostats (where it randomly detects motion). I still haven’t been able to figure out if its Nest and what causes them.

Hi, I added the motion capability in MyNextTstatV2.3.6 in the header and in the UI.

Also, I made sure that auto_away reports true or false just like the protects.

P.S. Make sure that your refresh rate is set to 1 minute to get better motion updates.

Hi,

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.3), MyNextTstatV2 (v2.3.6), MyNextAlarmV2 (v2.4.1) and MyNextSensorV2 (v2.1.5) 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.
You can also use the motion capability in your WebCore scenarios.

You can now download the new major version at my store:
www.ecomatiqhomes.com/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.3: able to process structure,rcs (sensors), and track data, optimization for faster queries to the Nest web APIs.
  • MyNextTstatV2.3.6: added motion capability based on auto_away, and exposed auto_away as true or false
  • MyNextAlarmV2.4.1: made some correction to populate last_connection and is_online 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:

https://thingsthataresmart.wiki/index.php?title=My_Next_Tstat

https://thingsthataresmart.wiki/index.php?title=My_Next_Alarm

MyNestTstatP1


Regards.

1 Like

Hi! I’ve been pretty sad since the previous Nest integration got shut out due to Google’s deprecation of the WWN program. Does your application allow me to set ECO mode if contact sensor are open for x amount of minutes?