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
OZW climate - not treatning Danfoss Z Thermostat as a climate entity (Setpoint thermostat) #36541
Comments
ozw documentation |
My Honeywell thermostat has the same issue. It's detecting the air temp as a sensor but nothing else. Running HA version 0.110.6 |
Climate entities are not available in 0.110. You need to use the 0.111 beta. |
I’m aware of that. Are running: Home Assistant Core release with the issue: Home Assistant 0.111.0b2 |
That was a reply to @natwilson.
|
Currently running 0.111.0 stable and my Popp Radiator Thermostat (reporting as a Danfoss Living Connect Z) also doesn't report a SetPoint value. |
I'm getting both issues - missing set point on danfoss rad stats and missing set point on Horstmann Thermostat - on 111.4. The rads are identified as danfoss devices but only the battery sensor is detected. For the thermostat, the device is no correctly identified. I can see the temperature sensor and battery sensor. EDIT: On deeper inspection: the Hortstmann thermostat is not being recognised by OpenZWave. It's just recorded as a node with the entities but no device description. I'll raise this as a separate issue in the addons repo. OpenZWave is reporting stat changes correctly(seen in the MQTT datastream)
The ozw integration is seeing the change
But it's not appearing as an entity in the device |
If this issue still exists (thermostat not recognized as climate device in hass), it would be great if we receive an mqtt dump from your setup. |
@marcelveldt Was there any change to this function or component since 0.111.0? Which was the last time I've tested it out. I had a very similar dump to @dkjsj one. Maybe that dump is still sufficient to fix this issue? |
Here you go. Node 7 is a Danfoss
|
I am also seeing this exact same error using the OpenZWave (beta) and Open Z-Wave Daemon (version 1.0.17). Running HA 0.112.3. I have 6 Danfoss TRV, being recognised as danfoss_living_connect_z_v1_06_014g0013 (although sometimes just being recognised as Z_thermostat or similar). Happy to delete any / all TRVs / factory reset etc and start again if it helps bring back the climate entity. Like the others, I am only seeing the battery level. Is there any way of turning on logging to file for the ozwdaemon to send over some logs, if that would help debug the issue? |
We prefer mqtt dumps from the ozw daemon topic |
Here is 60 seconds of logs |
mqtt_dump.txt |
Thanks for the mqtt dumps, I'll take a look what I can find. |
@marcelveldt Thanks very much for the work in the PR! Is there anything else you need in terms of logs etc from me to get it approved, or will it just get merged when the time comes? Cheers |
The problem
Latest Beta is not finding Danfoss Z Thermostat as a Climate Entity.
Information regarding the node:
and Command Class 67:
Any idea why it isn't picked up as a climate entity (Setpoint thermostat)? I've attached the mqtt.dump - but I'm not sure the data are in the file.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: