Home Assistant Z-wave 7 Stick Protocol Error
This is a living document of my troubleshooting steps to resolve an issue with my Home Assistant ZwaveJS integration. The issue is that when Home Assistant sends commands to any of my z-wave devices it will fail with the following error and the controller status will change to jammed
:
Details
Observed on the following versions:
Type | Version |
---|---|
Home Assistant - Core | v2023.12.3 |
Home Assistant - Supervisor | v2023.11.6 |
Home Assistant - Operating System | v11.6 |
Zwave Firmware - | v7.17.2 |
Issue
When Home Assistant sends commands to any of my z-wave devices it will fail with the following error and the controller status will change to jammed
:
1Failed to call service light/turn_on. unknown error.
Logs Home Assistant:
1Logger: homeassistant.components.zwave_js
2Source: components/zwave_js/entity.py:337
3Integration: Z-Wave (documentation, issues)
4First occurred: 11:57:16 AM (1 occurrences)
5Last logged: 11:57:16 AM
6
7Unable to set value 10-38-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 5 attempts (ZW0202)
Troubleshooting
Inprogress
Testing to see if the update frequency of my home energy monitor was causing the issue, currently 5 seconds. I have changed it to 30 seconds to see if this resolves the issue.
- Issue was resolved for a few days but has returned.
- Issue continues to occur intermittently with spans of functioning normally for days at a time to breaking for a few days.
Complete
Updated the Z-Wave firmware to 7.17.2 as suggested by the Home Assistant Controllers Page. Issue still occurs.
References
According to the Home Assistant Controllers Page, this issue should of been resolved in version 7.17.2 of the ZwaveJS firmware.
Until recently, 700 series Z-Wave Controllers had a bug that could cause the mesh to be flooded on some networks and the controller to become unresponsive. At present, all 700 series controllers share the same firmware and are subject to this bug. It appears that this bug is largely, if not completely, resolved as of firmware version 7.17.2.