Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Investigate duplication of S0 nonces in Thermofloor Z-TRM3 thermostat

See original GitHub issue

Version

Build/Run method

Docker
PKG
Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.2.1 zwavejs version: 6.4.0 Home Assistant Core (in Docker) 2021.2.3 Thermofloor Z-TRM3 thermostat firmware version 4.0.33 (config/devices/0x019b/z-trm3.json)

Describe the bug

My Z-TRM3 thermostat (climate entity) is no longer visible in Home Assistant. It was visible and working with version 1.1.1. The device that should have the climate entity is available, but all of the temperature sensors are shown as unavailable.

To Reproduce

Steps to reproduce the behavior:

Go to ‘Thermostat device in Home Assistant’
Click on ‘Climate’ entity (it was loaded from cache)
See error message about the device being unavailable.

Expected behavior

The climate entity should be detected and it should have the correct current setpoint and current temperature of the specified temperature sensor (based on the [10-112-0-2] Sensor mode).

This last thing about the correct temperature sensor being used has never worked, even in previous versions. It would always use the sensor [10-49-2-Air temperature] (which is the first in the list).

Additional context

When I start up zwavejs2mqtt 1.2.1 I get this message twice (I have two Z-TRM3 thermostats):

Unable to discover climate device, there is no valid temperature valueId

This seems to be related to https://github.com/zwave-js/node-zwave-js/issues/1184 which added compat values for CC 0x31 to the definition of z-trm3.json.

If I removed all of those compat additions to z-trm3.json from that issue, then all of the temperature sensors show up in Home Assistant, and the error message mentioned above is no longer shown, but the climate entity is still not detected.

I even went as far as fully re-interviewing the node, removing the device and all the entities (manually) in Home Assistant to ensure it was fully detected again. I also stopped HA and zwavejs2mqtt, let zwavejs2mqtt start up fully before I restarted HA, but still no dice.

My only solution to get the climate entity back to working was to downgrade zwavejs2mqtt to version 1.1.1.

I didn’t see anything in the release notes between 1.1.1 and 1.2.1 that indicates that work was done on anything thermostat-related, so this might be related to something else causing action at a distance.

One last note of relevance; if I keep the compat changes (0x31 CC) made to z-trm3.json mentioned above, but only downgrade to 1.1.1, the climate entity shows up in HA, but the current temperature value is unavailable. This seems to indicate that here might be two (or potentially three, if we count the wrong temperature sensor being used) inter-related issues at play here.