Changes to thermostat endpoint to value mapping in zwave-js 7.0.0

Checklist:

• I am not using HomeAssistant. Or: a developer has told me to come here.
• I am not using ZWaveJS2MQTT. Or: a developer has told me to come here.
• 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

It seems that in some cases, upgrading to zwave-js 7.0.0 results in different command classes being reported on different endpoints of the thermostat. In the example state dump provided below, the Thermostat Setpoint CC is on endpoint 0, but the Thermostat Mode CC and Multilevel Sensor CC values are on endpoints 1 and 2. Is this expected behavior?

Note that I was able to reproduce this when I upgraded but a re-interview resolved the issues I saw (by that I mean that all of the command classes ended up on endpoint 1).

I don’t think this is specific to zwave-js-server because in the server logic we simply dump the values that zwave-js provides.

Related issues: https://github.com/home-assistant/addons/issues/1943 https://community.home-assistant.io/t/do-not-update-to-the-z-wave-js-version-0-1-14/293400

Device information

Which device(s) is/are affected (make/model)? Radio Thermostat CT100 and CT101 (dump is from CT101 and is from another user, I did not think to take a dump) What are the node IDs? 4 and 8

Did you change anything?

• Yes: (please describe)
• No

Did this use to work before?

• Don’t know, this is a new device
• No, it never worked anywhere
• Yes, in: 6.6.x

How are you using node-zwave-js

• zwavejs2mqtt (latest) docker image
• zwavejs2mqtt (dev) docker image
• zwavejs2mqtt Manual Docker build
  • node-zwave-js branch:
  • zwavejs2mqtt branch:
• ioBroker.zwave2 adapter
• HomeAssistant version 2021.3.4 with the zwave-js-server core addon v0.1.14 (https://github.com/home-assistant/addons/tree/master/zwave_js)
• Pkg
• Manual Docker build
  • node-zwave-js branch:
  • zwavejs2mqtt branch:
• node-red-contrib-zwave-js
  • Module version (double click node):
• Manually built (as described in the docs)
• Other:

To Reproduce

Steps to reproduce the behavior:

1. Start with a version of zwave-js < 7.0.0 (must have a thermostat)
2. Upgrade to zwave-js 7.0.0 (don’t wipe your existing cache before doing this)
3. Observe the value to endpoint mappings

Additional context

Add any other context about the problem here.

Logfile:

I wasn’t able to get a logfile dump from the user but will ask. In the meantime I have the state dump of two nodes from the same user. thermostat.json.txt thermostat2.json.txt

[AlCalzone]

That’s because the values weren’t actually queried in 7.x, so they were not created if they didn’t exist.

[AlCalzone]

https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/docker_custom_builds