-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T5800 support #4
Comments
That looks like the right thing to do. Can you submit a pull request? It'd be good if there were a comment in there indicating it was due to the keys missing on a T5800. @Cinntax probably cares about this for home-assistant. |
Oh nice- the more the merrier. Also, we're discussing it here: A couple of things:
|
As far as I know, anything humidity related is pretty much the only thing that is not supported for the T5800 model. A yaml config variable sounds good to me. I'm not sure what other thermostat models (if any) would be the same as mine. |
Okay cool- actually, as I got to putting the "flag" in the hass component, I thought it might be cleaner if we have the library "tell" the component what it supports. So i'm thinking i can modify the library here to put a "supports humidity" or something of that nature, and it will return true if the thermostat supports it, and it's enabled. |
I've pushed 0.4 to pypi with changes from @rbebeau. |
I assume this issue has been resolved so I'm going to close it. |
I have an older Colortouch T5800 that I'd like to use with your code (for HomeAssistant). I noticed a few things that need to be somehow 'optional' for it to work with the T5800:
Example JSON:
$ curl "http://thermostatip/query/info"
{"name":"HOME","mode":3,"state":1,"fan":0,"fanstate":1,"tempunits":0,"schedule":1,"schedulepart":2,"away":0,"spacetemp":65.0,"heattemp":68.0,"cooltemp":80.0,"cooltempmin":65.0,"cooltempmax":99.0,"heattempmin":35.00,"heattempmax":80.0,"setpointdelta":4.0,"availablemodes":0}
I'm attaching a diff that seems to fix these issues.
Thank you for your work!
The text was updated successfully, but these errors were encountered: