[RELEASE] Resilient My Ecobee Device and ecosystem V5

Yes, the Nest integration still works although for the Nest Hello doorbell, it’s only considered as a cam (the Nest APIs don’t provide more features). However, fyi, sometimes the Nest APIs don’t provide the live streaming even though it’s publicly shared. The nest protects work fine.

The right package for the Nest Cams and Nest protects is the Nest devices bundle.


Thank you. So I could not trigger a light coming on if someone is at the door for example.
Especially if button is pressed. This will eliminate false positives.
Also why don’t we have full integrating.
It only makes sense.

Can you tell me what the difference is between the My Ecboee Device and My Ecobee Bundle?

Hi, as indicated at my store, the ecobee bundle includes My Ecobee device & Ecobee’s Remote Sensor (DTHs and smartapps), the ecobee Switch DTH, AND the zoning smartapp for Ecobee called ecobeeSetZoneWithSchedule.

For more details on the zoning smartapp, refer to the ST community wiki for supported features, look & feel, use cases supported & configuration, troubleshooting…

It’s basically the most advanced zoned heating/cooling solution under the ST platform. based on the concepts of rooms/zones/schedules


There are also entries for My Ecobee device & Ecobee Switch at the ST community wiki:



Thanks for it.

1 Like

Hi, For all ecobee users, please take note of the following ecobee outage annoncement (as indicated at status.ecobee.com).

If you have My ecobee device’s latest release installed, just relax, you’ll not lose your auth tokens and any failed commands will be replayed in the next hour after the ecobee outage.

If you have the ST stock device (or any ecobee implementation), this is a good time to upgrade…


Planned Server Outage Announcement

Upcoming scheduled maintenance notice

We’re performing scheduled renovations from 2 AM – 6 AM EDT on 22nd of May, 2019. Please be advised that ecobee thermostats will continue to operate normally on the set schedule and by manual adjustment, including all in-progress energy-savings events. The ecobee app, web portal and third-party apps may be temporarily unavailable. Our apologies for any inconvenience!

1 Like

Hi @yvesracine, do you know if issues are going on? For about a week now, my ecobee device using device handler 5.9.9x.8e, doesn’t refresh data.

It only gets new data if I run the init smartapp again but then doesn’t refresh it and commands don’t get sent as well.

Hi @bertanaygun,

If you have recently upgraded to the latest version, make sure to update also MyEcobeeInit (the service manager to V4.1b) as the DTH and service manager need to be updated in sync. This is actually indicated in the release notes included in the zip. You need to re-login with the new versions as the tokens handling logic has changed.

Also, if you have entered any other device preferences parameters other than for tracing, I’d recommend to remove any values as they can interfere with the tokens renewal logic.

If you still have any issues after the above troubleshooting steps, I’d be very curious to see your logs as I’ve not experienced any issues for several years now.


Filter the logs for MyEcobee device and MyEcobeeInit only and send them to me at services@maisonsecomatiq.com.

I personally monitor many user locations in North America as part of my support packages and there has been no issues whatsoever (except the occasional ecobee server outages), but in any case, My ecobee device can replay any failed commands .


Am I missing something when it comes to setting up my ecobee to accept hold types? I want to create a “vacation” button that when clicked, my ecobee will go into an indefinite hold, but I have tried multiple different hold commands, but keep an error in logging around the ecobee.


Hi, Please consult the ST community for the holdType preference and how to call the different methods with the holdType parameter. The methods in the DTH implementation also explain how to call them with the right parameters. All the configuration details are explained at the ST community wiki. If you want to set a different holdType in webcore than the default one set in the device’s preference, there is a section about it at the end.



And I did, but not sure how I use DTH in webcore

I don’t use Webcore, do please check with the webcore forum if you need help with webcore.


Do you have a smart app that will switch program to a specified program, for instance away, by pushing a virtual switch?

Hi, based on a virtual switch, you can execute automatically a routine under the ST classic app which will enable the (custom or Away) ST mode of your choice. The ST mode can trigger the right ecobee program (or climate) using the ecobeeChangeMode smartapp at my github.


Is there a way to set up the monitor and set smartapp to switch on the fan if the temp is between the program set point and the childapp hold temp?

No, you’d need Webcore for those custom rules.

For advanced fan features, you’d need to contribute to ecobeeSetZoneWithSchedule smartapp at my store. The smartapp is based on the concepts of rooms/zones/schedules.



PS. All the use cases supported by my smartapps are described in the 1st post of this thread.

Is there any way automatically to trigger reset of an obstructed vent? The 8 vents in my system sporadically flash red and report the obstruction to ST. Attempted remedies include new batteries, lubrication, configuring wifi to avoid ST’s ZigBee channel 24, and installing the most recent version of EcobeeSetZoneWithSchedule.

Hi Gary, if all your smart vents get obstructed, then there is something wrong with your vents…

I’ve never experienced any obstruction like that at my house and I have 15 vents.

My smartapps already check for the obstructed status and try to open/close them as successive commands, but of course, if they are physically obstructed, it’s not possible for my code to correct it.


15 vents! Formidable!

ST’s Event List shows ChallisfordVents (renamed ecobeesetZoneWithSchedule) shows the sequence APP_COMMAND/setLevel, COMMAND/setLevel, DEVICE/setLevel. The source for APP_COMMAND is your ecobeesetZoneWithSchedule. The source for COMMAND is unclear. ST reports only, “setLevel command was sent to Vent.” The APP_COMMAND/COMMAND pair often repeats many times before DEVICE, the vent, responds. That is during normal operation. I haven’t recently captured the sequence when an obstruction is in effect. Is that as it should be?


I don’t know anything about your configuration, but yes, it can be normal as my smartapp can send multiple setLevel commands in a short 5-min timeframe especially if you have few vents and more than 50% of your vents are closed… The smartapp will not allow too many vents to be closed at the same time to avoid damaging your HVAC (this is part of the safeguards).

The smartapp runs a cycle every 5 minutes and adjusts the vent settings according to your ambient temperature vs the setpoints.

As an example at my house:

Smart Vent MB1 (Device) Events —

Date Source Type Name Value User Displayed Text
[2019-05-31 1:58:16.223 PM EDT
moments ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/aa6bb2f0-83cd-11e9-aea9-068a251f1522?all=&source=&max=25) APP_COMMAND setLevel ecobeeSetZoneWithSchedule sent setLevel command to Smart Vent MB1
[2019-05-31 1:53:18.965 PM EDT
7 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/f9429c50-83cc-11e9-9ba9-0a685269a396?all=&source=&max=25) DEVICE pressure 100821.1 Smart Vent MB1 pressure is 100821.1Pa
[2019-05-31 1:53:16.416 PM EDT
7 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/f7b8ef10-83cc-11e9-ba57-0a21077b4dca?all=&source=&max=25) APP_COMMAND setLevel ecobeeSetZoneWithSchedule sent setLevel command to Smart Vent MB1
[2019-05-31 1:50:40.107 PM EDT
9 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/9a90aad0-83cc-11e9-b314-064f568497ca?all=&source=&max=25) DEVICE temperature 23.5 Smart Vent MB1 is 23.5°C
[2019-05-31 1:48:18.583 PM EDT
12 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/46333980-83cc-11e9-bbdc-128ea41ac3fc?all=&source=&max=25) APP_COMMAND setLevel ecobeeSetZoneWithSchedule sent setLevel command to Smart Vent MB1
[2019-05-31 1:43:18.673 PM EDT
17 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/9371f6b0-83cb-11e9-a670-069a69ae3e72?all=&source=&max=25) DEVICE pressure 100817.1 Smart Vent MB1 pressure is 100817.1Pa
[2019-05-31 1:43:17.690 PM EDT
17 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/92da98b0-83cb-11e9-b2d7-127642100480?all=&source=&max=25) APP_COMMAND setLevel ecobeeSetZoneWithSchedule sent setLevel command to Smart Vent MB1
[2019-05-31 1:40:39.773 PM EDT
19 minutes ago ](https://graph.api.smartthings.com/device/da98b33b-3c05-46d0-81a1-2b71aee74ad4/event/34bd4610-83cb-11e9-987e-12b55662f0c4?all=&source=&max=25) DEVICE temperature 23.41 Smart Vent MB1 is 23.41°C

© 2019 SmartThings, Inc. All Rights Reserved. Terms of Use | Privacy Policy

SmartThings; SmartApps®; Physical Graph; Hello, Home; and Hello, Smart Home are all trademarks of the SmartThings, Inc.