Is there a driver out there for the Honeywell Wi-Fi Smart Thermostat?

[tom]

Any new info on this Thermostat, I am using it in my house. Would be nice to integrate with my CQC setup.

[kfly]

Any new info on this Thermostat, I am using it in my house. Would be nice to integrate with my CQC setup.

+1
These Honeywell Wi-Fi Thermostats are great. Much higher end and more reliable than my old Z-wave thermostats. looks like they use the "Total Comfort API" so should be easy to create a driver.

Samples for reference:
https://github.com/lgkahn/honeywelltotal...omfort.txt

and
https://github.com/ethomasii/honeywell-s...ell.groovy

Here is a good forum desiccation on how to interface with them

[Ron Haley]

What are the best options for wifi thermostats for CQC. Currently I control everything with CQC and Elk, but have a location I can't hard wire to the elk so looking for a CQC solution. Not interested in a "smart" thermostat

[Dean Roddey]

We have the Venstar ones, which are IP based and all local.

If someone wants to expose one of the Honeywells I could look at doing a driver for those as well, but the Venstar ones already are there.

[potts.mike]

Whats the status on ecobees?

[Dean Roddey]

There is a third party driver currently. There again, if someone would open one up to me, I could update that and make a V2 compatible version of it, as long as the protocol docs are available.

[kfly]

We have the Venstar ones, which are IP based and all local.

If someone wants to expose one of the Honeywells I could look at doing a driver for those as well, but the Venstar ones already are there.

Dean, 
Through stupidity on my part(ebay bidding on 2 items and forgot) I have an extra Honeywell Wifi Thermostat.
https://www.amazon.com/Honeywell-TH9320W...0166QE9QC/

If you want it you can have it.
If you don't replace one of your home Thermostats(that are powered)  you will need a 24V AC power supply to run stand alone.

[Dean Roddey]

They use that stupid OAuth scheme. As best I can tell it is completely oriented towards phone applications, and there's no practical way for us to use it. The same came up with a Carrier HVAC system.

It assumes you are running some cloud based phone application. You go to a URL on the product vendor's site, with an id that indentifies which 'app' you are authorizing. That 'app' has to provide a URL to some server that the product vendor's server will call with information once you approve that app's access to your product. That server then has to use to complete the authorization process, which presumably it stores in your 'account' on that server for later use when your phone application connects to it (and to make it as convenient as possible for hackers to get the info required to access your stuff.)

We don't have any such thing, so we have no way to use their authorization scheme. And it requires that we register our 'app' as well, which doesn't exist because there is no app.

It's so stupid. I don't know why so many people use it. So, anyway, no, we can't do a driver for that since we can't do the authorization scheme because it's completely hostile to automation systems.

Nest uses a variation on this that doesn't require the redirect URL, so we can use that one. In the first step, instead of redirecting you, they just show you a PIN number. You can then provide that to your automation system or app or whatever, and it can complete the process to get the required authorization info. That's actually safer and far more sane to me, and I don't know why people don't use it.

[Dean Roddey]

I sent them a whiny request to at least support the alternative scheme, else we could only recommend our customers look elsewhere.