Configuration.yaml requirements are not clear

[Bart56]

Feedback

I'm running HA Supervised Version 2022.7.7. Mosquitto is the latest version from the add-on store (I tried to find the version but not in the diagnostic log). The instructions for configuration do not show any dependencies on the configuration.yaml file except the statement "Some broker configuration options can’t be set via the user interface, but require changes of your configuration.yaml" I managed to find that there are format changes from my old version (HA 0.107.4). But after those changes were made to the configuration file, it would not find all my sensors. I tried many changes and found that configuration.yaml seems to require the same info as the MQT config (Broker, Port, User, passwd) plus if I have more than one sensor, they must be listed under one "sensor:" tag under the mqtt: tag

` mqqt: Broker: port: Username: Password:

sensor: -unique_id: dev_1 name: "dev 1" state_topic: "sensor/topic1" qos: 0

-unique_id: dev_2 
  name: "dev 2"
  state_topic: "sensor/topic2"
  qos: 0

switch: -unique_id: sw-1 name: "sw 1" state_topic: "sensor/topicsw1" qos: 0

` This seemed to work and HA found all m devices. It was dumb luck. I found no documentation for this, and I may still have it wrong, so I am suggesting the configuration.yaml requirements be mentioned (listed) on the https://www.home-assistant.io/docs/mqtt/broker page. Thanks.

URL

https://www.home-assistant.io/docs/mqtt/broker/

Version

2022.7.7

Additional information

None really. I just wished the requirements were documented -or- if they are, placed in a conspicuously related place.

[Bart56]

I indented all the configuration file parameters, but they didn't show up properly in the post.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.