Z-wave stopped working "The serial port is not open! (ZW0202)"

Configuration Z-Wave
1

my system - including z-wave - has generally been working ok for a long time. i did a recent sw update a that included bumping zwave-js add-on to version 0.10.0 a day or so ago.

now i’m noticing that when i try to send any standard z-wave command to a device from home-assistant, i get the error " “The serial port is not open! (ZW0202)”.

I’m using an aeotec zw090 z-stick z-wave interface.

i’ve never seen this before. seems like there’s a small chance that my server (home assistant yellow) could have had some kind of failure or that my z-stick failed, but it seems like more than a coincidence the first time i’ve ever experienced this problem follows closely on the heels of a z-wave-js update.

i’ve tried unplugging the z-stick and plugging it back in. i’ve tried restarting z-wave-js add-on from within home-assistant. upon restarting the add-on, it seemed in the logs like the stick was definitely working initially. there were many log lines that seemed to indicate there had been successful communication with various modules. but then within a few minutes, i saw log messages which seemed to indicate that it had stopped working and that the serial port was no longer open.

2025-04-14T17:28:57.434Z CNTRLR   [Node 221] Beginning interview - last completed stage: NodeInfo
2025-04-14T17:28:57.438Z CNTRLR   [Node 221] Interviewing Version...
2025-04-14T17:28:57.440Z CNTRLR » [Node 221]   querying the CC version for Version...
2025-04-14T17:29:03.428Z CNTRLR « [Node 094] received wakeup notification
2025-04-14T17:29:03.431Z CNTRLR   [Node 094] The node is now awake.
2025-04-14T17:29:03.440Z CNTRLR « [Node 094] received wakeup notification
2025-04-14T17:29:03.686Z CNTRLR » [Node 094] Sending node back to sleep...
2025-04-14T17:29:03.830Z CNTRLR « [Node 094] received wakeup notification
2025-04-14T17:29:59.395Z CNTRLR   The controller is unresponsive
2025-04-14T17:29:59.398Z DRIVER   Controller missed Send Data callback. Attempting to recover...
2025-04-14T17:29:59.400Z CNTRLR   Performing soft reset...
2025-04-14T17:30:00.406Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
                                  0)
2025-04-14T17:30:00.408Z DRIVER   Automatic controller recovery failed. Returning to normal operation and hoping
                                   for the best.
2025-04-14T17:30:00.409Z CNTRLR   The controller is no longer unresponsive
2025-04-14T17:30:00.412Z CNTRLR   [Node 221] Failed all interview attempts, giving up.
2025-04-14T17:30:01.416Z CNTRLR   The controller is unresponsive
2025-04-14T17:30:01.419Z DRIVER   Attempting to recover unresponsive controller by restarting it...
2025-04-14T17:30:01.422Z CNTRLR   Performing soft reset...
2025-04-14T17:30:02.429Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
                                  0)
2025-04-14T17:30:02.431Z DRIVER   Attempting to recover unresponsive controller by reopening the serial port...
2025-04-14T17:30:02.444Z CNTRLR   [Node 094] The node is now asleep.
2025-04-14T17:30:03.455Z DRIVER   Serial port reopened. Returning to normal operation and hoping for the best...
2025-04-14T17:30:03.457Z CNTRLR   The controller is no longer unresponsive
Stopping logging event forwarder
2025-04-14T18:13:06.059Z CNTRLR » [Node 175] Notification CC values may be stale, refreshing...
2025-04-14T18:13:06.069Z CNTRLR » [Node 175] querying notification status for Access Control...
2025-04-14T18:13:06.112Z CNTRLR   [Node 175] failed to refresh values for Notification CC: Message dropped becau
                                  se of an unexpected error: The serial port is not open! (ZW0202)

anyone seen this? have any suggestions?

2

Tell us more about “my system”. Is it HAOS? Bare metal hardware?

[quote=“dduff617, post:1, topic:877836”]
i did a recent sw update a that included bumping zwave-js add-on to version 0.10.0 a day or so ago.

It looks like the most recent add-on version is 0.11.0, have you tried that?

Have you confirmed the device appears in the Hardware list? (System > Hardware > All Hardware) - look for the serial port you are using.

Did you make a backup before upgrading? Have you tried rolling back to that version?

3

thanks very much, @mterry63.

my system is home assistant yellow box, so runnning HAOS.

fyi, the update to zwave-js that was installed was just the default update that came through.

here’s a (strange?) update: i did another restart of the z-wave js add-on from within HASS and this time (i think the third time overall that i tried restarting j-wave js), it came up clean and has worked smoothly now for a few hours with no problems.

i still have no idea of the root cause, whether it will recur, how to prevent, or how to “fix”.

4

Glad it’s working for you now.

5

Did you setup Z-Wave using ttyUSBx or serial_byid ? ttyUSBx can change after a reboot.

6

i just use the default and i’m pretty sure it just auto-discovered my j-stick attached to usb port when i first started using it some time ago and i have not changed anything - and definitely not changed anything recently to cause the reported problem. current serial port is set to /dev/serial/by-id/usb-0658_0200-if00.

7

I am having the same issue after that Zwave JS update. Mine was on 11.0
HAOS on Raspberry using a AEOTEC gen 5 stick
I tried the above and zwave started working but with a 1min + delay.
Restored back to a previous version 10.0 and still the strange behavior.

8

Here the same issue. Also HAOS with the aeotec Gen 5 stick. For weeks now zwave port is closing randomly. After restarting the addon the port is open but is most cases a lot of zwave devices are not working. Some times it takes 3,4,5 restarts before all zwave devices are workingm

9

Running HASS OS bare bone on a Intel NUC with way to much CPU and RAM so nothing to suspect there.

I have Silicon Labs HomeSeer 700 running in Z-Wave JS and it worked excellent until a few updates ago.

Also seeing port issue in my logs and i guess the port changes when things happens like nightly backups or what not cause every morning it’s dead and i have to restart Z-Wave JS.

Any tip on how i can check if im using ttyUSBx or serial_byid?

Well, this uses: tcp://192.168.4.122:2001 so i guess the only question is why the port issue:

Z-Wave JS i guess will only try port 2001 so maybe the HomeSeer is doing som port stuff?