hassio-addons / addon-zwave-js-ui

Z-Wave JS UI - Home Assistant Community Add-ons
https://addons.community
MIT License
130 stars 36 forks source link

socket closed unexpectedly exactly every minute #719

Closed robo-kob closed 1 month ago

robo-kob commented 1 month ago

Problem/Motivation

I have HA OS running directly on an Intel NUC. However, I would like to virtualize the system and run it on Proxmox (cluster). Therefore I want to be independent of the USB port and use the TCP functionality. I have upgraded the Z-Wave JS UI to the latest version. I am currently using a Raspberry pi 4 with a Z-Pi 7 (Razberry7) and ser2net. This worked perfectly in the beginning, but then the problems started. I have also tried it with a Raspberry pi 3 and UZB as well as with Z-Stick7 and the same problem everywhere.

Soft reset = disabled Firmware/SDK = 7.18.8

Expected behavior

No error message.

Actual behavior

I receive these error messages exactly every minute:

2024-10-24 10:13:43.312 INFO STORE: Controller status: Driver: Serial port errored: The socket closed unexpectedly! (ZW0100) 2024-10-24 10:13:43.314 INFO STORE: Driver is CLOSED 2024-10-24 10:13:43.315 INFO STORE: Restarting client in 1 seconds, retry 1 2024-10-24 10:13:44.317 DEBUG STORE: Closing server... 2024-10-24 10:13:44.324 INFO STORE: Server closed 2024-10-24 10:13:44.328 INFO STORE: Client closed 2024-10-24 10:13:44.342 INFO STORE: Connecting to tcp://192.168.178.60:4000 2024-10-24 10:13:44.343 INFO STORE: Setting user callbacks 2024-10-24 10:13:44.355 INFO STORE: Zwavejs usage statistics ENABLED 2024-10-24 10:13:44.356 WARN STORE: Zwavejs driver is not ready yet, statistics will be enabled on driver initialization 2024-10-24 10:13:49.120 INFO STORE: Driver is READY 2024-10-24 10:13:49.120 INFO STORE: Z-Wave driver is ready 2024-10-24 10:13:49.120 INFO STORE: Controller status: Driver ready

Steps to reproduce

This happens every minute. Then all nodes are displayed again for one minute.

Proposed changes

Driver problem?

robo-kob commented 1 month ago

How stupid of me!

I checked the port for availability every minute with uptime Kuma. That must have caused the problem. Sorry!