Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost network socket connection without recovery by watchdog. #26624

Open
weekends opened this issue Mar 6, 2025 · 2 comments
Open

Lost network socket connection without recovery by watchdog. #26624

weekends opened this issue Mar 6, 2025 · 2 comments
Labels
problem Something isn't working

Comments

@weekends
Copy link

weekends commented Mar 6, 2025

What happened?

I'm have 2 installation in different places HA+z2m. Use 2 different adapters, one is ZigStarGW with FW: 20240914 second SLZB-06 with FW: v2.8.2.dev3. Bought of them use zigbee fw: 20240710. After update to 2.1.x version i'm has trouble once in 2-4 days on bought configurations:

2025-03-06 13:12:14] error: zh:zstack:znp: Socket error Error: read ECONNRESET
[2025-03-06 13:12:14] error: z2m: Adapter disconnected, stopping
[2025-03-06 13:12:14] error: z2m: MQTT error: write ECONNRESET

WatchDog can't help, more then 1:30 hour nothing change. Only manual z2m restart in HA restore work.

What did you expect to happen?

Updating to 2.1.x z2m version. Bought configuration work fine with out any issues near 1 year before update.

How to reproduce it (minimal and precise)

On my side - simple - restart z2m and wait 2-4 days, till z2m crashed.

Zigbee2MQTT version

2.1.3

Adapter firmware version

20240710

Adapter

ZigStarGW, SLZB-06

Setup

Add-on on HomeAssistant

Debug log

I'm add debug log later. Now turn it on and wait for crash.

@weekends weekends added the problem Something isn't working label Mar 6, 2025
@Nerivec
Copy link
Collaborator

Nerivec commented Mar 6, 2025

Since both MQTT and the adapter lose connection, looks like you are having issues with your network.
You should start looking there.
Any configuration changes in your network, updates, etc., anything that may trigger at a specific interval (2-4 days) that could be crowding the network...
Try restarting your modem/router, check firewalls, antivirus, etc.

@weekends
Copy link
Author

weekends commented Mar 7, 2025

There are no any changes in network configuration. On one of the configurations, network completely separated only for automation. All IP's in network static, ping's and web access to adapter work with out any issues. Socket also accessed when z2m wrote, that can't. Restart of the z2m fix problem for the time...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants