[RELEASE] My Next Manager for your Nest® products: migrated to custom capabilities (home/away, motion, presence, and more)!

Perfect. Thank you. I was hoping the motion sensors would still work for Eco regardless of whether or not zones were used for temperature sensing.

| | Nicholas Hillman - Chat @ Spike | j4x1h |

  • | - | - | - |

| yvesracine Insightful
May 30 |

  • | - |

Hi, if you make a zone inactive, then the motion detector(s) in it will still be used for setting the thermostat to away or present, but the temp sensor(s) will not be used for the average calculation to adjust the setpoint.

If you have any vents in the inactive zone, the vents won’t be adjusted either.


Visit Topic or reply to this email to respond.

In Reply To

| Nicholas_Hillman1 Nicholas Hillman
May 30 |

  • | - |

Hello Yves. I have a lot of motion sensors and am using them in rooms(zones)to perform ‘Eco mode’ in the nest Thermostat. However, I do not use those zones to determine temperature settings as I solely use the upstairs zone to dictate that. If I make the other 2 zones that I don’t use for temperatur…

Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Thanks for the quick update… one point of clarification: I had done the login details (google account option).

I removed all devices and the installed app, updated the code & went back thru the setup. Worked great. I only added 9 of my 14 devices on the first instance.

They are updating, however, unable to get back into the app and turn on more detailed logging. I get the same experience before: once I get past the first about screen, it’s blank and I get an error when clicking DONE. Same experience when I try to create a second instance.

Recorded a video… should I email that to you?

Also, better to remove all and re-add again and enable more detailed logs to send those?

Hi, there has been a lot of ST platform issues in the last week (timeouts and nosql issues)… The blank page in the 2nd page could be the results of ST rate limiting & timeouts.

Why don’t you start small with 4-5 devices in the 1st instance and build up from there? I have 8 devices at home, but at this time, they are not refreshing as often due to the timeouts. A way to do it is to break the workload into multiple chunks (2 or even 3 instances)
Make sure to use the latest version (v2.5.8 ) or at least MyNextManagerV2.5.7, copy & paste the new code over the existing one in the IDE, and don’t forget to save & publish. …You can download the latest version using the sellfy download link that was sent to you when you made your contribution.

Make sure to follow all the prerequisites and installation steps in the Readme file. And, do not log off from your active home.nest.com session. This approach will work like anyone in this thread.

I personally don’t need a video as the installation steps have been tested over and over again at multiple user locations… If you want to make a video after you’ve been successfull for others, that’s fine (but there are some secret login information not to share). What you need to do is to follow the prerequisites & instructions step by step…

P. S. You can also enable detailed logging in the IDE by clicking on a device and editing the preferences


I’m running latest (2.5.8), saved & published, verified I did all pre-req’s, auth is working as in the initial setup, I can see all my devices & I didn’t logout of my browser session where I obtained the login URL & cookie (I just closed the browser as your README says).

The “Last Activity” column for the list of devices in the IDE shows old timestamps when the device was seen, but when I look at the device properties in the mobile app, it shows it was updated in the last 10m. IOW, after going through the initial setup, everything seems to work fine.

I just deleted everything to try again, adding JUST my two thermostats and assigning the app the name “NEST Thermostats” to setup another instance later. I can see the status & control of the thermostats. IOW, everything worked exactly as I’d expect (and has so far).

But trying to get back into the SmartApp (or to add another instance by repeating the setup) & selecting NEXT after the about screen always goes to the blank screen. This is where my problem is… my understanding from your response is this is a ST issue that’s been going on for the last week. Is there a status page I can monitor (I’m a software dev, just not versed in ST development, so I understand this part of the process)?

Will monitor the thermostats to see if they keep refreshing & can connect and will keep trying slowly add more devices.

Hi, if you want to add another copy of the code, you just need to create another smartapp called MyNextManagerForProtect (change the name of the smartapp at the end of the file), copy the same Nest login info, and enable oAuth.

Will this work to get my nest thermostat into my smartthings 2.0 app?

Yes, as per the screenshots displayed above in the new Samsung Connect app.


@yracine: I had to finally migrate my Nest account to a Google account due to the new Nest Aware packages. I followed the instructions and was able to restablish communication with all of the systems by adding the request url and the cookie to the settings.

All devices started updating immediately when I did that. And my automations started to send notifications.

The challenge I have is, when I start MyNextManagerV2, click Next, I end up with a blank page, nothing is pulled in. Any thoughts on what is going on? I only have the option to go back or click Done. When Done is clicked, I get the “Error saving unamed page. Please contact SmartApp developer.”

The same issue happens in the old and new SmartThings apps.

Hi @Skates, since about a week, the ST platform has had lot of timeout issues. You can see it yourself when you enable live logging in the IDE. Due to the rate limiting in the ST platform, you may have this issue when you have a lot of Nest devices under a single Nest/Google account.

Hopefully, this is temporary.

Please refer to my previous post about how to split your Nest devices in 2 or 3 MyNextManagerV2 instances.


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.


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:

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:




FYI, there are also some complimentary smartapps at my github:


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.


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.


Yep missed one of the DTH, all fixed thanks