Running OH 4.1.2. Running Zwave devices mostly. I already have a Nest thermostat (model 1.4) gotten before starting with OH, on one of my home’s zones, want to add another thermostat for the other zone. We can program and control the Nest through the Google Home app. Will the Nest binding work with this thermostat? Next thermostat purchase does not need to be a Nest device, any suggestions for a OH friendly thermostat and/or just working with thermostats in OH in general?
There’s a binding for the Ecobee thermostats. But I’m not sure of the availability outside the US and Canada.
I’m a big fan (and contributor to the binding) of Venstar, they expose a local, secure, and documented REST API endpoint, so no cloud required! Wish all vendors were so developer friendly. I have 5 of them, not had a single issue. Not sure if they are available outside the US.
I’m not super pleased with the Honeywell T6 Pro Z-Wave but it works ok with the OH z-wave plugin.
See Honeywell T6 Pro Z-Wave (TH6320ZW2007) - #3 by smitopher
Is this still a good recommendation a year later? I’m needing to replace 5(!) Nest thermostats that are about to become colorful dumb thermostats. I’m in the U.S.
And is there any smart-capability reason to get the ColorTouch model instead of the Explorer Mini, or one of the other wifi-enabled models? I’d rather have the smaller wall footprint and lower price.
Hmm, i have not seen the Mini before, but looks like a great unit actually, and still supports the full local API which i love that they prominently call out on the main product page. That seems like a great option (and looks similar to their commercial units you see a lot in hotels) . If there is any changes to the API (i doubt it, but you never know) we can update the venstar binding to be compatible, but i’m guessing this works out of the box given the docs on it.
Sweet!
So i just checked, and we are specifically looking for a color touch thermostat when trying to discover it on the network. I can fix that and update the binding to support the mini and any other venstar api thermostat ( the color was the only API enabled one when we wrote the binding.)
That being said, you can manually add a “Color Touch Thermostat” thing and configure it with the mini’s ip and it will work, it’s just a limitation on auto discovery. I’ll probably refactor the binding to have a generic “Thermostat” thing instead, and the current “Color Touch” will just be an alias to this since the control is all the same regardless of model.
If you do end up ordering them, let me know and i’ll make those changes, should be pretty small.
My wife decided she liked the ColorTouch better, so we’re going with that. But also, I don’t ever do autodiscovery anyway. I think it would be a good long-term project to have the binding be device-agnostic, though.