[RELEASE] My Next ManagerV2 for your Nest® products

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?

Hi @gregws,

Yes, with MyNextManagerV2, MyNextstat DTH, and the WindowOrDoorOpen smartapp, you can do this use case and much more…

Refer to the 1st post of this thread for all the use cases supported.

With your contribution at my store, you can use many of my smartapps at my github:

Regards

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 temperature settings, ‘inactive’ in my schedules(scheduletstatzones), will It also ignore the motion sensors that I have in rooms within in those zones? I do want those to be ‘seen’. Thank you

Thanks for doing this & more than happy to pay! I just purchased the full pack and installed everything. Looks like authentication is working (via a migrated Nest => Google Home account), but having two issues:

I have multiple (12) Nest Protects & 2 NEST Thermostats. All show as “MyAlarm null” and “MyTstat null”.

When I look at the alarms (Protects) (in the ST Classic, ST Connect & ST IDE interfaces), I can see it’s collecting data correctly based on timestamps and the values returned… but I can’t tell which one is which. Before I start looking at device IDs & structure IDs to rename them manually checking if there’s an easy refresh fix here.

However, when looking at the thermostats the same way, there’s zero data coming back… no telemetry on the device for current settings/temps, nor is there a name.

I’ve left it for 10m to ensure it’s refreshing & getting data, and I’ve gone to the devices in the ST Classic app and manually refreshed them, but the names are all still generic.

I looked through the troubleshooting section in the docs & searched this thread, but can’t see anyone else having this same issue. Suggestions?

[UPDATE] since posting the above, I notice that now, when I select NEXT in MyNextManagerv2 SmartApp from the initial landing screen, the next page is blank. I went back to the IDE and selected UPDATE after making no changes, but same result.

Notice that after the initial setup, it seems like the devices are not being updated. I went back through the process to get the credentials & update the app. I also went to the devices in the ST Classic app and hit REFRESH, but no change… it hasn’t seen the apps in over an hour.

Running MyNextManagerV2 v. 2.5.6

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.

Regards.

Hi @swamplander,

The ST platform has some rate limiting and, when you have more than 10 Nest devices, it’s recommended to split your Nest devices into 2 separate MyNextManagerV2 instances. You just need to create a second copy of the code and add the required login_information again in the IDE.

I’ve just updated the readme at the github to indicate this ST platform limitations.

That being said, I’ve just uploaded a new version of MyNextManager(v2.5.7) which will be more resilient to these kind of issues. It’s optimized to avoid loading/updating too many Nest devices in memory, just the ones selected in the smartapp.

Please download the latest version, copy & paste the minor update over the existing code, save & publish and recreate your Nest devices from scratch.

If you have any other issues, send me some detailed logs at services@maisonsecomatiq.com.

Here is how to enable detailed logging in the IDE:

https://thingsthataresmart.wiki/index.php?title=My_NextServiceMgr#Issue_.2310:_I_want_detailed_Logging.2FNotifications_or_I_want_to_enable_Ask_Alexa_Notifications

P. S. According to your update, you haven’t extracted the login info required from your Google/Nest account. Please follow the instructions in the Readme file as indicated at my store and in the installation pdf file in the downloaded zip. Also, do not log off from your active home.nest.com session after entering your login info in the smartapp (as indicated at my store).

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.7), MyNextTstatV2 (v2.3.7), 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.5.7: optimization for faster queries to the Nest web APIs and avoiding loading too many devices in memory when not required.

  • MyNextTstatV2.3.7: added tstat attributes such as thermostat_alert,should_wake_on_approach, user_brightness, smoke_shutoff_supported

  • 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

Regards.

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.

Regards.


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?