Ilya Kirov

@kaciker I apologize for the delay. but I need a herdsman log... did you run this command: `DEBUG=zigbee-herdsman* npm start` Your console should display a lot of information that needs...

@kaciker it is not a "herdsman log". it should have a lot of lowlevel data (uart packets). it is issued by the command that I wrote above.

@kaciker this is again not a herdsman log. it should look different, like this: ``` kirov@kirov-home:~/Projects/zigbee2mqtt$ DEBUG=zigbee* npm start > [email protected] start /home/kirov/Projects/zigbee2mqtt > node index.js Zigbee2MQTT requires node version...

@Vladimir1604 I do not see what led to errors in your log, maybe a problem with connecting the stick? are you using a usb extension cable? please record [herdsman log](https://www.zigbee2mqtt.io/guide/usage/debug.html#zigbee-herdsman-debug-logging)...

@kaciker now the correct log, but this is not enough, you need to record a similar log before the errors occur in order to see their cause. I don't know...

@Vladimir1604 Use pastebin type services for large logs. Yes, now the correct log. But I don't see any errors in it.

@kaciker try the current dev/edge version of z2m

@kaciker sorry for delay. you have an interesting log - useful. this is the first time I've seen packets being resent from the chip to the host: ``` 2022-11-06T20:16:39.320Z zigbee-herdsman:adapter:ezsp:uart

@kaciker it looks like communication problems between the z2m host and your tcp-port on gateway.

@MattWestb already implemented in dev/edge version z2m