core: HA light entity breaks with zwave-js 7.0.0+ (zwavejs2mqtt addon 0.9.0+)
The problem
Upon upgrading zwavejs2mqtt addon from 0.8.1 to 0.9.0, HA can no longer control the dimmer on my ZEN30 combo (relay/switch still works fine).
Looking at the entities for this device in the Z-Wave JS integration, it appears that the original light entity is now in “Unavailable” status, and a new light entity was created. This new entity does not work, e.g. state doesn’t change. The original and new light entities from core.entity_registry config file are shown below.
Z-Wave communication with the device is working fine. I can control the dimmer from the zwavejs2mqtt Control Panel, and there I can also see debug value changes when I manually operate the dimmer.
When I roll back to addon version 0.8.1, the original light entity works again.
What is version of Home Assistant Core has the issue?
core-2021.3.4
What was the last working version of Home Assistant Core?
core-2021.3.4
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Z-Wave JS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
I haven't noticed anything unusual in the HA logs or the zwavejs2mqtt addon log, but let me know if there's a specific thing I can go and check for more information.
core.entity_registry light entities:
{
"entity_id": "light.downstairs_toilet_vanity_new",
"config_entry_id": "7581b37606e52da2f5da9b3e01fbd7ff",
"device_id": "340a83ba4f5bdf882d468693f6748c89",
"area_id": null,
"unique_id": "3578726706.72-38-1-currentValue",
"platform": "zwave_js",
"name": "Downstairs Toilet Vanity Light NEW doesn't work",
"icon": null,
"disabled_by": null,
"capabilities": {},
"supported_features": 33,
"device_class": null,
"unit_of_measurement": null,
"original_name": "DownstairsToiletCombo",
"original_icon": null
},
{
"entity_id": "light.downstairs_toilet_vanity_original",
"config_entry_id": "7581b37606e52da2f5da9b3e01fbd7ff",
"device_id": "340a83ba4f5bdf882d468693f6748c89",
"area_id": null,
"unique_id": "3578726706.72-38-0-currentValue",
"platform": "zwave_js",
"name": "Downstairs Toilet Vanity Light ORIGINAL used to work now Unavailable",
"icon": null,
"disabled_by": null,
"capabilities": {},
"supported_features": 33,
"device_class": null,
"unit_of_measurement": null,
"original_name": "DownstairsToiletCombo",
"original_icon": null
}
Here is a truncated Z-Wave JS network dump file, only showing the controller and the node in question (node 72): zwave_js_dump_truncated.json.txt
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (3 by maintainers)
It may be related to https://github.com/zwave-js/node-zwave-js/issues/2286 The change causing this issue was reverted in Z-Wave JS 7.2.0 (https://github.com/zwave-js/node-zwave-js/pull/2288). Now waiting for the the Z-Wave JS Home Assistant add-on to be bumped to 7.2.0+ to see if it works again.
It is fixed in zwavejs2mqtt: 3.3.0 zwave-js: 7.2.2 I had to manually re-interview the nodes.
I have four of these devices (Zen 30) and have ran into the same issue after updating zwavejs2mqtt to 3.2.0. In the control panel I can still turn the lights on and off (dimming doesn’t seem to be an option) but the integration into HA states the lights are unavailable.
I’m experiencing the exact same issue with my 3 Qubino ZMNHJD, starting with zwavejs2mqtt 0.9.0. Reverting to 0.8.1 also fixes the issue for me. I can provide additional logs if needed.