After each restart of HA connection to MQTT/zigbee2mqtt is lost and all devices are unavailable

[skumka]

The problem

After each restart of HA connection to MQTT is lost and all devices are unavailable. You need to stop and start zigbee2mqtt to get it to work again.

When UI starts you see the status of devices and switches available for few seconds. After that time all become unavailable.
in version 116.x all was working well.

Environment

HA on Raspi in docker.

version 117.0 to 117.5

[probot-home-assistant]

mqtt documentation
mqtt source
_{^{(message by IssueLinks)}}

[frenck]

Sounds to me like an issue with zigbee2mqtt and retained messages on MQTT.

[probot-home-assistant]

Hey there @home-assistant/core, @emontnemery, mind taking a look at this issue as its been labeled with an integration (mqtt) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[skumka]

@frenck Did you analyze it and have an outcome confirming that issue is on zigbee2mqtt side? Asking because mostlikely I will be directed to HA by them. I have opened problem report on z2m github.

[marklagendijk]

I'm having the same issue.

[emontnemery]

@Koenkk could this be due to the recent change in zigbee2mqtt to use a list of availability topics to support both gateway offline setting all devices unavailable and availability for each device?

The logic should be like this: Koenkk/zigbee2mqtt#775 (comment) , is that how is implemented?

[frenck]

@frenck Did you analyze it and have an outcome confirming that issue is on zigbee2mqtt side

No, I did not. I wrote "sounds to me like" which is a guestimate.

[Koenkk]

@emontnemery I don't know what causes this issue yet but my gut feeling it is on the z2m side. I think this issue should be closed. We can reopen it if we find it's HA related. Z2M issue: Koenkk/zigbee2mqtt#4912

[skumka]

Z2M issue: Koenkk/zigbee2mqtt#4912. Closing HA issue