In my code, the thermostats are considered remote sensors just like the others. There is no special processsing for them. I’ve checked at other user locations that I monitor because some users have contributed to my support packages, and this specific issue is not happening elsewhere, so there must be something wrong in your SmartThings or ecobee configuration.
If you want me to look into it, please contribute to one of my support packages at my store.
That appears to have been the issue. I recall renaming the thermostats shortly after the initial install, which sounds like it broke the association within your code.
After tearing it down and setting it back up again it is working as I would expect.
Hi, I sent out a new version of ecobeeRemoteSensorInit (v2.7) (to all my active contributors) which allows renaming of the ecobee remote sensors without any impact.
If you want to keep getting updates, please follow the procedure in the email.
As I posted before in this thread, when you contribute to my code, you’re contributing to the ecobee-SmartThings integration work that I’ve accomplished in the past 3 years. We’re talking about 15K lines of code that has been thorougly tested and deployed at many user locations all over North America, Europe, and even Australia.
I can guarantee you that My Ecobee device will work well at your location and you can also read the different testimonials in this thread.
To answer your specific questions:
1. My Ecobee bundle contains My ecobee device with the remote sensor AND the ecobeeSetZoneWithSchedule smartapps.
For more details, refer to
All other smartapps are available at my github, so that you can control your ecobee thermostat according
to the use cases described in my 1st post:
2.You have some limited minor updates as indicated under the terms of service at my store till a major version is released (V6). This is standard practice in the software industry.
I cannot tell you at this point when the V6 will be released (it may be within few weeks or few months).
With the v5.7.6 and 5.7.7 releases that I sent you by email to your paypal verified email address back in December and January, I included a detailed procedure on how to stay “active”.
Please follow the procedure within the emails or contribute to one of my support packages at my store.
@yvesracine, what is the proper command in webCoRE to monitor how long heating or cooling has been active. I am currently using “thermostateOperatingState” is any of cooling or heating…but the timer keeps getting reset even though the cooling cycle is still active. Must be resetting whenever polling occurs.
Goal:
I am trying to setup a rule that says,
If heating or cooling Stays Active for 2 Hours
Then Set Thermostat Mode to Off
The problem is I can not use Stays as it is a trigger so I am using
If heating or cooling is active
Wait 2 Hours
Turn Off
Cancel on Piston State Change
Hi @rontalley, I don’t use webCore or any other rule engines (I’m very happy with just my own smartapps), so I’m sorry but I cannot help you on this topic.
For sure, the thermostatOperatingState attribute could be used within webcore for that purpose.
But, my DTH also directly exposes the running stats from ecobee (data like HomeIQ) which can give you more precise info.
This is a just a reminder about the following integration features of My ecobee device with the Ask Alexa smartapp available since V5 (more than 9 months ago):
If you want to be notified (via push notifications) of any exceptions affecting My Ecobee device you’d need to do the following:
a) In MyEcobeeInit>Other Settings Page>HandleExceptions
just set the handle/notify exception input parameter to true.
If you want to be notified of any ecobee alerts, just set the following flag to true
b) In MyEcobeeInit>Other Settings Page>NotifyAlerts
If you want to verbally notified via Ask Alexa/Amazon Echo of the above (alerts and exceptions), just set the following flag to true:
c) In MyEcobeeInit>Other Settings Page>Amazon Echo/Ask Alexa Notifications:
I don’t think you can change the thermostat mode with the native Amazon integration (I’ve tried and it doesn’t seem to work), However, it works well with Ask Alexa.
Just to let you know, My ecobee device has been tested with the latest ecobee thermostat (ecobee4) with its remote sensors… Everything works as expected.
Just installed the Ecobee4 and tossed my Nest. Installation was easy - thermostats usually are. I bought the myEcobee Bundle and installed it - very easy to install. Configuration is very similar to ScheduleTstatZones app - but many more capabilities with Ecobee than there were with Nest.
I have to say, the app has a LOT of things that can be configured - well worth adding a support package and letting Yves tailor the configuration to meet my needs.
Love having a solution that integrates ST with Keen vents and my thermostat. Overall our house stays much closer to our desired temperature in heat or cool modes.
I’ve installed MyEcobee and remote sensor device types. I am wondering if I can us them as sort of a poorman’s security system (report on movement when no one is home). I think I realized that there is something like a 30 minute delay (which is OK, we are talking poorman’s solution afterall!).