Zwave js ui keeps crashing Socket closed unexpectedly!

Been running Home Assistant for about 6 months now and everything seemed fine, still learning. Suddenly my zwave keeps crashing and restarting. Not sure how to troubleshoot. Any help would be appreciated.

Log:

2024-04-30 10:35:23.674 INFO Z-WAVE: [Node 062] Value updated: 38-1-targetValue 0 => 0
2024-04-30 10:35:23.676 INFO Z-WAVE: [Node 062] Value updated: 38-1-currentValue 0 => 0
2024-04-30 10:35:29.208 INFO Z-WAVE: [Node 062] Metadata updated: 50-1-value-66049
2024-04-30 10:35:29.212 INFO Z-WAVE: [Node 062] Value updated: 50-1-value-66049 0 => 0
2024-04-30 10:35:34.866 INFO APP: GET /health/zwave 301 0.963 ms - 191
2024-04-30 10:35:58.051 INFO Z-WAVE: [Node 060] Metadata updated: 49-0-Illuminance
2024-04-30 10:35:58.054 INFO Z-WAVE: [Node 060] Value updated: 49-0-Illuminance 0 => 0
2024-04-30 10:36:04.942 INFO APP: GET /health/zwave 301 1.895 ms - 191
2024-04-30 10:36:35.018 INFO APP: GET /health/zwave 301 1.739 ms - 191
2024-04-30T14:36:58.187Z DRIVER   Serial port errored: The socket closed unexpectedly! (ZW0100)
2024-04-30 10:36:58.188 INFO Z-WAVE: Controller status: Driver: Serial port errored: The socket closed unexpectedly! (ZW0100)
2024-04-30 10:36:58.189 INFO GATEWAY: Driver is CLOSED
2024-04-30 10:36:58.190 INFO Z-WAVE: Restarting client in 1 seconds, retry 1
ZWaveError: The controller is not yet ready! (ZW0103)
    at Driver.get controller [as controller] (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:766:10)
    at Timeout._onTimeout (/opt/server/lib/ZwaveClient.js:2847:30)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)
2024-04-30 10:37:37.827 INFO Z-WAVE: Setting user callbacks
1 Like

Bad connection to usb stick? Reseat it.

Power issue? What hardware you have?

Running HAOS OS on Proxmox, ZWave is an older Homeseer Znet.
I tried restoring a backup from a week ago and having the same problem.
There is no change in ping responses to the znet when ZWave JS pops up the error so I dont think it’s network related.

The error occurs at about a 3 minute regular interval.

I’m at a total loss here. I disassembled my znet and reseated the gpio board. I restored a backup from a month ago. Still lose zwave connectivity every few minutes while it reconnects and rescans devices. All zwave devices become unavailable while the integration restarts.

The only change I made that I can think of is updating my aeotec home energy meter. I have disabled all automatic reporting on it but still having issues.

2024-05-02 16:55:02.244 INFO APP: GET /health/zwave 301 0.793 ms - 191
2024-05-02T20:55:11.037Z DRIVER   Serial port errored: The socket closed unexpectedly! (ZW0100)
2024-05-02 16:55:11.038 INFO Z-WAVE: Controller status: Driver: Serial port errored: The socket closed unexpectedly! (ZW0100)
2024-05-02 16:55:11.039 INFO GATEWAY: Driver is CLOSED
2024-05-02 16:55:11.040 INFO Z-WAVE: Restarting client in 1 seconds, retry 1
ZWaveError: The controller is not yet ready! (ZW0103)
    at Driver.get controller [as controller] (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:766:10)
    at Timeout._onTimeout (/opt/server/lib/ZwaveClient.js:2847:30)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)

As far as I can tell my zwave network is stable under Homeseer but not under HomeAssistant. I must have done something wrong when transferring over.

Under Settings->Devices and services->Integrations I have Z-Wave JS listed.
Under Settings->Add-ons I have Z-Wave JS UI and Z-Wave JS listed.

Should Z-Wave JS be listed in both places?

You cannot use both add-ons at the same time. If your integration is configured to use the core add-on, then you’ll need to switch. If it’s configured for Z-Wave JS UI, then you should uninstall the core add-on.

https://www.home-assistant.io/integrations/zwave_js/#can-i-switch-between-the-official-z-wave-js-add-on-and-the-z-wave-js-ui-add-on

Can I switch between the official Z-Wave JS add-on and the Z-Wave JS UI add-on?

You can, but you cannot run them both at the same time. Only one of them can be active at the same time.

Follow the instructions in the link above to switch, or follow:

At this point I’m going to uninstall anything with zwave in it’s name and start from scratch.

Is there anything other than a reboot needed in HomeAssistant before I attempt a re-adoption of my znet?

Setting up ZWave in Homeassistant from scratch didn’t help.
I moved my znet back to Homeseer and created an event that toggles a light every 5 seconds. I then started seeing an error in the log that “posting to webhook failed” every 3 minutes. If I disable the event the error goes away.

Possible causes:
1.Something wrong with my znet
2.Something wrong with my Proxmox server
3. Something wrong with local area network
4. A Bad zwave device

Amazon is delivering a new Zooz 800 usb stick today.

No

Did you ever fix the problem with zwave js and zwavejsui being used? You can only use one or the other. This was defined your problem

According to the documentation you have to install the ZWave JS UI, configure it, and start it, then install the official ZWave JS integration but uncheck the use supervisor check box.

I have done that now and my new zooz 800 is connected directly to proxmox server by USB. The disconnect every 3 minutes error is gone however there are no zwave nodes currently adopted.

[

Zwave network is on stick

Was network working before with devices connected?

Took me a few days but I unlearned all devices from the znet using homeseer and learned them into the zooz800 using Home Assistant. When I only had the china cabinet test left I ran it and still saw the error in the homeseer log. So either the znet is the problem or possibly something on my network.

I did learn some weird things about zwave JS UI.

  1. it’s possible to add the same device twice, not sure how that’s possible but I did it.
  2. when I restart HomeAssistant there is already an inclusion running, have to go into inclusion to stop it.

I’m going to let it all run for a few days and see if it remains stable.