Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202)

Configuration Z-Wave
21

Are you running ZwaveJS UI 4.x? In that case you could try going back to version 3.24.0. I have the some kind of errors, that I never have going back to 3.24. To me it seems like it has to do with ZwaveJS UI 4.x and higher.

1 Like
22

Thank you for the link and the recommendation.
Iā€™m not sure where to find the zwcfg*.xml configuation files for my nodes.
Iā€™m running Zwave JS UI as a docker app, but the appdata config folder is not showing any files.
Could it be that I need to open the actual folder on the docker.img to see these files?

23

My guess is zwcfg.xml is from an old z-wave version (ozw?).

Hopefully someone can jump in here and explain how the discovery works and why it might be mapping your device to the LIGHT platform instead of COVER. Maybe not related to the queue full error, but itā€™s one thing that seems off.

What is that cover device? And what ID (manufacture productType-Product ID) does it have?Itā€™s at the top when you expand a device in ZUI e.g. 0x027a 0x7000-0xf001.

Sorry, not much help.

1 Like
24

I appreciate all your help so far :slight_smile:
This is one ID for the problematic switches being recognized as lights instead of blinds.
0x0293 0x0003-0x0024

Screenshot 2025-04-10 at 23.25.42
Screenshot 2025-04-10 at 23.25.42558Ɨ162 6.36 KB

25

So, itā€™s this device? Two light swiches and two blind controls?

Odd thereā€™s not much data for that device. Maybe descovery.py needs a config for the device? Probably worth a fresh post asking about it. Itā€™s not something I know about.

1 Like
26

Yes, itā€™s this device.

27

fwiw, since yesterdays z-wave update I am also seeing this
not sure what they did to the server, but I dont think we should be fixing this with delays in our automationsā€¦

note this is Not the z-wave UI add-on but the core add-on.
issue at Z-Wave js: Transmission queue full (ZW0202) Ā· Issue #3982 Ā· home-assistant/addons Ā· GitHub

2 Likes
28

You have zwave devices sending meter reports every 150ms. Thatā€™s too fast. My guess is the new code is slower than the old and itā€™s pushed your system to where it canā€™t keep up.

29

Ill upload a log with the downgraded 0.10.0 version, for comparison.

30

I agree. Delays in automations is a bad idea.

The transmission queue full (ZW0202) happens here after upgrading to version 4. When I downgrade back to the latest 3.x version, the problem is gone and everything runs fine.

It really has to do with the 4.x version.

1 Like
31

For what itā€™s worth; same problem here with 4.x

32

Iā€™ve got the same issue.

Transmission queue full and nodes going randomly dead / unresponsive following 4.x upgrade.

Iā€™ve seen a few people mention downgrades to 3.x. How does one do that please?

33

Have you got backups enabled? You could look in the backups for the older addon. I set the backup plugin to backup when upgrading.

When you found the older plugins in the backups, just select it and restore that version. The network will be up and running after that.

34

I have the same problem. I also have Z-Stick Gen 5+ and the Z-wave JS UI addon v. 4.1.0 (= Z-wave JS 15.0.6). Gets ā€œtransmission queue fullā€ error when running multiple automations (e.g., to turn off most of the lights in the house during night time). I am running HAOS but donā€™t have any old backups (recent installation). Is there another way to downgrade the Z-Wave JS UI addon?

35

Do you have ssh access to the HAOS host?

What I did was modify the version in the Add-Onā€™s config.yaml file, and then asked the Supervisor to look for updates (on the Configuration->Add-Ons page) and it offered up the old version. Itā€™s a bit of a hack, and probably depends on the add-onā€™s config not changing other than the image version. Save a backup the zui config (/data/store).

36

Iā€™ve had this issue regularly for a while as well :frowning:
Downgrading to version 3.24.0 also fixed the issue for me. Hopefully a solution can be found soon.

37

I had those issues with the 4.0.x versions, no longer with 4.1.0 (also issue log for zwavejs/zwavejs-ui shows that this issue is solved)

38

I still have the issue with 4.1 too. :frowning: I am back at 3.24. This is the last version without the problem.

39

Indeed, 5 minutes after writing my earlier post, I got error messages again. So still issues with 4.1.0

40

One of my long-standing automations has now aborted twice reporting this same error, and I recently upgraded ZWave JS UI from 3.8.4 to 4.0.3 as well on 4/7, and to 4.0.4 on 4/13. Currently on 4.1.0 and it happened today.

My error is:

Error: Unable to set value 32-37-0-targetValue: zwave_error: Z-Wave error 202 - Failed to send the command: Transmission queue full (ZW0202)

