Missing entities on some SRT321 devices

[gsemet]

The problem

Please see the detailed report on the forum. In a nutshell, I have 4 SRT321 devices, that works fine, I can enable/disable them, set the setpoint, and so on.

They are thermostat that controls qubino flush pilot on/off activator to control heater.

But some displays correctly the heater activation

while other does not

I have seen that the ones that display the heater activation correctly are seen as "SRT321 by Secure Meters (UK) Ltd.
"
while the ones without this information are seen as “HRT4-ZW / SRT321 by Secure Meters (UK) Ltd.”

What entity I see missing in "HRT4-ZW / SRT321" is the "Node status" entity
compared to "SRT321" (this only shows the device awakes every 10 minutes.

but in the zwave js, i see that the good ones exposes "[119-66-0-state] Operating state" that seems to be the linked to the heater activation.

In the bad ones, I do not see this state. Not sure if this is a zwavejs bug, a firmware bug, or a display issue in home assistant

I have the flush pilot devices in home assistant, would it be possible to link this information in the climate device to the on/off state of the device?

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

zwavejs

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[gsemet]

Bug also opened in zwavejs

[kpine]

In the bad ones, I do not see this state. Not sure if this is a zwavejs bug, a firmware bug, or a display issue in home assistant

It most likely means your device does not support that command class, which provides the ability to report the operating state, thus HA does not know whether it's heating or idle and cannot implement the hvac_action attribute. It's the same thing I explained in #133357.

You can try re-interviewing the affected devices, but if the Thermostat Operating State is not shown in ZUI after that, there's nothing that can be done from the HA side as it relies on that to value (provided by Z-Wave JS) to implement the hvac_action attribute.