core: Since HA Core 2023.11.1 Z-Wave Become Unavailable

The problem

Since i have installed the core 2023.11.1 (and also with the core 2023.12.1) when pressing buttons on my MCO switches the z-wave newtwork became unavailable and it restarts by randomly turning on lights. This happens everytime a physical button from MCO Touch panel is pressed independently on which MCO entity it is. The problem doesn’t happen if i switch on the same button via the tablet.

If I downgrade HA Core to 2023.10.4 version everything works properly.

Please find below a snapshot of the tablet Lovelace message 20231209_121807

I have those MCO Devices: MH-S411 MH-S413 MH-S314

Zwave dongle: AEON Lab Z‐Stick Gen5 USB Controller

Home assistant is Running on Raspberry Pi 4

What version of Home Assistant Core has the issue?

2023.12.1

What was the last working version of Home Assistant Core?

2023.10.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-wave

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

2023-12-09 12:36:43.824 INFO APP: GET /health/zwave 301 1.884 ms - 191 2023-12-09 12:36:57.874 INFO Z-WAVE: [Node 003] Value updated: 32-4-currentValue 99 => 99 2023-12-09 12:36:57.879 INFO Z-WAVE: [Node 003] Value updated: 37-4-currentValue true => true 2023-12-09 12:36:58.246 INFO Z-WAVE: [Node 003] Value updated: 32-2-currentValue 0 => 0 2023-12-09 12:36:58.251 INFO Z-WAVE: [Node 003] Value updated: 37-2-currentValue false => false 2023-12-09 12:36:58.574 INFO Z-WAVE: [Node 003] Value notification: 91-0-scene-004 1 2023-12-09T11:36:58.579Z CNTRLR « [Node 003] received CentralScene notification { “nodeId”: 3, “ccId”: “Central Scene”, “ccCommand”: “0x03”, “payload”: “0x610104” } 2023-12-09 12:36:58.589 INFO Z-WAVE: [Node 003] Value updated: 32-4-currentValue 99 => 0 2023-12-09 12:36:58.592 INFO Z-WAVE: [Node 003] Value updated: 37-4-currentValue true => false 2023-12-09 12:36:58.922 INFO Z-WAVE: [Node 003] Value notification: 91-0-scene-002 1 2023-12-09T11:36:58.926Z CNTRLR « [Node 003] received CentralScene notification { “nodeId”: 3, “ccId”: “Central Scene”, “ccCommand”: “0x03”, “payload”: “0x600102” } 2023-12-09 12:36:59.203 INFO Z-WAVE: [Node 003] Value updated: 32-2-currentValue 0 => 99

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Referenced entities switch.switch_scenari_cucina_2 are missing or not currently available
12:20:37 PM – (WARNING) helpers/service.py - message first occurred at 11:59:42 AM and shows up 501 times
Error unloading entry Z-Wave JS for zwave_js
12:20:37 PM – (ERROR) config_entries.py
Run All Lights Off: Already running
12:20:37 PM – (WARNING) Automation
Run Welcome: Already running
12:20:37 PM – (WARNING) Automation
Error setting up entry Z-Wave JS for update
12:20:36 PM – (ERROR) config_entries.py
Unexpected exception: Invalid event type Central scene scene 001 for event.switch_camera_padronale_scene_001
12:20:36 PM – (ERROR) Z-Wave - message first occurred at 11:59:41 AM and shows up 11 times

Additional information

No response

About this issue

Original URL
State: closed
Created 7 months ago
Comments: 27 (7 by maintainers)

Most upvoted comments

Confirming that disabling the events for those switches in the HA Device configuration stops the error occurring and the subsequent repeated reload of the integration. Seems like the easiest fix for now and will raise an issue with zwave-js regarding the allowed values once I have reinterviewed and captured a log. Thanks very much kpine for your assistance!

andrewpc on Dec 20, 2023

Thanks. The logs dont seem to format nicely when I paste them in and use the code tag. I reinterviewed both switches and it didn’t solve the problem. The error regarding “Invalid event type Central scene” still shows up. I will monitor and see if the crash re-occurs and try to capture a log as requested.

Edit: Fixed formatting of above log files in previous comment

andrewpc on Dec 19, 2023

The driver defines which states (key attributes for Central Scene) are valid for each scene:

        "46-91-0-scene-001": {
          "endpoint": 0,
          "commandClass": 91,
          "commandClassName": "Central Scene",
          "property": "scene",
          "propertyKey": "001",
          "propertyName": "scene",
          "propertyKeyName": "001",
          "ccVersion": 2,
          "metadata": {
            "type": "number",
            "readable": true,
            "writeable": false,
            "label": "Scene 001",
            "min": 0,
            "max": 255,
            "states": {
              "0": "KeyPressed"
            },
            "stateful": false,
            "secret": false
          }
        },

You can see that it only shows support for KeyPressed. The event entity code can’t find the KeyReleased event so it results in some unexpected behavior.

If you want to dig further, you could post the driver logs of a re-interview of the device. For sanity, since you are using ZUI you can get those logs directly (we’re only interested in driver logs so that has much less noise than integration debug logs). The states that are advertised are a responsibility of Z-Wave JS. Either it is not providing the right information, or there’s a bug in the device firmware and it doesn’t correctly advertise the supported key attributes.

Either way, the integration shouldn’t reload on these unexpected errors, which is the same cause as https://github.com/home-assistant/core/issues/101803 and will be solved by a fix in the corresponding Python library.

If you aren’t using the event entities, you could try disabling them to avoid the problem. I wouldn’t expect a disabled entity to process these events, but I’m not sure.

kpine on Dec 20, 2023

short_debug_log.txt

Here is an extract of the log showing what I mentioned above. Thanks

andrewpc on Dec 20, 2023

That device diag looks fine. It shows Central Scene values with states (KeyPressed). The only reason you’d continue to see the error for that device would be a) if you did not reload the integration after re-interview, or b) if it is reporting a key attribute that it doesn’t advertise (something else besides “KeyPressed”). Would need to see debug logs to confirm the latter.

kpine on Dec 20, 2023