[RELEASE] My Next ManagerV2 for your Nest® products

What’s weird, it worked right before I migrated accounts and then stopped working right after.

In the Live Log, I see the following error when I open the app and hit next:

8:31:36 AM: error java.util.concurrent.TimeoutException: Execution time exceeded 20 app execution seconds: 236160926902145 @line -1 (doCall)

8:31:14 AM: debug getChildDevices(false), children=7

8:31:16 AM: debug getChildDevices(false), children=7

8:30:53 AM: error physicalgraph.exception.StateCharacterLimitExceededException: State cannot be greater than 100000.0 characters

Which version of MyNextManager are you using? You should upgrade to the latest version using the same selffy download link.

I believe that you have not the latest version.

P.S. As I wrote to you before, you may split your Nest devices into 2 separate instances due to the timeouts that appear in your logs.

I am on v2.5.8.

As I wrote to you before, you may split your Nest devices into 2 separate instances due to the timeouts that appear in your logs.

Make sure to save & publish the code also.

I don’t think it was a ST issue.

I got tired of playing around with it, deleted all of the devices and SmartApp for ST. I then reinstalled the SmartApp, and have had no issues since.

Luckily I only had a few Webcore items that needed to be updated.

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.6.2), MyNextTstatV2 (v2.3.8), 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.

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.6.2: cleanup of state variables in cache to avoid state variables’ size limitations as much as possible

  • MyNextTstatV2.3.8: changed ocfDeviceType for better display in new Samsung connect app

  • 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:

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

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

MyNestTstatP1

FYI, there are also some complimentary smartapps at my github:
https://github.com/yracine/device-type-myNext/tree/master/smartapps

Regards.

I am looking to do the same thing: redirect a Nest Hello doorbell press to my Sonos speakers “Someone is at the front door”.

@yvesracine, do you see any way to to this in the future, tie the Nest Hello interactions into SmartThings , so it can be used for automations?
It’s been a little too long now that Google said the API will be coming “later”.
What is the likelihood that a non-official integration could work? I just installed homebridge-nest-cam on my raspberry pi, and it is able to bring the doorbell button integration into HomeKit.
Unfortunately HomeKit is not as easy to automate as SmartThing is. It would be great if we could bring the button press to SmartThings as well

Hi @mjlewis, sorry but the Nest hello is not exposed with the Nest APIs… Maybe, the google apis will expose it later, but I’m not sure. There is definitively no ETA.

Regards.

Ok I got all the way through the smart phone settings selected the Nest Thermostat and Protect (1 each) got to the end, selected save and I get a red banner, unexpected error and that’s it…

Where shall we start?

Pulled this from the logs in IDE seems to show up when the error happens

2502d67a-2f98-48a1-8e98-3b8c449cfa9c 5:07:28 PM: error physicalgraph.app.exception.UnknownDeviceTypeException: Device type ‘My Next TstatV2’ in namespace ‘yracine’ not found. @line 2024 (doCall)

Hi, you have to follow all the prerequisites and steps at the readme (as indicated at my store and in the zip).

In your case, make sure that you’ve saved and published the device handlers in the right shard.

Regards.

Yep missed one of the DTH, all fixed thanks

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.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.

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.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:

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

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

MyNestTstatP1

FYI, there are also some complimentary smartapps at my github:
https://github.com/yracine/device-type-myNext/tree/master/smartapps

Regards.

Just following up on this issue, it was resolved in the last few updates of your TStatv2 code.

The display is correct for both of my Thermostats now on the v2.0 app.

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.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.

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.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:

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

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

MyNestTstatP1

FYI, there are also some complimentary smartapps at my github:
https://github.com/yracine/device-type-myNext/tree/master/smartapps

Regards.

errr like?

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.

Hi,

Well, according to the Nest web Apis, you did log out. Please try again.

Follow the instructions to get your Google account info:

https://thingsthataresmart.wiki/index.php?title=My_NextServiceMgr#Issue_.2314:_My_Next_devices_are_not_updating_or_my_auth_tokens_are_lost

Regards.

Do I need to first logout from the Nest app on my smartphone or any other devices?

Not usually, but you need to login from an incognito window from the Chrome browser.

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.