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
{{ message }}
This repository has been archived by the owner on Oct 26, 2023. It is now read-only.
I have 3 instances on 3 different rpi0w, in different rooms. All of them are used to control my AM43 blinds and to prevent conflicts when processing an MQTT command, they have topic_prefix set depending on the rpi0w's hostname.
The idea is to have up-to-date data sent to MQTT every time HASS restarts. Unfortunately, the defined topic gets concatenated with topic_prefix. It would be good to have an extra option in the topic_subscription in order to prevent such concatenation.
The text was updated successfully, but these errors were encountered:
By home assistant manual https://www.home-assistant.io/integrations/mqtt/#birth-and-last-will-messages - By default, Home Assistant sends online and offline to homeassistant/status. Adding prefix to this topic is a bug in my opinion, because other mqtt gateways then wont receive birth notifications, if we customize birth message in home assistant to match bluetooth gateway config.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have 3 instances on 3 different rpi0w, in different rooms. All of them are used to control my AM43 blinds and to prevent conflicts when processing an MQTT command, they have
topic_prefix
set depending on the rpi0w's hostname.In the config I have the following bit:
The idea is to have up-to-date data sent to MQTT every time HASS restarts. Unfortunately, the defined
topic
gets concatenated withtopic_prefix
. It would be good to have an extra option in thetopic_subscription
in order to prevent such concatenation.The text was updated successfully, but these errors were encountered: