zwave-js: Device (Heatit thermostat) doesn't report binary switch as it should with updated firmware
Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
Checklist
-
I have checked the troubleshooting section and my problem is not described there.
-
I have read the changelog and my problem was not mentioned there.
Describe the bug
What causes the bug? Unclear. Maybe the device was set up using documentation of a previous firmware version of the device that didn’t support the binary switch?
What do you observe? The thermostat reports setpoints as expected, but the new firmware is also capable of reporting wether or not the relay is open which is the feature I want.
What did you expect to happen? That binary switch for heating status is correctly reported
Steps to reproduce the behavior: I’ve tried re-interviewing the nodes multiple time. I’ve got two identical thermostats. They reported correctly using Homeseers implementation so I know it’s actually possible.
I turn up the setpoint above current temperature, see the red LED-indicator light up, and look for changes in the events tab, but all I get is the new setpoint.
I have attached the documentation of this firmware version if that could be of any use.
Device information
Manufacturer: HeatIt Model name: Z-trm2fx Firmware: 1.92 Node ID in your network: 96
It’s added as “Thermofloor Thermostat TF016 / TF021” in Zwavejs2mqtt
How are you using node-zwave-js?
-
zwavejs2mqttDocker image (latest) -
zwavejs2mqttDocker image (dev) -
zwavejs2mqttDocker manually built (please specify branches) -
ioBroker.zwave2adapter (please specify version) -
HomeAssistant zwave_jsintegration (please specify version) -
pkg -
node-red-contrib-zwave-js(please specify version, double click node to find out) - Manually built from GitHub (please specify branch)
- Other (please describe)
Which branches or versions?
version:
node-zwave-js branch:
zwavejs2mqtt branch:
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
No, it never worked anywhere
If yes, where did it work?
It worked in Homeseer before I migrated to zwavejs2mqtt and Homeassistant
Attach Driver Logfile
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 17 (10 by maintainers)
The thermostat is using a
BinarySwitchCCSetwhich is meant to control a binary switch and not to report status. See manual:According to the manual, there is another association group on Endpoint 1, which uses Basic Report commands to do the same. This sounds like a better fit:
I’m not sure how this one is labeled though, since we don’t have any associations defined for the endpoints in the config file.
You do seem to have a few duplicated associations though. The controller doesn’t have any endpoints, so specifying a different target endpoint than “None” (or 0 for some lifelines) just results in duplicate reports.