I’m taking advantage of @Prof_Techno’s message to also raise the issue… I was supposed to deal with it a while ago, but I kept forgetting every time.
For info @pierre-gilles, the MQTT service not reconnecting problem has been happening at my place since… forever ^^ and has never stopped!
To recontextualize, I have 2 installations at home (well actually 3 ^^ but one doesn’t update automatically ^^):
-
Gladys light is installed on a Pi 4 (Raspberry Pi 4) in the living room, it has the same devices and features as the primary Gladys but doesn’t store any history and doesn’t trigger scenes.
It just manages zigbee2mqtt in the house.
Its IP is ‹ xx.5.xx.51 ›.
During Gladys updates it reconnects without issues to the MQTT broker which is on another Pi 4 (Raspberry Pi 4) at address ‹ xx.5.xx.51 ›.
It used to be my primary Gladys and couldn’t reconnect to MQTT until I removed its scenes and value histories. -
The primary Gladys located in the IT office is installed on a Beelink mini PC (the cream of the crop ^^) and manages value histories and scenes.
It is connected to Gladys light to retrieve zigbee2mqtt info (and is awaiting a second service to manage the building’s Zigbee ^^)
Its IP is ‹ xx.5.xx.227 ›.
During Gladys updates it never reconnects to the MQTT broker which is on another Pi 4 (Raspberry Pi 4) at address ‹ xx.5.xx.51 ›. I have to reconnect it manually.
This point is very important to me because at 5:30 AM Gladys is supposed to start the hay purifier for the horses. And inevitably with every update that happens during the night the command is never sent and I get… you know what ^^
I was planning to take the time to look into it because I think it’s a reconnection timeout issue… simply clicking on the connection the next morning reconnects without issue so …