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

Thank you. I’m off tomorrow and so I’ll dig into it further then. Thank you

Hi, after reading your question again, I think that I misunderstood your question, is it about the ScheduleTstatZones smartapp?

I gave you the method signature to enable fan schedules using the NextTstat DTH (with your own custom rules within Webcore as an example), but I guess you would like to enable it through the schedules in the zoning smartapp.

If so, please take note that the Nest APIs only allow turning on the fan using a timer or a schedule, and ScheduleTstatZones is using a 15-min. trigger by default.

So, in your case, if you want to run it almost continously, it would be better to run the fan using the method setThermostatFanSchedule() instead (as indicated in my previous post). You can use webCore to call the method on the NextTstat device.

To enable detailed logging on the zoning smartapp, refer to



Yes. Was speaking about scheduletstatzones app. I have never used webcore and not really looking to learn it just for this use. Thank you Yves.

Hi, as I wrote to you in my previous post, for your use case, I’m afraid that the Nest APIs are limited… The only valid & reliable option would be to use setThermostatFanSchedule() method with WebCore so that your fan runs continously between a startTime and an endTime…

P.S. ScheduleTstatZones works for all kinds of connected thermostats, and Nest has a different behavior than regular zigbee/zwave/other wifi thermostats. Other connected thermostats don’t require a timer to turn on the fan, hence I cannot modify the zoning smartapp for your use case.

In ScheduleTstatZones, have you enabled the fan adjustement in GeneralSetup? If so, that’s the only settings required that I can think of.

input (name:"setAdjustmentFanFlag", title: "Enable fan adjustment set in schedules based on sensors?", type:"bool",required:false)


After fiddling with it, it does seem that I can make an automation in the SmartThings app without webcore based on a trigger. Your software makes exposes the thermometer and fan mode is an option. Experimenting with it, I was able to trigger the fan and so Thank you.

1 Like


Just want to inform my contributors and all Nest users that a new version of MyNextTstat(v3.2.3) can be downloaded at my e-commerce solution provider (sellfy) using the original download link.

You can download the Next devices at my store:


  • The new version corrects the setTargetHumidity() method to avoid any issue when setting the “target_humidity_enabled” attribute to true for humidifiers/dehumidifiers connected to a Nest tstat.

  • All you need to do is to copy &paste the new code over the existing one for the DTH (Device Handler Type).

  • You’d probably need to refresh the Samsung connect app’s cache in order to see the UI changes for the Next devices since V3. There are some instructions to do so in the release notes.

  • Since V3 of MyNextDevices, the new UI presentation adds the set Target Humidity tile to control the humidity via the humidifiers/dehumidifiers connected to Nest (see image below).**

On top of it, there are many complimentary smartapps designed for My NextTstat DTH and are located at my github.

You can also refer to the 1st post of this thread for all the use cases supported.

MyNextManagerV3.2, MyNextTstatV3.2.3, MyNextAlarmV3 (For Protects) are available at my store:



1 Like

Ended up buying this a few days ago and trying to set it up using my Google Account in the nest field trial (essentially making sure any public endpoints in the code use home.ft.nest.com instead of home.nest.com), but have been unable to get it to see my Thermostat, protect, or sensors…

Using the latest DTH for the thermostats, I am seeing the following error in the IDEs once in a while:

10:00:33 AM: error java.lang.reflect.UndeclaredThrowableException @line 3323 (getStructure)

Just an FYI.


Probably a ST platform issue while updating the DTH (ref. UndeclardThrowableException)… This is not related to my code per se.


On another note, I am seeing a issue with the Humidity SmartApp, it’s setting the appropriate humidity target but it’s turning off humidification?

The maintain humidity above selector is being turned off by the SmartApp?

Hi, for energy savings purpose, the smartapp may change the “target_humidity_enabled” flag when the ambient relative humidity is within range (+/- 5% by default vs. the target or within your custom range if any provided)…

Does the latest Nest Thermostat work with this app? I have the newest Net Thermostat with the mirrored finish and I purchased the MyNext Tstat for SmartThings. However, I cannot get my device to show up in the SmartApp.

I tried Issue #15: My Nest Tstat doesn’t show up in MyNextManager’s list of devices, but my device does not have a WWN reset option, it only has a factory reset. I tried this and went through the setup process again, only to find out the SmartApp still does not recognize my device.

Usins the IDE logging, I did not see any errors and I have copied to my SmartApp the cookie and token setup information. My cookie started like this, “cookie: __Secure”, so I copied __Secure and everything that followed.

Am I missing anying as to why my thermostat will not show up?


I cannot validate your cookie as it’s unique to your Nest/Google account…You’re the only one able to do the cookie and url extract.

if your tstat doesn’t show up after a reset, then, most likely, your cookie or google_issue_token_url is not valid, please follow the instructions at the readme or at the ST community wiki (with screenshots):


P.S. The reset option is a workaround that it’s also used for the ST stock device (it’s not specific to my custom Nest integration), for additional workarounds, refer to


Is there anything else to try or verify as I am dead in the water here. I have went through the process several times getting a new URL and Cookie to try and nothing. When viewing the ST Log, I get no errors, so I’m not sure what is not working and where. I purposely tired leaving the Cookie variable blank to see an error and I did get one, however when putting the correct URL and Cookie variables in place, I get no errors, but I cannot see my thermostat.

When logging into https://home.nest.com/, what should one see? I do not see my thermostat, only the option to change my Home to either Home or Away and the ability to “Add product” However, when trying to add product, my thermostat is not an option to add, yet my thermostat is working and I can control it from the Google Home app. Just wondering if I should be able to see it and control it from the web interface too.

Any help would be appreciated as I’m getting no where fast. Also, I have version 3.2.4 of MyNextManagerV3 and I purchased My_Next_Tstat.

Hi @twodaend , if you don’t see your tstat at home.nest.com, then you need to contact Nest support as you should see it first in the Nest app/portal before being able to expose it to SmartThings.

I’m afraid that I cannot help you on this one, as this is beyond my code.

P.S. Only after adding your tstat to the Nest app/portal, then you can think about exposing it to SmartThings.

After thinking about this, I never used the Nest app. With my latest model Nest thermostat, I have only used the Google Home app. I never had a Nest account, nor did I have to migrate to Google Home. I have used Google Home from day one.

Would your app work for those who never used Nest and have only/always used Google Home? Correct me if I’m wrong, but I don’t think there is a web interface for Google Home.

Whether you have a Nest or Google account, you should be able to see your tstat in the Nest app /portal.

If not, then it means that your tstat is not linked to your account, and the Nest APIs won’t be able to see it.

Please contact Nest support to fix your tstat link with your account

Just chatted with Google/Nest Support and was told, the newest Google Nest Thermostat only works with the Google Home App and cannot be seen or controlled via the Nest App or Nest web interface

The support agent said, “New Google Nest Thermostat is design exclusively for Google Home App.”

Looks like I’m out of luck.

Problems with Google nest in Ohio
Cannot login to nest portal. Google account not working
Smartthings official nest thermostat, non ide, not working. No connection. Deleted smartthings tstat and tried to install. Now thermostat not showing. Killed it.

Using your tstat worked perfectly 2 days ago, now it’s down.
Is this a permanent Google nest issue with portal not working?

Hi, this may be a local issue, as MyNextManager in Chicago is working well. Please contact Nest support.

P. S. I don’t work for Google/Nest so I’m not aware of any customer service status.