You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've connected an ebusd device to Home Assistant via MQTT.
When monitoring the published MQTT topics, I notice some unexpected behavior:
Some topics are published even though I have never polled them (neither via MQTT nor ebusctl).
Some topics appear very infrequently (only every few hours).
To address this, I set up an automation in Home Assistant to periodically trigger the get command with a polling priority:
With this setup, I expect bai/Flame to be updated as frequently as possible, while other topics may update less often.
However, what I observe is:
The temperature reported by ebusd/bai/Status01 (which I never explicitly requested) decreases, while bai/Flame does not update to "off" as expected.
I see frequent updates for unrelated topics likeebusd/ctlv2/Z3SFMode, even though I don’t have a Z3 circuit at all.
My Questions:
Is my approach of actively polling messages correct?
Could these unintended messages be blocking the queue?
Can I prevent the device from polling or publishing these unwanted topics?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I've connected an ebusd device to Home Assistant via MQTT.
When monitoring the published MQTT topics, I notice some unexpected behavior:
Some topics are published even though I have never polled them (neither via MQTT nor ebusctl).
Some topics appear very infrequently (only every few hours).
To address this, I set up an automation in Home Assistant to periodically trigger the get command with a polling priority:
With this setup, I expect bai/Flame to be updated as frequently as possible, while other topics may update less often.
However, what I observe is:
The temperature reported by ebusd/bai/Status01 (which I never explicitly requested) decreases, while bai/Flame does not update to "off" as expected.
I see frequent updates for unrelated topics like
ebusd/ctlv2/Z3SFMode
, even though I don’t have a Z3 circuit at all.My Questions:
Thanks a lot for your help!
Beta Was this translation helpful? Give feedback.
All reactions