Yesterday, the cloud-to-cloud connections with ecobee were down for a little bit more than an hour, and again My ecobee devices at many user locations (that I personally monitor) were able to recover without any issues and no need to re-authenticate…
Just like back in June last year…
The code has been proven to be more robust than the stock ST ecobee device.
After a few month using Ecobee 4 and My Ecobee Device I am happy I made the switch from Nest. I have all functionality of the Ecobee in ST thanks to this device handler. Also, I am taking advantage of this device by using it with ecobeeSetZoneWithSchedule SmartApp and Keen Smart Vents. Developer is always quick to reply to any questions/concerns/comments.
I just bought the app and installed monitorandsetecobee. I thought this had the follow me feature similar to recover and that’s why I primarily got this. However, I can only get it to do an average of all the motion sensors temperatures. I need it to only use the temperatures of motion sensors that have recently seen motion (like ecobee’s follow me). Averaging all isn’t following . Please how do I get this working?
If you’ve added all your motion sensors (with both temp & motion capabilities) in the following parameter (and only in this parameter, not elsewhere in the smartapp):
Choose indoor sensor(s) with both Motion & Temp capabilities to be used for dynamic temp adjustment when occupied [optional]
The smartapp will only average out the motion sensors that have been occupied in the last ‘x’ minutes (configuable threshold) for the setpoint adjustment.
This is done in the addIndoorSensorsWhenOccupied() method in the smartapp. You can check the code yourself… The average calculation will only take into account the occupied sensors as done in addAllTempsForAverage() method.
Please note: MonitorAndSetEcobeeTemp is a very basic version of ecobeeSetZoneWithSchedule. If you want to choose which sensors participate in a given schedule during the day, visualize each room’s motion/temp values at any given time in a dashboard/config page, and have more granular control of each room’s motion/temp sensor & specify a different timeout for each motion sensor, then you should contribute to the paid smartapp instead at my store. The smartapp implements the notion of schedules & zones (composed of 1 to many rooms). So, I’m not planning to make any changes to MonitorAndSetEcobeeTemp.
Thanks! And is there a way to see the averaged temperature being used? Would that be the number in the centre or is that number only the ecobee temperature?
Hi, As I wrote earlier, My Ecobee device is the DTH (interface with ecobee) where you can see the setpoints.
MonitorAndSetEcobeeTemp is the smartapp that does the average out of your temp sensors and adjusts the setpoints at the DTH (with a temporary “hold”). So, the setpoint in the DTH will change according to the smartapp’s logic. You can manually press the “refresh” tile in the DTH to get the latest setpoints.
If you want to have detailed notifications of the smartapp’s logic and how it affects your setpoints, just enable the detailed notifications in the MonitorAndSetEcobeeTemp smartapp (last page) and indicate “yes” to send Push Notifications. You can also see the logic running under the IDE at
And, as I wrote earlier, if you want a dashboard and config pages that allow you to visualize all your remote sensors and the average temp differential used to change your setpoints, then you’d need to contribute to ecobeeSetZoneWithSchedule smartapp at my store…The paid smartapp will show you all the relevant stats.
How does your smartapp work with ecobee’s ac overcool feature? I’ve found that the humidity gets pretty high at night which makes it pretty uncomfortable. I set the ac overcool max on ecobee to 2F to help w/ reducing the humidity (don’t have a humidifier yet) and when I run it by itself, it works pretty well.
Would the AC overcool work with your smartapps or is there a smartapp that replicates this (so rather than using outdoor humidity, it uses indoor humidity to determine whether to keep cooling).
P.S. If you have an humidifier and/or a dehumidifier connected to ecobee later,you could use the MonitorAndSetEcobeeHumidity smartapp to monitor and control your indoor relative humidity level.
I’m still not sure this whole “follow me” is working for me. I changed one of my motion sensors to have a very high temperature (86F) while my Ecobee had a temperature of 73.4F. My home auto thresholds are at 71F and 76F respectively with the setpoint at 73F. Thus, the average temp is 79.7F and I’d expect the offset to be at 79.7F - 73.4F = 6.3F and the new setpoint to be at 73F - 6.3F = 66.7F. However, my ecobee isn’t cooling any further even though it’s set by MonitorAndSetEcobeeTemp.
Looking at the logs, I see that it correctly calculates the average temp. However, there is no log about an offset or the like so I have no idea what’s happening. Also, the my ecobee device ST UI has the setpoint set to 73F. I also looked at the history of the logs and even though different rooms have had different temperatures, the setpoints have never deviated from 73F.
There is a input parameter in the smartapp that sets the maximum temp adjustment (by default, it’s 5F). It’s called max_temp_diff in the smartapp. So, if you want to adjust the temp for more than 5F, you’d need to set it up accordingly.
BTW, MonitorAndSetEcobeeTemp will not adjust the setpoints in ‘auto’ mode, only in ‘cool’ and ‘heat’ modes as the ‘auto’ mode is more complex to tackle. Only the ecobeeSetZoneWithSchedule (paid) smartapp is able to adjust the setpoints in ‘auto’ mode. as it includes the special logic to do so.
The smartapp has been used by many ST contributors, so I don’t expect any issues at this point with the setpoint adjustment logic.
If you have any issues with the smartapp, please contribute to one of my support packages, and I will look into it. You’d need to send some detailed logs (just for the smartapp) to services@maisonsecomatiq.com.
Regards.
EDIT: MonitorAndSetEcobeeTemp’s latest version (v3.4.9) should work in ‘auto’ mode. Again, MonitorAndSetEcobeeTemp is a basic version of ecobeeSetZoneWithSchedule. If you want more features, please contribute to the right smartapp at my store.
That’s very disappointing to hear. I only use auto mode and when you advertised MonitorAndSetEcobeeTemp having the “follow me” feature, you didn’t say anything about it not working in auto mode (or only working with the paid smartapp). I’ve been struggling to understand what’s been happening throughout this week and why it hasn’t been working based on your responses. It’d have been way less time consuming for me if you had made this clear. And as I said earlier, that’s the one reason why I needed more complex ecobee ST controls and why I got your app in the first place.
You definitely need to make it clear what your different smartapps do since people are actually paying now. You need to make it clear that MonitorAndSetEcobeeTemp had limitations and make clear what those limitations are. Paying customers are owed that.
I thought auto mode was the main way people used the ecobee. In fact, I thought that was a big attraction of smart thermostats as it gives a range vs the thermostat trying to reach a specific level.
Auto mode should be used only in some states (and at some specific times of the year) in the US or Canada where it’s cold in the mornings and hot in the afternoons (in the same day), ex. Arizona/Florida in the winter/spring/fall.
Elsewhere, it’s more efficient to set the thermostat to cool or heat.
Another option you could do if the app update doesn’t do the trick is to have webCore flip between heat/cool based on some external parameter (i.e. temp from Weather Underground). I wanted to use Auto with Ecobee also but I found too many cases where I wanted the heat and cool set points too close together which risks toggling the AC compressor a lot.
Just a heads up, I get an “unexpected error occurred” when I run the new code. When I revert back to the old, it works fine. Seems it has something to do with the if (ecobeeMode in [‘cool’,‘auto’]) . When I revert that back to if (ecobeeMode == ‘cool’), it works fine.
. Please how do I get this working?