Add YAML and discovery info export feature for MQTT device subentries #141896
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hey there @emontnemery, @bdraco, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
1af3b60 to
d3b845f
Compare
d3b845f to
ec41abd
Compare
emontnemery
reviewed
Jun 25, 2025
| }, | ||
| "export": { | ||
| "title": "Export MQTT device config", | ||
| "description": "An export allows you set up the MQTT Device configuration via YAMl or MQTT discovery. The configuration can also be helpful for troubleshooting. The export includes the unique ID's used in the configuration. You cannot activate this configuration unless you remove the MQTT-device or change the unique id's. Removing the MQTT device subentry will also remove the device from the device registry. After removing the MQTT device subentry, it can be set up via YAML or discovery with the same unique ID's.", |
There was a problem hiding this comment.
It's not clear to me as a user what exactly I need to change.
Also, if I don't change it, how am I notified? Does the MQTT integration catch the duplicates, or will I get some cryptic error message about Platform mqtt does not generate unique IDs.?
8acd353 to
9747ebc
Compare
|
Drafting for now to allow a repair issue to remove the subentry in case an exported item was discovered or added in YAML. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
Add YAML and discovery info export feature for MQTT device subentries.
Optional refactoring after implementation of: home-assistant/architecture#1215
The current implementation uses normal a normal
TextSelectorandTemplateSelector withread_onlyflag enabled.Suggestion is to use this as initial implemention and improve the selectors with copy buttons as soon as the frontend is ready to support this.
YAML export:
Discovery export:
This allows users to move their MQTT subentries to a YAML or discovery based setup and enables to share the active config for diagnostic purposes.
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: