HA loses connection to zwavejs2mqtt when receiving a CC Multilevel Switch notification

[Cytrian]

The problem

When I touch a toggle switch connected to my Fibargroup Roller Shutter 3 (FGR223), HA loses the connection to my zwavejs2mqtt service and does not connect again; afterwards no ZWave device is available in HA until I restart HA.

This seems to be an issue that came with https://github.com/zwave-js/zwavejs2mqtt/releases/tag/v6.7.0
I have not experienced this problem with release 6.6.2

zwavejs2mqtt logs this when I touch a toggle switch:

2022-04-19 21:15:17.232 INFO ZWAVE: Node 4 CC Multilevel Switch { eventType: 4, direction: 'up' }
2022-04-19 21:15:17.279 INFO ZWAVE-SERVER: Client disconnected
2022-04-19 21:15:19.199 INFO ZWAVE: Node 4 CC Multilevel Switch { eventType: 5 }
2022-04-19 21:15:19.445 INFO ZWAVE: Node 4: value updated: 38-1-targetValue 0 => 7
2022-04-19 21:15:19.451 INFO ZWAVE: Node 4: value updated: 38-1-duration unknown => unknown
2022-04-19 21:15:19.456 INFO ZWAVE: Node 4: value updated: 38-1-currentValue 0 => 7
2022-04-19 21:15:19.640 INFO ZWAVE-SERVER: Client disconnected

On the HA side I see this

2022-04-19 19:15:17 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to listen: Notification received with unsupported command class SWITCH_MULTILEVEL: {'source': 'node', 'event': 'notification', 'nodeId': 4, 'ccId': 38, 'args': {'eventType': 4, 'direction': 'up'}}
2022-04-19 19:15:19 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to listen: Notification received with unsupported command class SWITCH_MULTILEVEL: {'source': 'node', 'event': 'notification', 'nodeId': 4, 'ccId': 38, 'args': {'eventType': 5}}

Notes:

• zwavejs2mqtt is connected via "Z-Wave JS websocket server", MQTT is disabled.
• After the connection is closed, HA does not retry the connection until restart.

What version of Home Assistant Core has the issue?

core-2022.4.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[Cytrian]

Related to home-assistant-libs/zwave-js-server-python#396

[j9brown]

I'm seeing this too. It's related to a newly added feature (that I look forward to using): zwave-js/node-zwave-js#4282

For future-proofing, perhaps the integration could be improved to emit a warning and ignore unsupported notifications instead of doing whatever it's doing now that stops it from working altogether.

[raman325]

I'm seeing this too. It's related to a newly added feature (that I look forward to using): zwave-js/node-zwave-js#4282

For future-proofing, perhaps the integration could be improved to emit a warning and ignore unsupported notifications instead of doing whatever it's doing now that stops it from working altogether.

yup the original implementation was poorly thought out (I was the one that did it so I feel comfortable saying that 🙂 ) we'll get it fixed soon, not sure if we can get it done in a patch release or whether it will have to wait for the next release which is in 2 weeks.