HASS.Agent Satellite randomly stops sending out MQTT after hibernate or sleep
Setup:
- HASS.Agent 2.1.0-beta1 [BETA}
- Tailscale connecting the desktop to Pi, requesting DNS from PiHole
- Docker on Pi
- mosquitto 2.0.18
- HA Core 2024.3.0 - but problem has been since at least 2024.1.0 version
---
Expected behaviour:
- HASS.Agent Satellite should keep sending MQTT info for sensors and commands after waking from hibernate/sleep.
Actual behaviour:
- HASS.Agent Satellite does not send out MQTT info, seems to be after waking from hibernate/sleep.
- I have noticed the normal HASS.Agent sometimes does this too but to a lesser and even less replicable degree
- Comment: Pull Request #51 may have provided a fix for this, I'll check again later with the settings enabled
---
Relevant Github things:
- Bug: Reconnecting MQTT not working properly #35
- Feature: ability to ignore MQTT grace period after waking up from hibernation #51
- Notably, this fix does not address the Satellite portion.
Edit 1:
Restarting HASS.Agent does not fix this problem, notably restarting the Satellite service does (duh).
Probably good to put a restart service button in HASS.Agent.
18 Replies
hm, just to be clear, the issue is that after hibernation/sleep the HASS.Agent satellite service doesn't send any messages and doesn't react to commands until restarted?
correct, the way I set it is that Home Assistant will look at loggeduser to decide what to display
so every time Satellite service breaks, it displays nothing
could you please see if you have satellite logs from the time this occured?
satellite is installed in the programfiles
The system halted from 07:00 to 22:00
right now it says connected, but nothing is showing up
same thing with the normal hass.agent too
when in normal situation, it would be like this
Update: this is the correct response (so far)
Mqtt issues for sure then
Mqtt explorer?
Are entities still there?
i'll check in a bit
note: this was mistaken, I don't think this is actually true, I rechecked and it's reported as unavailable
note again:
Commands sent can be received properly. just sensors are not working
Back with more info, some very interesting things
I thought the bug was related to my unique setup where the pi runs tailscale, and HASS is hooked through tailscale DNS
but I switched over to direct local IP and the issue persists
MQTT explorer shows the changes properly
but HA just doesn't pick it up, for whatever reason
Both satellite and core HASS are broken if:
- the pi restarts, regardless of local/tailscale ip
But it's fine if:
- disconnection happens on the client side, at least on the short term
Hm, how long is your mqtt grace period in the settings?
60 seconds