Skip to content
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

Closed
jceloria opened this issue Aug 31, 2016 · 11 comments
Closed

Z-Wave/climate shows incorrect values for Honeywell TH8320ZW1000 #3070

jceloria opened this issue Aug 31, 2016 · 11 comments

Comments

@jceloria
Copy link

jceloria commented Aug 31, 2016

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:
screen shot 2016-08-31 at 9 58 01 am

Before applying commit 17a7678, values showed "null"

Additional info:
zwcfg: https://gist.github.com/4b7fb35e9769ea577340d432d3166aa1

@turbokongen
Copy link
Contributor

You should really do 0.27.1 before we go any further with this.

@turbokongen
Copy link
Contributor

turbokongen commented Aug 31, 2016

Sorry, It's not released yet, but when you want to test, you must take all the commits of the pr to test the changes made, not only the last. There is two Prs for the zwave fix #3017 and #3023
You need to apply both.

@jceloria
Copy link
Author

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.
$─► hass --version
0.27.1

$─► curl -X GET -H "Content-Type: application/json" http://localhost:8123/api/states | jq '.[]|select(.entity_id|contains("thermostat_"))|{entity_id, state}'
{
"entity_id": "climate.thermostat_furnace_5",
"state": "165.20000000000002"
}
{
"entity_id": "climate.thermostat_cooling_1_5",
"state": "165.20000000000002"
}
{
"entity_id": "sensor.thermostat_temperature_5",
"state": "74.0"
}
{
"entity_id": "climate.thermostat_dry_air_5",
"state": "165.20000000000002"
}
{
"entity_id": "climate.thermostat_heating_1_5",
"state": "165.20000000000002"
}

@turbokongen
Copy link
Contributor

turbokongen commented Aug 31, 2016

Can you provide the state attributes for the climate.thermostat_cooling_1

@jceloria
Copy link
Author

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"
}

@turbokongen
Copy link
Contributor

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.
Ha uses the setpoint to get unit_of_measurement.
I will make a small adjustement, as I see It can be improved to be fetched on per setpoint basis.

@turbokongen
Copy link
Contributor

Please test the commit :D

@jceloria
Copy link
Author

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:
https://gist.github.com/d3faa9dc877c33b5f517ec38ffe4dbc1

@turbokongen
Copy link
Contributor

A new commit to test

@jceloria
Copy link
Author

Looking good!

Thank you for your work on this, you and the other devs rock.

@turbokongen
Copy link
Contributor

👍

@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants