Is there a way to pull all the non ecobee motion sensor temps around the house and calculate an average and feed that into ecobee to control hvac? The same way they use their own room sensors ?
It might be worthwhile to ask in some Ecobee forum if there is a way to fool the thermostat into thinking that something external is an Ecobee sensor that actually isn't. Not inconceivable, but I doubt it could be done easily.
Failing that, you could use logic in Hubitat to decide whether you need to call for cool (or heat) and then tell the Ecobee to do it. That is, basically turn your Ecobee into a switch with no intelligence.
But neither of these approaches seem worth pursuing to me. In my opinion, having multiple sensors within the same zone is mostly a gimmick if you can't influence which area gets air flow. That is, if we've decided that setting the hall thermostat to 78 degrees is what it takes to make the house comfortable in every room, then the sensors don't do anything to help that. Just my opinion.
No, which is actually one of the reasons I sold my ecobee and changed to a zwave thermostat that I could bias the temp on. But my use case/need was very specific.
I looked into this when I had my Ecobee. The short answer is no. Trying to take over the logic the Ecobee uses to turn on/off your HVAC is very, very difficult and would require you to adjust the setpoint relative to the observed temperature to control whether the HVAC is cooling, heating or idle.
If you're going to stay with Ecobee, and given the number of server downtimes they've had over the past few months, i don't know why anyone would, I would invest in some of their sensors to use for the thermostat control. You're going to be a lot happier with the reliability and performance that way.
@Ryan780 >
If you're going to stay with Ecobee, and given the number of server downtimes they've had over the past few months, i don't know why anyone would, I would invest in some of their sensors to use for the thermostat control. You're going to be a lot happier with the reliability and performance that way.
I have two of the ecobee, and yes the server down time have been a little annoying, but not so much as ST's were. The main reason i went with them was the remote sensor priority over the main thermostat. With that in mind is there a Zwave alternative you would recommend with the came or similar capability?
Nope, not that I am aware of. That said, there are easier ways to control a directly connected Z-wave thermostat more than an Ecobee. For example, user @JasonJoel modifies the settings on his Go-Control Z-wave thermostat based on a remote temp sensor. I assume that he takes the reading off the remote sensor, compares it to the thermostat sensor and then modifies the offset setting on the Thermostat. But maybe he can give more detail.
CORRECTION:
After looking at the GoControl Z-wave configuration again (that the therm i have) you can set a remote Z-wave temp sensor to be the device's temp sensor. You just have to program the thermostat with the node number of the Z-wave temp sensor you want to use. I don't have any devices that are z-wave and temp sensors so I never tried it out to see how it works. But it is there.
Correct. You can do that, or you can do like I do with the gocontrol and bias the temperature calibration programmatically (that does take a user driver, the inbox driver does not expose the calibration parameter).
The second option allows you to control from any temperature you like (including zigbee). With the caveat that hubitat is doing all of the biasing. So if it crashes your biasing stops.
I assume that if you set a Z-wave remote sensor in the Thermostat itself, that will be the thermostats temp reading and it will function independent of HE, correct?
Yes, that is how it is supposed to work. I messed with it a little when installing my 4 thermostats, but did not test it thoroughly.
