Closed a-cesari closed 4 months ago
You may want to show us your configurations (working and not working ones)
Thank @mib1185 for taking on this. I added some more info. Let me know if it's enough or if you need something else in particular
Hey there @emontnemery, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (mqtt
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
mqtt documentation mqtt source (message by IssueLinks)
See: https://www.home-assistant.io/docs/configuration/splitting_configuration/
May be you have an indention problem. I tried to reproduce, (did not use your config as it is not valid), but can only conclude that it works as expected. So this not an issue with Home Assistant.
The problem
I'm trying to add several MQTT switches (via Zigbee2MQTT) and covers (via shelly MQTT) via configuration.yaml. The configurations is fine as all the devices (including availability and state reporting) work fine if added separately (i.e. commenting out the configuration for the others). However, when including all together, randomically some of them are displayed as not available or not reporting the state. The command topic is always fine. The issue seems that even if HA subscribe to the correct state topic (I can see it's subscribing from the log), it then doesn't receive any message (even if they are published on the broker. Again checked with Mqtt explorer). Also I can see that there are no messages HA side from the "MQTT info" panel of each device. It looks like HA go crazy when there are many MQTT topic to subscribe to.
What version of Home Assistant Core has the issue?
core-2024.3.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
MQTT
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
The mqtt_switches.yaml file
Anything in the logs that might be useful for us?
Additional information
No response