Everything unavailable when z2m restarts/crashes

[copystring]

What happened?

It looks like z2m crashed and restarted. When this happens every device is marked as unavailable and only sometimes return to available.

What did you expect to happen?

Maybe it makes more sense to automatically restart the adapter when there's a connection loss instead of endlessly trying to reconnect?
Also as you can see in the third screenshot of the logs it seems like iobroker.zigbee2mqtt behaves different than a restart when the connection ist lost which seems to be the reason the devices do not always turn back to being available.

How to reproduce it (minimal and precise)

Wait for z2m to restart for example be connection loss of the adapter.

Adapter version

2.4.4

Log

Disconnect:

Eventually z2m works again and iobroker.zigbee2mqtt reconnects:

This is what it looks like when manually restarting iobroker.zigbee2mqtt:

[o0shojo0o]

What happened?

It looks like z2m crashed and restarted. When this happens every device is marked as unavailable and only sometimes return to available.

I have now tried so several things, but do not get this behavior readjusted, then z2m always sends all available states on a new connection.

Maybe it makes more sense to automatically restart the adapter when there's a connection loss instead of endlessly trying to reconnect?

The websocket connection is completely reinitialized, as with an adapter restart, that would make no difference.
Also a full adapter restart would be a problem for users using the 'dummy MQTT server' from the adapter, for them it would end in an endless loop.

Also as you can see in the third screenshot of the logs it seems like iobroker.zigbee2mqtt behaves different than a restart when the connection ist lost which seems to be the reason the devices do not always turn back to being available.

No this is only because I suppress the log when an adapter is running and reconnects.
https://github.com/o0shojo0o/ioBroker.zigbee2mqtt/blob/ea52abe240a43fe729f7236773281f92b27264d0/main.js#L142-L146

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[o0shojo0o]

I assume from your other issues (#148) that you are using the MQTT connection type here.
Please switch to the websocket connection.

[copystring]

I do still have this Problem.
For example this device:

As you can see it's clearly available in z2m but not in the ioBroker adapter.
A few seconds later everything is online again.

🤷‍♂️

I will try to get a log when this happens the next time.

[copystring]

I have not been able to get a good log for this, but I'm still confident it has something to do with the websocket connection reconnecting.

For example, this light:

All the other devices have the same available timestamp as this light, which is roughly 10 seconds after websocket reconnected.

Here's a log with the time range https://pastebin.com/XNcRB09a

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days