I have had an external MQTT server defined in my configuration.yaml file for ages. With the upgrade to 2022.3.x, I see that the use of the Configuration.yaml entry is deprecated. Has anyone removed this and used the integrations panel to add it back? Did it change any of your sensors/devices using MQTT?
Log Details (WARNING)
Logger: homeassistant.components.mqtt
Source: helpers/config_validation.py:817
Integration: MQTT ([documentation](https://www.home-assistant.io/integrations/mqtt), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+mqtt%22))
First occurred: 4:51:41 PM (4 occurrences)
Last logged: 4:51:41 PM
* The 'broker' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
* The 'discovery' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
* The 'password' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
* The 'username' option near /config/configuration.yaml:41 is deprecated, please remove it from your configuration
Could you please explain what you mean by “everything comes back”? I am getting the same deprecation messages. The configuration is working for now, but the warnings mean that they will not in the future, if deprecation means anything. I have not been able to find any documentation on this matter.
Comment out the current mqtt entry in the configuration.yaml file, restart, then go into Configuratin > Integrations and add the mqtt integration there. Everything I had working with MQTT before came back and did not have to be recreated.
I deleted my mqtt settings from configuration.yaml. Then I still had an error, so I deleted the integration, and re-added it. Indeed, everything seems to come back, but all the names are back to default again. This is a disaster. I have to find out each and every sensor, switch, dimmer, etc. Really disappointing.
It should be enough just delete it from configuration.yaml and then restart HA. Integration should remain untouched. This worked with every migration from configuration.yaml defined integrations in past to UI defined integrations after upgrade.
With an old version like that, I don’t think it matters: the old config definitely will generate errors in the new version; but I don’t know if the old version will cope with the new config.
Perhaps comment out the switch: section and the light: line, then upgrade, then sort it out int eh new version.