Zwave now fails in Home Assistant but works in Indigo

Configuration Z-Wave
1

Recently I’m getting error messages when I try to initiate a zwave device action. This seemed to happen around the time that I upgraded HA to 2024.12.

When I attempt to switch on a zwave device I get the following message:

Failed to perform the action switch/turn_on. Unable to set value 18-37-5-targetValue: zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202)

Curiously enough when I remove the Aeotec Z-stick Gen 5, and then attempt to switch a zwave device I get the exact same message. Does this mean that my HA Green is somehow no longer seeing the Aeotec stick?

And, interestingly if I take the stick and plug it into an older installation of the Indigo home automation app for Mac, it works flawlessly and can control the device without error.

I’ve restarted the HA Green and unplugged/plugged the stick multiple times. The stick is on a USB extension cable and was previously working flawlessly with this setup.

Can anyone point me in the direction of how to troubleshoot/fix this?

2

What Z-wave add-on are you running? What configuration does that add-on have? Do the logs of that add-on indicate an error? Based on your comments I’d guess your add-on no longer has the correct device path for your Z-wave controller.

If you navigate to Settings > System > Hardware > All Hardware, does your Z-wave controller appear in the list and does it match the add-on configuration?

3

Hi Martin, thanks for your insights and ideas. I’m running Z-wave JS.

That was a good prompt to look at the Hardware settings. (As I’m fairly new to HA, it was very helpful that you gave me the path to check. I wasn’t aware of that route but am now!)

It does appear on the list under: tty ACMO /dev/serial/by-id/usb-0658_0200-if00 which I believe is correct.

I restarted zwave JS and checked the logs. The messages indicated that the zwave nodes were okay but then reported that the controller became unresponsive.


> 2024-12-12T13:09:32.713Z CNTRLR   [Node 017] The node is alive.
> 2024-12-12T13:09:32.716Z CNTRLR   [Node 017] The node is ready to be used
> 2024-12-12T13:09:32.720Z CNTRLR « [Node 017] ping successful
> New client
> Starting logging event forwarder at debug level
> 2024-12-12T13:09:52.772Z SERIAL » 0x01030016ea                                                         (5 bytes)
> 2024-12-12T13:09:52.784Z DRIVER » [REQ] [SendDataAbort]
> 2024-12-12T13:10:02.776Z CNTRLR   The controller is unresponsive
> 2024-12-12T13:10:02.781Z DRIVER   Controller missed Send Data callback. Attempting to recover...
> 2024-12-12T13:10:02.783Z CNTRLR   Performing soft reset...
> 2024-12-12T13:10:02.798Z SERIAL » 0x01030008f4                                                         (5 bytes)
> 2024-12-12T13:10:02.801Z DRIVER » [REQ] [SoftReset]
> 2024-12-12T13:10:03.811Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
>                                   n 100 ms.
> 2024-12-12T13:10:03.916Z DRIVER » [REQ] [SoftReset]
> 2024-12-12T13:10:03.918Z SERIAL » 0x01030008f4                                                         (5 bytes)
> 2024-12-12T13:10:04.925Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
>                                   n 1100 ms.
> 2024-12-12T13:10:06.028Z DRIVER » [REQ] [SoftReset]
> 2024-12-12T13:10:06.031Z SERIAL » 0x01030008f4                                                         (5 bytes)
> 2024-12-12T13:10:07.040Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
>                                   0)
> 2024-12-12T13:10:07.043Z DRIVER   Automatic controller recovery failed. Returning to normal operation and hoping
>                                    for the best.
> 2024-12-12T13:10:07.047Z CNTRLR   The controller is no longer unresponsive
> 2024-12-12T13:10:07.052Z CNTRLR   [Node 011] ping failed: Timeout while waiting for a callback from the controll
>                                   er (ZW0200)

Ironically, as of now zwave is now responsive again after 3 or so days of not being so. I’m not sure if that’s driven by anything that I’ve done recently but at least I now know the areas to begin looking.

1 Like
4

Z-wave-JS UI will serve you much better in times of need. :slight_smile: There is a guide on the forum on how to convert.

5

Thanks Martin. In that case, I’ll look into it. Much appreciated.

6
7

Thanks Martin. I did track that down after you mentioned it but certainly appreciate the heads-up. Looks a bit involved but I guess I should make the move especially as at some point I’ll need to migrate to a newer stick.

The zwave guys seem to make it virtually impossible to move sticks, seems curiously user hostile for a company who’s best interests would seem to lie in keeping users engaged and on platform!

8

You can backup and restore between the sticks with Z-wave-JS UI. There are instructions on this forum.

9

Yes, I saw that thanks to you pointing out the benefits of ZUI. I’ll bite the bullet over the festive season!

1 Like
10

I’m having exactly the same problem. My Z-Wave gave up after upgrading to 2024.12.0 and I have simply not have had the time to look into the problem until today.

Using Aeotec stick, my log looks exactly as yours Jason. I’ve been testing different stuff in regards of the Z-Wave JS add-on, and at one point a temperature-sensor updated its value (which has been the same for some time now (since 2024.12 was released).

I checked the things you mentioned as well Martin. But now I’m wondering, is a move from Z-Wave JS to Z-Wave JS UI the way to go? Please if you have further updates in any direction what so ever, it would be much appreciated to take part of that

Thanks,
Marcus