-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
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
Z-Wave/climate shows incorrect values for Honeywell TH8320ZW1000 #3070
Comments
You should really do 0.27.1 before we go any further with this. |
I didn't see a release but 0.27.1 does appear to be available... I was able to upgrade. Unfortunately, I'm still seeing the same issue. $─► curl -X GET -H "Content-Type: application/json" http://localhost:8123/api/states | jq '.[]|select(.entity_id|contains("thermostat_"))|{entity_id, state}' |
Can you provide the state attributes for the |
Sure, is this what you are looking for? {
"attributes": {
"current_temperature": 165,
"fan_list": [
"Circulate",
"Auto Low",
"On Low"
],
"fan_mode": "Auto Low",
"friendly_name": "Thermostat Cooling",
"max_temp": 95,
"min_temp": 45,
"node_id": 5,
"operation_list": [
"Cool Econ",
"Off",
"Auto",
"Cool",
"Heat",
"Heat Econ",
"Resume"
],
"operation_mode": "Cool",
"temperature": 165,
"unit_of_measurement": "°F"
},
"entity_id": "climate.thermostat_cooling_1_5",
"last_changed": "2016-08-31T17:50:46.683879+00:00",
"last_updated": "2016-08-31T17:50:46.683879+00:00",
"state": "165.20000000000002"
} |
It looks like a conversion issue. I see that two of your setpoint classes are in Fahreheit, and two in celsius. You should get them matched. Use ozwcp or similar. |
Please test the commit :D |
That's odd, I wonder where the mismatched units came from, I haven't had this thermostat for very long and when setting it up on the touchscreen interface, there was only 1 option for C or F. I have not yet corrected the settings in ozwcp in case you would like me to test more. There were errors: |
A new commit to test |
Looking good! Thank you for your work on this, you and the other devs rock. |
👍 |
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.27.0 with commit 17a7678
Python release (
python3 --version
):3.4.2
Component/platform:
climate/zwave
Description of problem:
Before applying commit 17a7678, values showed "null"
Additional info:
zwcfg: https://gist.github.com/4b7fb35e9769ea577340d432d3166aa1
The text was updated successfully, but these errors were encountered: