With V1.1.7 I was able to delete the extra sensors.
With V1.1.7 I was able to delete the extra sensors.
To all my contributors and ecobee users (which would like more resilience under the ST platform),
The ecobee outage was reported at 17:14 EDT and was resolved at 19:16 EDT and now everything is back to normal. The commands sent to My Ecobee device that were not executed have been stored in a queue for execution in the next hour window.
It’s always a good idea to check the following ecobee status page for any ecobee issues:
P. S. With my ecobee Device, you don’t need to re-login at ecobee as the code is resilient to the ST or ecobee outages.
If you’ve tried to re-login at ecobee w/o success because of a temporary issue, then you may have lost your auth tokens in the process, so just make sure to follow all the steps at the readme, and re-login when your ST account is back to normal.
For all my contributors & ecobee users, I’ve just released a new version of My Ecobee device (v5.9.9x.3) which allows you to change the backlight settings of the ecobee (ex. BacklightSleepIntensity, BacklightOnIntensity, BacklightOffTime in seconds).
The new commands are
command "setBacklightOffTime" command "setBacklightSleepIntensity" command "setBacklightOnIntensity"
ex. device.setBacklightSleepIntensity(0) // in webcore, to deactivate the backlight in sleep mode
FYI, a new smartapp at my github called ecobeeSetBacklight allows you to change the backlight settings on a predefined schedule.
You can also use the github integration to get the smartapp using the following settings:
Owner : yracine
Name : SmartThingsPublic
Branch : master
As a contributor to my code, if you haven’t upgraded to MyEcobeeInit (v4), you need to carefully read the release notes to ensure a smooth transition. The new version allows you to create all ecobee devices (ecobee tstat + ecobee switch+).
FYI, My Ecobee devices (tstat + switch) are compatible with the new Samsung Connect mobile app.
Please note that at the moment, the new Samsung mobile app will only display the basic attributes for the thermostat until the custom capabilities are available for the developers. You can then use the ST classic app for more capabilities and commands.
The instructions to force a refresh for your existing device(s) in order to be displayed under the Samsung app are included in the installation file as part of the download zip file.
You can download the new versions at my store using your original sellfy download link.
P.S. If you’re an active contributor to one of my support packages (and I have access to your ST account), the upgrade has already been done for you. You don’t need to do anything, everything has been taken care of.
Question about the humidifier control. The internal humidity sensor doesn’t have the best accuracy. Can you recommend a external humidity sensor to integrate into the humidity control?
Hi, there is a thread here
Just used one of my updates now that setting hold type is easy in WebCore.
Just wanted make sure I’m doing it right:
To retain previous behavior plus limiting Google commands to nextTransition::
Did my life just get that easy?
How do you do it in WC? I tried that quite a while ago and couldn’t figure it out. Sounds like there is a new update to WC that makes it easy? I haven’t updated WC since with my ST ecosystem I don’t update something unless broken or new functionality I want, but this would fall into that new stuff I want! I have that exact problem of not wanting to set holds forever through Google.
With the new version it takes a few minutes to settle and you have to pop open the webcore app smartapp and kick it until the new commands show in the config dashboard. Then it’s just choose it like any other command. the only tricky part is the selections aren’t programmed in so there’s a button for parameters to pass and you can select the string type and enter your values as needed. Not as clean as retail-supported methods but hopefully coming in the future so we don’t have to look everything up.
Or, at least, that’s what I’m here to make sure I’m doing right…
Since this post, the setHoldWithHoldType method has been available for webcore users :
There is some documentation about setHoldWithHoldType under the ST community wiki (at the end of the section):
There are also some explanations near the signature of the method (in the DTH code).
Make sure to call the method with the right parameter types (setpoints as number).
@guarddog13 can help you with webcore, as he was the first to query about this method last month.
Its string (leave blank), integer (heat sp), integar (cool sp), string (fan), string (hold type).
Hm, I have all temperatures in my Ecobee comfort settings already, do I need to re-duplicate them all in this call now? I’m just trying to trigger away, as-programmed, indefinitely (like when I leave), and then remove the away/resume and return to normal function of holds defaulting to nextTransition.
Just make that call as your away, if you want to be indefinite and indefinite is different than your normal transition. When you return home just use resumeProgram() and it will go back to your ecobee program.
I do it like this because i have my ecobee switch back to its normal program after 2 hours of a temp change. I also want yves DTH to do nextTransition. If everyone at my house is away i want that to be indefinite so i use this method.
When using your app and device handlers to expose the ecobee remote sensor, what is the polling interval, is it adjustable ? The stock ecobee app only reports on 15 minute intervals, not usable for motion.
First, the ecobee’s proprietary remote sensors are not motion sensors per se, but occupancy sensors…
They have some limitations for motion detection, refer to
In any case, the polling interval can be changed in the ecobeeRemoteSensorInit smartapp (by default, it’s every 5 minutes).
So is this the correct way to set an indefinite away hold?
Per https://www.ecobee.com/home/developer/api/documentation/v1/functions/SetHold.shtml it seems to be but if so I’m not sure why setholdwithholdtype was needed…
Now that WebCore is so popular is there any documentation on how to interact with myEcobee with it?
I did see this: device.setClimate("",‘away’,[holdType:‘indefinite’]) BUT I have no idea what to put where in WebCoRE because I can’t seem to find an example of values mapping (a list of commands, arguments, variable types, and orders required).
No, it’s not the right way.
First, do you need to set a permanent Away Hold (which will apply the indefinite option for all your commands to the thermostat) or a temporary one (for just one command)?
If the former, then you’d need to set the holdType parameter in the device (indefinite is the default anyway).
If the latter, then you’d need to use the setHoldWithHoldType() command with your heating/cooling setpoints as indicated in the previous posts above. Webcore doesn’t support Maps as input parameter hence the setHoldWithHoldType() method for the webcore users.
In all cases, refer to the ST community wiki for a better understanding of the holdType possible options.
P.S. If you’re using webCore, then you’d need to contact power users in this forum (or the webcore forum) who use webcore with My Ecobee device.
FYI, I don’t use webcore as I’m focusing on implementing some smartapps for the most common use cases (refer to my smartapps at my github).