Closed thedanbob closed 5 years ago
Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave
) you are listed as a codeowner for? Thanks!
I think you need to exclude and include the device again. If you look at the zwave
entity you should see the model of the device pulled in, instead of it saying unknown like it is. Also check the user manual and ensure you have it in the right operation. I remember I had to adjust mine too get it to function properly.
No change unfortunately, even after I factory reset the thermostat. There doesn’t seem to be any z-wave settings I can change on it, just include/exclude.
Read the manual, there's a way to change the operation with some code. It's not a zwave setting. It's like a device programming setting.
I've tried changing some of the settings but nothing fixes the issue. There's one operation mode "cool only" that I could see causing this behavior but I don't have it set to that. The manual has all the advanced settings on pg. 15-19 if you're interested: https://forwardthinking.honeywellhome.com/pdfs/T6_Pro_Z-Wave_Install_Guide_33-00294.pdf
Edit: I reread your comment above, do you have a T6 Pro as well? You wouldn't happen to remember which setting did the trick for you?
I dont have the t6 I have a 8320.....i dont remember the exact setting but I remember that my heater did not work properly from the device itself.
Make sure when you pair the thermostat that the zwave
entity has the correct model and product name. See how mine does:
I’ve tried several combinations of settings but I can’t get any of them to show the model name or set the heat setpoint. I really think this is a bug in either HA or my thermostat.
HA is missing the device config for the T6. You can grab it from OZW 1.4 or I also have a fork with the HA configs and missing 1.4 configs. One thing the XML file does is override the setpoint base index to 0 (from the default of 1). That will affect how the setpoints are detected. You'll probably want to at minimum grab the config file, install it in your HA config (updating manufacturer_specific.xml), then remove and re-add the node and see how it's working.
If you search the community forums you'll find people who have gotten it to work. For example, this post describes how they installed the XML file using the above instructions. I would recommend downloading the files into a directory in your /config and use the config_path
setting to avoid HA updates reverting it.
You can also test out your thermostat with OZW 1.6. If it works there, than it's most likely an OZW 1.4 problem, and there's not much you can do about that except wait until HA updates to use OZW 1.6 (which is a work in progress). If you use docker, you can easily test it with openzwave/openzwave-control-panel.
Fantastic! My first thought was that the zwave config for the T6 was missing, but I then I saw openzwave had a file for it. I just didn't realize HA had its own fork of openzwave with different configs. I've added the config files from your fork and it works perfectly now.
Home Assistant release with the issue:
0.102.2 and 0.102.0.dev.20191128
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on linux
Integration:
https://www.home-assistant.io/integrations/zwave/
Description of problem:
I have a Honeywell T6 Pro z-wave thermostat (https://products.z-wavealliance.org/products/2893) which I'm trying to configure in HA. In 0.102.2, I see the following entities:
Configuring
cooling_1
as a thermostat allows me to change the hvac_mode, turn the fan on and off, and change the setpoint on cool mode, but not on heat mode. None of the other entities let me change the heat setpoint either.In 0.102.0.dev.20191128 with this PR merged I see the following entities:
I believe
mode
is supposed to combine the heat and cool setpoints but it has the same behavior, I can't change the heat setpoint.Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: Climate entities in 0.102.2: Climate entities in 0.102.0.dev.20191128: