Since version 1.40.2-1, before and after reboot 2 error messages: MQTT error: read ECONNRESET (after stop) & 'Error: spawn udevadm ENOENT' (after start)

[alexsaas]

What happened?

After updating to the new (current) version of zigbee2MQTT, every time I restart the Home Assistant completely, or when I manually stop zigbee2MQTT and start it again, I have two error messages in the log of z2m. One before the start and one after. The first one, however, only happens with a complete restart or shutdown of home assistant. Maybe the broker or the integration stops faster when Home Assistant is shut down than zigbee2MQTT?

[2024-10-14 03:00:13] error: z2m : MQTT error: read ECONNRESET
[03:01:37] INFO: Preparing to start...
[03:01:37] INFO: Socat not enabled
[03:01:371 INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2024-10-14 03:01:39] error: zh: zstack: znp: Failed to determine if path is valid: 'Error: spawn udevadm ENOENT'

What did you expect to happen?

No more error messages like before the update.

How to reproduce it (minimal and precise)

Restart zigbee2MQTT Add-on

Zigbee2MQTT version

1.40.2-1

Adapter firmware version

20221226

Adapter

SONOFF Zigbee 3.0 USB Dongle Plus ZBDongle-P

Setup

Home Assistant Add-On, Core: 2024.9.3, Supervisor: 2024.10.0, Operating System: 13.1

Debug log

[2024-10-14 03:00:13] error: z2m : MQTT error: read ECONNRESET
[03:01:37] INFO: Preparing to start...
[03:01:37] INFO: Socat not enabled
[03:01:371 INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2024-10-14 03:01:39] error: zh: zstack: znp: Failed to determine if path is valid: 'Error: spawn udevadm ENOENT'

[alexsaas]

Update

Koenkk commented on the error 'Error: spawn udevadm ENOENT' here: https://github.com/Koenkk/zigbee2mqtt/discussions/24199#discussioncomment-10940280

So the error 'MQTT error: read ECONNRESET' still remains open.