addons
addons copied to clipboard
home-assistant
Z-Wave js: Transmission queue full (ZW0202)
Describe the issue you are experiencing
happening since yesterdays update to 0.11.0
many devices are no longer available, or randomly lose contact.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Z-Wave JS
What is the version of the add-on?
0.11.0
Steps to reproduce the issue
- simply updating caused the issue to happen
...
System Health information
System Information
| version | core-2025.4.2 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.13.2 |
| os_name | Linux |
| os_version | 6.12.18-haos |
| arch | x86_64 |
| timezone | Europe/Amsterdam |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| HACS Data | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 2.0.5 |
| Stage | running |
| Available Repositories | 1651 |
| Downloaded Repositories | 45 |
Home Assistant Cloud
| logged_in | true |
|---|---|
| subscription_expiration | 31 augustus 2025 om 02:00 |
| relayer_connected | true |
| relayer_region | eu-central-1 |
| remote_enabled | true |
| remote_connected | true |
| alexa_enabled | false |
| google_enabled | true |
| cloud_ice_servers_enabled | true |
| remote_server | eu-central-1-5.ui.nabu.casa |
| certificate_status | ready |
| instance_id | f510xxxx4bf925 |
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 15.0 |
|---|---|
| update_channel | beta |
| supervisor_version | supervisor-2025.04.0 |
| agent_version | 1.7.2 |
| docker_version | 28.0.1 |
| disk_total | 458.4 GB |
| disk_used | 24.8 GB |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | generic-x86-64 |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Log Viewer (0.17.1), Samba share (12.5.0), Terminal & SSH (9.16.0), Mosquitto broker (6.5.0), Z-Wave JS (0.11.0), Studio Code Server (5.18.4), Get HACS (1.3.1), ESPHome Device Builder (2025.3.2), File editor (5.8.0), Network UPS Tools (0.14.1), Advanced SSH & Web Terminal (20.0.2) |
Dashboards
| dashboards | 12 |
|---|---|
| resources | 23 |
| views | 184 |
| mode | yaml |
Network Configuration
| adapters | lo (disabled), enp2s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth9c3d18a (disabled), veth939192e (disabled), veth6dfdc7e (disabled), vethd9e272d (disabled), vethd17af21 (disabled), veth34d412c (disabled), vethb3ca12d (disabled), veth332151e (disabled), veth6d9184d (disabled), veth0de3633 (disabled), veth58b9ea4 (disabled) |
|---|---|
| ipv4_addresses | lo (127.0.0.1/8), enp2s0 (192.168.1.61/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth9c3d18a (), veth939192e (), veth6dfdc7e (), vethd9e272d (), vethd17af21 (), veth34d412c (), vethb3ca12d (), veth332151e (), veth6d9184d (), veth0de3633 (), veth58b9ea4 () |
| ipv6_addresses | lo (::1/128), enp2s0 (fe80::696d:3be9:f0cd:407a/64), docker0 (fe80::50eb:1eff:fee7:dc36/64), hassio (fe80::ecbc:f7ff:fefc:95c/64), veth9c3d18a (fe80::8429:4fff:fee3:c41d/64), veth939192e (fe80::6458:20ff:fe93:7126/64), veth6dfdc7e (fe80::8c11:abff:feee:d9be/64), vethd9e272d (fe80::818:1dff:fe21:f3da/64), vethd17af21 (fe80::20f3:d3ff:fe0f:e3a4/64), veth34d412c (fe80::68cf:baff:fef6:284c/64), vethb3ca12d (fe80::4cf1:4eff:fe3b:5627/64), veth332151e (fe80::e45f:e7ff:fe61:95a9/64), veth6d9184d (fe80::1c08:71ff:fe63:8053/64), veth0de3633 (fe80::10f5:aff:fe40:f08c/64), veth58b9ea4 (fe80::a836:9bff:fe74:3bb/64) |
| announce_addresses | 192.168.1.61, fe80::696d:3be9:f0cd:407a |
Recorder
| oldest_recorder_run | 28 maart 2025 om 21:39 |
|---|---|
| current_recorder_run | 12 april 2025 om 14:47 |
| estimated_db_size | 3553.29 MiB |
| database_engine | sqlite |
| database_version | 3.48.0 |
Spotify
| api_endpoint_reachable | ok |
|---|
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Z-Wave error ZWaveError: Failed to send the command: Transmission queue full (ZW0202)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)
at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)
at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)
at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)
at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)
at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45) {
code: 202,
context: SendDataResponse {
type: 1,
functionType: 19,
expectedResponse: undefined,
expectedCallback: undefined,
payload: Bytes(0) [Uint8Array] [],
callbackId: undefined,
nodeUpdateTimeout: undefined,
prematureNodeUpdate: undefined,
_transmissionTimestamp: undefined,
_completedTimestamp: undefined,
wasSent: false
},
Additional information
No response
ok I've set it to debug now and will see if it shows more soon, but also notice there was more in the current (error) log oddly enough this mentions the MultilevelSensor, but that one is not unavailable....:
Z-Wave error ZWaveError: The node did not acknowledge the command (ZW0204)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)
at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)
at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)
at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)
at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)
at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45) {
code: 204,
context: SendDataRequestTransmitReport {
type: 0,
functionType: 19,
expectedResponse: undefined,
expectedCallback: undefined,
payload: Bytes(0) [Uint8Array] [],
callbackId: 75,
nodeUpdateTimeout: undefined,
prematureNodeUpdate: undefined,
_transmissionTimestamp: undefined,
_completedTimestamp: undefined,
transmitStatus: 1,
txReport: undefined
},
transactionSource: ' at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)\n' +
' at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)\n' +
' at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)\n' +
' at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)\n' +
' at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)\n' +
' at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)\n' +
' at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)\n' +
' at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45)'
}
Z-Wave error ZWaveError: The node did not acknowledge the command (ZW0204)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)
at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)
at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)
at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)
at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)
at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45) {
code: 204,
context: SendDataRequestTransmitReport {
type: 0,
functionType: 19,
expectedResponse: undefined,
expectedCallback: undefined,
payload: Bytes(0) [Uint8Array] [],
callbackId: 99,
nodeUpdateTimeout: undefined,
prematureNodeUpdate: undefined,
_transmissionTimestamp: undefined,
_completedTimestamp: undefined,
transmitStatus: 1,
txReport: undefined
},
transactionSource: ' at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)\n' +
' at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)\n' +
' at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)\n' +
' at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)\n' +
' at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)\n' +
' at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)\n' +
' at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)\n' +
' at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45)'
}
Z-Wave error ZWaveError: Failed to send the command: Transmission queue full (ZW0202)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)
at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)
at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)
at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)
at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)
at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45) {
code: 202,
context: SendDataResponse {
type: 1,
functionType: 19,
expectedResponse: undefined,
expectedCallback: undefined,
payload: Bytes(0) [Uint8Array] [],
callbackId: undefined,
nodeUpdateTimeout: undefined,
prematureNodeUpdate: undefined,
_transmissionTimestamp: undefined,
_completedTimestamp: undefined,
wasSent: false
},
transactionSource: ' at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)\n' +
' at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)\n' +
' at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)\n' +
' at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)\n' +
' at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)\n' +
' at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)\n' +
' at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)\n' +
' at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45)'
}
Z-Wave error ZWaveError: The node did not acknowledge the command (ZW0204)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)
at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)
at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)
at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)
at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)
at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)
at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45) {
code: 204,
context: SendDataRequestTransmitReport {
type: 0,
functionType: 19,
expectedResponse: undefined,
expectedCallback: undefined,
payload: Bytes(0) [Uint8Array] [],
callbackId: 202,
nodeUpdateTimeout: undefined,
prematureNodeUpdate: undefined,
_transmissionTimestamp: undefined,
_completedTimestamp: undefined,
transmitStatus: 1,
txReport: undefined
},
transactionSource: ' at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)\n' +
' at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)\n' +
' at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7104:29)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:292:36)\n' +
' at Proxy.get (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC._validateArgs.ts:12:30)\n' +
' at Proxy.<anonymous> (file:///usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSensorCC.ts:240:16)\n' +
' at ZWaveNode.pollValue (file:///usr/src/node_modules/zwave-js/src/lib/node/Node.ts:737:56)\n' +
' at NodeMessageHandler.handle (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:75:42)\n' +
' at Client.receiveMessage (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)\n' +
' at WebSocket.<anonymous> (file:///usr/src/node_modules/@zwave-js/server/dist-esm/lib/server.js:55:45)'
}
this is what was logged up to now, hope this helps
since these are mission critical in my config, I downgraded to 0.10.0, which immediately brings back all nodes.... If you need, I can upload the last log once again, and hope that change was caught?
fwiw, many of the qubino smart plugs were having trouble in my system after updating, and since this device is mentioned explicitly in the 0.11.0 update, the would maybe indicate an issue there
I see meter devices in there reporting every ~150ms. I don't know if that's the root cause, it's certainly not ideal for your network.
I did have the odd error on the Multi sensor device, but the rest was always very stable and reliable. So apparently ythose updates didnt bother the system before (an d I have very low % in the add-on, not indicting trouble at all)
new log with 0.10.0
Node 39, 90 and 108 are the bulk of the traffic.
It the physically transmission speed of the zwave network it's very slow. You have alot of data going through a small pipe.
Qubino smart plug, Greenwave single socket, Qubino smart plug.
39 might have the worst connection, the other 2 are practically near the stick
Network is very stable now though so even if there is a lot of traffic, it doesn’t harm.
Seems the 0.11.0 update needs to be checked for this
I see meter devices in there reporting every ~150ms
That's definitely a no-go. If the controller receives one every 150ms, depending on the routers and possible re-transmit attempts involved, this can mean the mesh sees much more frequent traffic.
@Mariusthvdb can you give timestamps from that log where you saw the errors?
I found something in the logs that bothers me. https://github.com/zwave-js/zwave-js/pull/7732 is a potential fix.
@Mariusthvdb can you give timestamps from that log where you saw the errors?
you mean in the HA log?
Logger: homeassistant.components.zwave_js Bron: components/zwave_js/entity.py:84 integratie: Z-Wave (documentatie, problemen) Eerst voorgekomen: 12 april 2025 om 15:12:05 (8 gebeurtenissen) Laatst gelogd: 06:00:11
Error while refreshing value Value(value_id='38-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts. Transmission queue full (ZW0202) Error while refreshing value Value(value_id='106-50-0-value-65537'): zwave_error: Z-Wave error 204 - The node did not acknowledge the command (ZW0204) Error while refreshing value Value(value_id='68-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts. Transmission queue full (ZW0202) Error while refreshing value Value(value_id='96-49-0-Air temperature'): zwave_error: Z-Wave error 204 - The node did not acknowledge the command (ZW0204) Error while refreshing value Value(value_id='13-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202)
tbh, I am not sure this is from before downgrading to 0.10.0 or still on 0.11.0.. let me look those up:
2025-04-13 15:15:23.582 ERROR (MainThread) [homeassistant.components.zwave_js] Error while refreshing value Value(value_id='68-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts. Transmission queue full (ZW0202)
is definitely from after downgrade to 0.10.0 but, the main thing is, 0.10.0 does not choke on that, and keeps a reliable network, no devices going unavailable
ok sorry. I might be misunderstanding your ask, but the logs I sent contain the timestamps? I dont have specific moments where this was 'happening', other than after updating to 0.11.0 the nodes lost connection, and to me, in rather a random order. restarting the add-on made some re-appear, but others disappear.
I was trying to find a correlation between the error you quoted from the HA logs:
zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts. Transmission queue full (ZW0202)
and the Z-Wave logs that would show what exactly caused it. The logs that were shared don't seem to span the same timeframes
zwave-js-ui-store(4).zip Same problem: ERROR Z-WAVE-SERVER: Failed to send the command: Transmission queue full (ZW0202). Error happens when trying to execute automation that turns off multiple lights. I have tried Z-wave JS UI Add-on version 4.1.0 but still same error.
Z-wave JS UI log attached.
I now see I missed adding the community topic on the same issue: https://community.home-assistant.io/t/z-wave-error-202-failed-to-send-the-command-transmission-queue-full-zw0202/874365/27?u=mariusthvdb
also https://community.home-assistant.io/t/all-light-devices-are-unavailable-after-upgrade-to-zwave-js-ui-4-0-1/869328
not sure if these are 100% related (using the UI version, where I use core only) but the trouble seems very much so
and let me repeat, even after downgrading to 0.10.0 these errors persist., they just dont break the system note the nodes now are 91 and 106.... as said, seems to randomly affect the connected nodes
Logger: homeassistant.components.zwave_js
Bron: components/zwave_js/entity.py:84
integratie: Z-Wave (documentatie, problemen)
Eerst voorgekomen: 09:15:04 (3 gebeurtenissen)
Laatst gelogd: 15:52:04
Error while refreshing value Value(value_id='91-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202)
Error while refreshing value Value(value_id='106-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command after 1 attempts. Transmission queue full (ZW0202)
Error while refreshing value Value(value_id='96-49-0-Carbon dioxide (CO₂) level'): zwave_error: Z-Wave error 204 - The node did not acknowledge the command (ZW0204)
Hmm... very interesting... My error disappears when I enable the Driver logs (Debug log level) in the Z-wave section from Z-wave JS UI. Also no errors when setting Log level to Error. However, when I disable the logs I get the error again. For the time being, I will keep Driver log enabled (but without Log to file) - that seems to be a workaround.
even after downgrading to 0.10.0 these errors persist., they just dont break the system
It looks like the Z-Wave JS driver doesn't retry these failed commands on v15/0.11 as it used to on v14/0.10. But even when it does, the command can eventually fail and the errors need to be handled.
I'm not clear on what exactly is failing or causing devices to be unavailable when there is an error. @MartinHjelmare any idea on that?
If the driver crashes the server the client will be disconnected and all the Z-Wave entities will go unavailable until the client can connect to a working server again.
Not sure if that's what happening, but in the driver stack trace it looks like the errors are not handled by the driver in the server, right?
If the driver crashes the server the client will be disconnected and all the Z-Wave entities will go unavailable until the client can connect to a working server again.
Not sure if that's what happening
I do not think so no. Not all of the nodes go unavailable (not always anyways, I did see that once or twice, but that was auto fixed after some time)
even the 0.10.0 version now starts breaking things:
Logger: homeassistant.components.script.espresso_on_when_home Bron: helpers/script.py:2057 integratie: Script (documentatie, problemen) Eerst voorgekomen: 08:03:08 (1 gebeurtenissen) Laatst gelogd: 08:03:08
espresso_on_when_home: Error executing script. Error for call_service at pos 2: Unable to set value 77-37-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command after 3 attempts. Transmission queue full (ZW0202)
This is new to my config, and cant say related to anything changed tp the hardware side of things. the device here has been untouched for years now.... a simple switch.turn_on couldn't be done apparently.
Z-Wave JS logs are terrible for finding a related entry at that time. Why are there no timestamps in those loggings at all?
What z-stick do you have? My problems disappeared when I upgraded from Aeotec Gen 5+ to Aeotec Gen 7.
I never dared to upgrade to the new stick, as many issues were reported at that time, and no substantial benefit would be met for these types of installs... not even mentioning not being able to transport the current mesh into the new device, which would be a terrible job redoing...
nevertheless, given these issues are new, it probably isnt related to the stick itself, but to some firmware/driver change recently?
Any updates on this? I am new to all this, and I am using a totally different protocol and hardware but still getting full queue errors as you on the OpenThread Border Router add-on using the zbt-1. Not sure if it is related, probably not. But worth the ask.
OpenThread Border Router add-on using the zbt-1
That has nothing to do with Z-Wave.
https://github.com/zwave-js/zwave-js/releases/tag/v15.1.0 should fix this, but the addon still needs an update.
so ive been running the updates for several days now, and it seems to be better., the mentioned queue full error hasn't been spotted.
What does happen though, and this is new, is that at unpredictable moments, All zwave entities go unavailable in the Dashboard, and if a script or automation would need them at that time, there is failing functionality...
I havent been able to 'reproduce' actively or find a specific reason in the log, but it is quite impactful. Not sure how to proceed with this. Keep posting here, as the change is introduced after the mentioned fixed above? or, would it be a z-wave issue, that needs an issue in the https://github.com/zwave-js/zwave-js/releases/tag/v15.1.0 repo
I do believe it should be mentioned here, as it is hard to find the right spot among the various z-wave repos (integration/add-on/library..) , and this might help others..
I havent been able to 'reproduce' actively or find a specific reason in the log, but it is quite impactful.
Best make a new issue in the zwave-js repo, mentioning the times this happened, and driver logs that include the timespan. I can help find the reason in the logs if there's anything in there.
yeah well.... I shouldnt have said it of course... it's still there...
Logger: homeassistant.components.zwave_js Bron: components/zwave_js/entity.py:84 integratie: Z-Wave (documentatie, problemen) Eerst voorgekomen: 12:15:24 (8 gebeurtenissen) Laatst gelogd: 13:15:39
Error while refreshing value Value(value_id='91-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202) Error while refreshing value Value(value_id='106-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202) Error while refreshing value Value(value_id='39-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202) Error while refreshing value Value(value_id='94-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202) Error while refreshing value Value(value_id='13-50-0-value-65537'): zwave_error: Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202)
turning on debug
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}