Device 32 is a Zooz ZEN21 wall switch and the third in a Group of 7 being turned on inside the automation (32-37-0 is the Binary Switch). Unfortunately, Iā€™ve found that Traces only goes back a few runs so I donā€™t know if it is the same device in the previous failure. Can you increase that history somehow?

However, looking at the logs, it appears that the issue is with Binary Switches. It has affected multiple devices on my system, but only the failed automation brought it to my attention. I do not see any excess traffic from any of my devices, something I checked since I re-interviewed ALL of my devices after having this issue. I make a point of disabling all unused entities and configuring each device to minimize traffic.

From the logs, I had this error 2 times each day on 4/13, 4/14, and 4/16, and 4 times on 4/15, and more since that time, including another instance of the above automation aborting because one of the binary switch commands failing today.

Here are two log entries from z-ui logs and their time associated entries from the zwavejs logs:

2025-04-13 15:12:22.631 ERROR Z-WAVE-SERVER: Failed to send the command: Transmission queue full (ZW0202)
ZWaveError: Failed to send the command: Transmission queue full (ZW0202)
    at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
    at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
    at Driver.sendSupervisedCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:7032:27)
    at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:7087:30)
    at Proxy.play (/opt/node_modules/@zwave-js/cc/src/cc/SoundSwitchCC.ts:217:20)
    at Proxy.play (/opt/node_modules/@zwave-js/cc/src/cc/SoundSwitchCC._validateArgs.ts:40:30)
    at Proxy.<anonymous> (/opt/node_modules/@zwave-js/cc/src/cc/SoundSwitchCC.ts:326:26)
    at ZWaveNode2.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:539:39)
    at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:23:43)
    at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)

2025-04-13T15:10:01.478Z CNTRLR Ā« [Node 112] received wakeup notification
2025-04-13T15:10:01.480Z CNTRLR   [Node 112] The node is now awake.
2025-04-13T15:10:01.732Z CNTRLR Ā» [Node 112] Sending node back to sleep...
2025-04-13T15:10:01.749Z CNTRLR   [Node 112] The node is now asleep.
2025-04-13T15:16:33.633Z CNTRLR Ā« [Node 044] received wakeup notification
2025-04-13T15:16:33.635Z CNTRLR   [Node 044] The node is now awake.
2025-04-13T15:16:33.886Z CNTRLR Ā» [Node 044] Sending node back to sleep...
2025-04-13T15:16:33.903Z CNTRLR   [Node 044] The node is now asleep.

2025-04-13 13:35:37.488 ERROR Z-WAVE-SERVER: Failed to send the command: Transmission queue full (ZW0202)
ZWaveError: Failed to send the command: Transmission queue full (ZW0202)
    at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6786:23)
    at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6986:28)
    at Driver.sendSupervisedCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:7032:27)
    at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:7087:30)
    at Proxy.set (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:140:20)
    at Proxy.set (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC._validateArgs.ts:13:30)
    at Proxy.<anonymous> (/opt/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:162:16)
    at ZWaveNode2.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:539:39)
    at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:23:43)
    at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist-esm/lib/server.js:134:100)

2025-04-13T13:29:00.697Z CNTRLR Ā« [Node 051] received wakeup notification
2025-04-13T13:29:00.699Z CNTRLR   [Node 051] The node is now awake.
2025-04-13T13:29:00.950Z CNTRLR Ā» [Node 051] Sending node back to sleep...
2025-04-13T13:29:00.967Z CNTRLR   [Node 051] The node is now asleep.
2025-04-13T13:34:08.245Z CNTRLR Ā« [Node 060] received wakeup notification
2025-04-13T13:34:08.247Z CNTRLR   [Node 060] The node is now awake.
2025-04-13T13:34:08.498Z CNTRLR Ā» [Node 060] Sending node back to sleep...
2025-04-13T13:34:08.640Z CNTRLR   [Node 060] The node is now asleep.
2025-04-13T13:34:56.567Z CNTRLR Ā« [Node 021] received wakeup notification
2025-04-13T13:34:56.569Z CNTRLR   [Node 021] The node is now awake.
2025-04-13T13:34:56.820Z CNTRLR Ā» [Node 021] Sending node back to sleep...
2025-04-13T13:34:56.835Z CNTRLR   [Node 021] The node is now asleep.
2025-04-13T13:38:26.212Z CNTRLR Ā« [Node 108] received wakeup notification
2025-04-13T13:38:26.213Z CNTRLR   [Node 108] The node is now awake.
2025-04-13T13:38:26.464Z CNTRLR Ā» [Node 108] Sending node back to sleep...
2025-04-13T13:38:26.481Z CNTRLR   [Node 108] The node is now asleep.

Hope this helps the team track this down. Let me know if I can provide anything else.

Cheers