Thermostat SRT-321 has no BinarySwitch and ThermostatMode states

[sucesor]

Versions:

• Adapter version: 3.0.5
• JS-Controller version: 4.0.24
• Node version: 8.16.0
• Operating system: Linux Debian 11

Thermostat SRT-321 has no BinarySwitch and ThermostatMode states however when I used ioBroker.zwave adapter those states were available and the device supports the appropriate classes https://products.z-wavealliance.org/products/1563/classes

Device:

• Manufacturer / Model: Secure SRT-321
• Node numbers:
• manufacturerId: 0x059
• productType: 1
• productId: 3
• firmwareVersions: 6.0

Logfile of an interview:
zwavejs_2023-06-19.log

[AlCalzone]

You have the 300 series version of the device, the link you posted is for the newer 500 series version (product ID 5). So the information on that page is not 100% reliable.

We will have to force-add these two missing CCs through a config file, as the device does not report support for those during the interview.

[sucesor]

Thank you for the response.
I have initiated "Refresh Node Info" using open-zwave control panel which is similar to zwave js interview process.
It seems the device provides appropriate classes support information by specific request.
Please take a look at the ozwcp.log
Hope it will help to get a better result.
ozwcp.log

[AlCalzone]

I see - the device reports both these classes as controlled (can control the CC in other devices), which does not mean that it supports (other devices can control the CC in this one) them.

Just to be clear, you were able to control the device using those states in ioBroker before?

[sucesor]

No, I could not control the device using these states, however, I was able to handle the events of these states in order to control the behavior of the actuators.

[AlCalzone]

Oh, now it starts to make sense. Can you capture another log where you turn the thermostat on or off?

[sucesor]

Sure, not a problem.
I'd like to clarify, what is the exact type of log you need zwave-js on open-zwave?

[AlCalzone]

zwave-js. I'd like to see what exactly it sends and how zwave-js reacts.

[sucesor]

Done.
Please, pay attention that node numbers were changed. So, Node0002 now is thermostat SRT-321
zwavejs_2023-06-20.log

[AlCalzone]

Thanks. I'll have to see how to best handle this, since the thermostat sends controlling commands (SET, not REPORT), which we don't simply interpret as reports like OZW used to do.