Z-wave radio transmission failure help

Devices & Integrations
1

Im looking for some help figuring out what’s going on. Recently Ive starting having issues getting z-wave devices to respond to commands either by routine or manually. The issue is only effecting my z-wave devices. Looking at the logcat in the CLI, I see the a “failed to be queued for radio transmission” error. Below is an except from the logcat for the stock Z-Wave Window Treatment driver though the issue is not isolated to this driver, other z-wave devices both using legacy DTH and edge drivers are not executing properly. The issue is sometimes resolved when rebooting the hub, but this is now a daily occurrence.

2023-02-26T13:35:18.698089663+00:00 DEBUG Z-Wave Window Treatment Shade - Bed 2-4 device thread event handled
2023-02-26T13:35:18.710170621+00:00 ERROR Z-Wave Window Treatment Z-Wave command(04d57d71) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:18.710960746+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: a5bd61b3-e476-4424-b98f-ffbff50c70b9 [5B] (Shade - Kitchen 2)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-02-26T13:35:18.716784621+00:00 DEBUG Z-Wave Window Treatment Shade - Kitchen 2 device thread event handled
2023-02-26T13:35:18.730031455+00:00 ERROR Z-Wave Window Treatment Z-Wave command(d9a946d7) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:18.730688121+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: 2c7be759-a41d-46e3-80a8-8df1ae1e6c41 [30] (Shade - Bed 3-2)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-02-26T13:35:18.736554288+00:00 DEBUG Z-Wave Window Treatment Shade - Bed 3-2 device thread event handled
2023-02-26T13:35:18.753753121+00:00 ERROR Z-Wave Window Treatment Z-Wave command(bf7baaab) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:18.754367621+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: 00a6460c-f643-4356-ad30-498c4d3bdabd [5D] (Shade - Kitchen 3)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-02-26T13:35:18.761816038+00:00 DEBUG Z-Wave Window Treatment Shade - Kitchen 3 device thread event handled
2023-02-26T13:35:19.124421413+00:00 ERROR Z-Wave Window Treatment Z-Wave command(07deed1d) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:19.131075580+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: 0274af87-d881-4be9-aa66-8a1a439c3c27 [22] (Shade - MBT3)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-02-26T13:35:19.131885246+00:00 DEBUG Z-Wave Window Treatment Shade - MBT3 device thread event handled
2023-02-26T13:35:19.151111746+00:00 ERROR Z-Wave Window Treatment Z-Wave command(ef134e37) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:19.154727996+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: 7adf416e-9097-4ebf-9d4d-b9df2e8d65bf [2A] (Shade - Bed 2-2)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-02-26T13:35:19.158568621+00:00 DEBUG Z-Wave Window Treatment Shade - Bed 2-2 device thread event handled
2023-02-26T13:35:19.211136288+00:00 ERROR Z-Wave Window Treatment Z-Wave command(d50eb559) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:19.214123538+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: 74d9182c-08b4-484c-9d23-7b1135aee0d7 [27] (Shade - Bed 2-1)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}
2023-02-26T13:35:19.219354038+00:00 DEBUG Z-Wave Window Treatment Shade - Bed 2-1 device thread event handled
2023-02-26T13:35:19.230252746+00:00 ERROR Z-Wave Window Treatment Z-Wave command(d0fbc056) failed to be queued for radio transmission: CC:Switch Multi-level, CID:0x02
2023-02-26T13:35:19.234835455+00:00 INFO Z-Wave Window Treatment <ZwaveDevice: 6200a544-ccf7-4262-bee8-69ecb9a6597a [23] (Shade - MBT4)> sending Z-Wave command: {args={}, cmd_class=“SWITCH_MULTILEVEL”, cmd_id=“GET”, dst_channels={}, encap=“AUTO”, payload=“”, src_channel=0, version=1}

2

If you have any metering devices you should disable the power/energy reports or change their threshold/frequency to reduce the number of reports being sent.

That might have nothing to do with your issue, but reducing the number of z-wave messages the hub has to deal with often resolves random z-wave issues so it’s worth trying.

Are you seeing those errors from your shades all the time or only after attempting to control them?

3

Thanks Kevin - I did have some devices that were polling/reporting a little too frequently, so thanks for that. It seems to happen most frequently when several devices are triggered in routines, i.e. I have a daylight hours scene that essentially impacts 90% of my devices thats triggered in the morning, and the last few days all z-wave devices stall and this error is seen. If I reboot the hub, it seems to fix the issue most of the time. I’ll keep an eye on it to see if the tip you suggested helps out.

Is there a way to all of the device logging in a manner similar to what we had on the IDE with Live Logging back in the day? I know I can see all of the edge devices with logcat but wasn’t sure how others were getting logs for groovy devices.

4

Routines usually execute the actions at least 3x so a routine with multiple actions and/or multiple routines that fire at the same time can easily overload the mesh resulting in performance and reliability issues.

The simplest solution is to use delays for the non time-critical routines so that it’s not trying to do so much at the same time. Even a 2-3 second delay might solve the problem, but I usually try to space mine out by more than that.

All that being said, most of the time when you overwhelm the hub it starts dropping messages or takes an extremely long time to finish processing them all. I haven’t seen the error message you’re getting so if reducing the messages being sent at the same time doesn’t help then you’ll probably need to contact ST support.

1 Like