Thermostats - Have a Nest thinking of upgrading to Ecobee

Hi,
I have had a Nest Thermostat since they were released, but not too happy that I can't connect it to Hubitat and control it with triggers and events in Rule Machine.

Nor do I want to setup Github to control my Nest.

Any advice - on whether Ecobee is the way to go or not, or are these thermostat connections all still maturing and should I wait.

Thanks
David

So I still have the "official" HE nest integration app before they took it down and it works with both my Nests with no github required.. :grin:. You do have to have a Nest developer account already established to get it to work though..

Unfortunately I haven't really done anything with it yet - do you have any specific things in mind? The Nests (for me) pretty much do everything on their own.

If you want to completely control your own thermostat experience then something like the Remotec ZTS-500 or Centralite Pearl might be worth checking out.

(you might find better deals on EBay)

Do you have a link to this Nest Integration app, I would love to get my hands on it.
I was looking at incorporating the nest into my home automation.

For example using Multi Sensors to trigger an increase in temperature if the room I am in isn't at a comfortable temperature.

The ability to see the Nest Temp on my dashboard and adjust it up or down if needed. Tie the Nest into Away settings on Hubitat automatically.

Really, just have a Thermostat and eventually the Protect Fire/CO2 detectors part of the ecosystem instead of standalone.

I have 2 Ecobee 4s. I bought them for the remote sensors and they've performed great. They have a very high WAF --so much so, that I'm hesitant to integrate them with HE. As is, I don't have to get involved, wife runs everything from the app.

As you mentioned, it feels like thermostats are still evolving with HE. I see some here using the Centralite Pearl. If I didn't have the Ecobees, I'd likely try the Pearl with HE.

1 Like

So I am using the Pearls for our heated floors. Thought a Nest or other smart thermostat would be overkill in that situation.

I'll have 3 ecobee 3, 1 ecobee 3 lite, and 12 or so sensors for sale shortly.

Just have to put in my other 3 ZTS-500s.

What made you transition to the ZTS-500?

HE removed the Nest integration app on the last upgrade. It wouldn't work anyway without the developer account. I thought @tonesto7 was porting his app over not sure where that stands.

Have been a number of cloud outages/issues with ecobee lately, which is a big deal to me as I use the thermostats operatingState in a number of automations.

So wanted to move to something 100% local.

1 Like

Also didn't you mention in another thread how fast and configurable the ZTS-500's are.. as well as maybe cheaply made though.

Any reason you didn't choose the centralite pearl... just curious.

David

I only have one of them so far, and I will say the build quality was pretty poor. I was able to insert a couple spacers to make it work correctly, but out of the box the buttons would get stuck ramping the temperature down to minimum all the time. :slight_smile:

I have three more sitting on my desk for when I get home later this week, I'm kind of hoping that they are a little bit better. But if not I know how to put spacers in the plastic to make it work adequately.

The update speed is basically instantaneous since it's a local zwave plus device. And since you can adjust the sensor calibration programmatically, I wrote a program to continually update the temperature bias to match an external temp sensor. Thus making it control off of the remote sensor effectively.

1 Like

yes. I believe that you can't continuously adjust the temperature calibration on the Pearl. I wanted to basically run off of an external temperature sensor, so needed the ZTS' ability to continually adjust the sensor calibration to make it match the external sensor.

oh, and I prefer Z-Wave devices in general. I'm pretty adept at writing drivers for Z-Wave devices at this point.

zigbee can be a lot more difficult because of the variable structure and parameters used by different vendors. That doesn't mean zigbee is bad, but it does take more work to write drivers for.

From the pics the Remotecs look great at least and I guess you don't really have to fiddle with them manually all that much.

the family likes how the ZTS looks. And now that I put some rubber spacers in and the buttons don't stick, local control works just fine again.

I'm very curious to see how the other three I ordered are going to be. With only one data point it's hard for me to decide whether the build quality is really poor, or if I just got a weird one.

1 Like

Cool let me/us know!!! I am interested in maybe replacing one or both of my Pearls..

Will do. One thing I can attest to, the ZTS driver is in excellent shape.

While I was adding the last few features in this weekend, I went through every single feature in every single combination while debugging the code and optimizing it.

Seems like everything's in very good working order at this point.

There is one feature not added yet, which is the temperature Delta w for second stage heating and cooling to kick on. I might add that in at some point (is easy to do), but I do not have multi-stage units so I can't really test it.

I have:

  1. ecobee lite3 (with remote)
    High WAF and user (me)AF. I needed them for the ability to control from the remote sensor. Works fine. Don't use the app and only log into the website when I'm bored.

  2. Honeywell Zwave and Pearl Zigbee.

Both the Honeywell and Pearl work find. And because they connect right to the hub all the HE rules go right to the thermostat (no internet involved).
Ii understand correctly the ecobee integration will be going through the ecobee website (not sure of this)

Personally if I were mostly interested in controlling by HE with rules, modes etc I would go to a thermostat that pairs directly to HE.

I'm on the going local train. I've removed one Ecobee 3 lite thermostat and replaced it with the Pearl. I have one more to replace. If you want to rely on Ecobee scheduling and not integrate (or minimally integrate) to HE, then it's a viable option. If you want tighter integration with HE, stay away from Ecobee. Their cloud services are incredibly unreliable and that's required for their API. Effectively, their stuff has been down as much as it has been up, lately. I'm very happy with the Pearl at that price point.

1 Like

I have three Nest 3 Lite thermostats and Inlive them. They work great with Hubitat and SmartThings and as said before super high WAF. With the 4 out now you can find the 3 versions pretty cheap.

I should add that my experience doesn’t match that noted above. In the 2 years I have had my ecobee 3 the cloud service has only been down maybe twice and the response time has been nearly instant. Of course as always, your experience may vary.