jeans/core
jeans/core
1
0
Fork 0
mirror of https://github.com/home-assistant/core.git synced 2025-07-18 18:57:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Explain the user can change the identifiers if the subentry is to be kept

Browse Source
This commit is contained in:
jbouwh 2025-07-15 19:58:33 +00:00
parent 9ba6056935
commit 19d03f3caa
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
homeassistant/components/mqtt/strings.json
View File

@ -661,7 +661,7 @@
},
"export_yaml": {
"title": "[%key:component::mqtt::config_subentries::device::step::export::title%]",
"description": "You can copy the configuration below and place it your configuration.yaml file. Home Assistant will detect if the setup of the MQTT device was tried via YAML instead, and will offer a repair flow to clean up the redundant subentry.",
"description": "You can copy the configuration below and place it your configuration.yaml file. Home Assistant will detect if the setup of the MQTT device was tried via YAML instead, and will offer a repair flow to clean up the redundant subentry. You can also choose to change the identifiers if you do not want to remove the subentry.",
"data": {
"yaml": "Copy the YAML configuration below:"
},
@ -671,7 +671,7 @@
},
"export_discovery": {
"title": "[%key:component::mqtt::config_subentries::device::step::export::title%]",
"description": "To allow setup via MQTT [discovery]({url}#device-discovery-payload), the discovery payload needs to be published to the discovery topic. Copy the information from the fields below. Home Assistant will detect if the setup of the MQTT device was tried via MQTT discovery instead, and will offer a repair flow to clean up the redundant subentry.",
"description": "To allow setup via MQTT [discovery]({url}#device-discovery-payload), the discovery payload needs to be published to the discovery topic. Copy the information from the fields below. Home Assistant will detect if the setup of the MQTT device was tried via MQTT discovery instead, and will offer a repair flow to clean up the redundant subentry. You can also choose to change the identifiers if you do not want to remove the subentry.",
"data": {
"discovery_topic": "Discovery topic",
"discovery_payload": "Discovery payload:"

2
tests/components/mqtt/test_repairs.py
View File

@ -140,6 +140,8 @@ async def test_subentry_reconfigure_export_settings(
assert device is not None
# Assert a repair flow was created
# This happens when the exported device identifier was detected
# The subentry ID is used as device identifier
assert len(events) == 1
issue_id = events[0].data["issue_id"]
issue_registry = ir.async_get(hass)