HRT4-ZW/SRT321 Thermostat expose ONLY 'Heat' HVAC Mode and not Setpoint update

[Chilgl0rd]

The problem

HRT4-ZW/SRT321 have multiple thermostat mode (Off, Heat, Cool, Auto...) but ZWave JS only extract Heat mode and not sync the hvac status. It should be at least Off/Heat Plus, Action Set Temperature or Action ZWave Set a value doesn't work. I try with an other type of thermostat (Heatit) and it worked

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js

Diagnostics information

It works only via Z Wave JS GUI but not via Actions

10/10/2024, 9:22:57 PM - value updated Arg 0: └─commandClassName: Thermostat Setpoint └─commandClass: 67 └─property: setpoint └─propertyKey: 1 └─endpoint: 0 └─newValue: 14 └─prevValue: 18 └─propertyName: setpoint └─propertyKeyName: Heating

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

It seems to be action issue only with this device and this device is not configured properly with simple climate with heat/Off but with climate with heat only and an additional switch for on/off And the action set temperature is not coded correctly

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[MartinHjelmare]

Please download diagnostics of your Z-Wave device and attach it as a text file here by dragging and dropping the file in a comment.

The diagnostics tool is available by clicking the three dots menu of the Z-Wave device in the device page in the Home Assistant GUI.

The device diagnostics will help us troubleshoot your device.

Thanks!

[Chilgl0rd]

config_entry-zwave_js-612b85679413239739021c48bdda96e4.zip Hello @MartinHjelmare Please find the diag file here. It is the device 129, I did some extra tests yesterday. It worked correcly last winter. It is strange now, the ZWave integeration created a switch instead of HVAC Status in climate... Thanks !! Xtof

[MartinHjelmare]

Please provide the diagnostics of the device in question. We don't need the whole integration config entry diagnostics. The device diagnostics can be found under the three-dots menu in your screenshot. You can upload the json file directly without zipping it.

[Chilgl0rd]

zwave_js-612b85679413239739021c48bdda96e4-Climate Control Office-ebc06c3eb3e42406cdcd6d9153e2cbdd.json

[MartinHjelmare]

The Thermostat Mode command class value in your diagnostics dump doesn't have any metadata. Any mode beyond heat need to be present in the metadata of that command class value for Home Assistant to know that it should support additional modes.

Additionally there's only one Thermostat Setpoint command class value (heating) in the dump. So there's no indication in the diagnostics that the device should support anything else than heating, as far as I can tell.

I'd try re-interviewing the device. If that doesn't help you can open an issue in the driver project at: https://github.com/zwave-js/node-zwave-js/issues

and provide this dump and a debug level driver log of an interview of the device.

https://www.home-assistant.io/integrations/zwave_js/#how-do-i-access-the-z-wave-logs

[Chilgl0rd]

I already re*interviewed the device without more chance. When i look at the zwave nodes I can see that values At least "Off" should appear. And why the set temperature command doesn't work ?

[Chilgl0rd]

I also excluded/included. It worked fine last year :-/

[MartinHjelmare]

As I said, those other modes are not listed in the metadata of the Thermostat Mode command class value in the diagnostics. I don't know why that is.

I suggest you open an issue with the driver project as suggested above.