From 5b47d83351f383d90d50d1ac00bd6a9749ea3c10 Mon Sep 17 00:00:00 2001 From: jbouwh Date: Wed, 25 Jun 2025 08:44:52 +0000 Subject: [PATCH] rephrase --- homeassistant/components/mqtt/strings.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/homeassistant/components/mqtt/strings.json b/homeassistant/components/mqtt/strings.json index 3bc883d8f28..6641613e932 100644 --- a/homeassistant/components/mqtt/strings.json +++ b/homeassistant/components/mqtt/strings.json @@ -639,7 +639,7 @@ }, "export_yaml": { "title": "[%key:component::mqtt::config_subentries::device::step::export::title%]", - "description": "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. Note that removing the MQTT device subentry will also remove the device from the device registry.", + "description": "The export includes the unique ID's used in the subentry configuration. You must change these ID's or remove the MQTT device subentry to avoid conflicts. Note that removing the MQTT device subentry will also remove the device from the device registry.", "data": { "yaml": "Copy the YAML configuration below:" }, @@ -649,7 +649,7 @@ }, "export_discovery": { "title": "[%key:component::mqtt::config_subentries::device::step::export::title%]", - "description": "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. Note that removing the MQTT device subentry will also remove the device from the device registry.\n\nTo allow [discovery]({url}#device-discovery-payload), the discovery payload needs to be published to the discovery topic. Copy the needed information from the fields below.", + "description": "The export includes the unique ID's used in the subentry configuration. You must change these ID's or remove the MQTT device subentry to avoid conflicts. Note that removing the MQTT device subentry will also remove the device from the device registry.\n\nTo allow [discovery]({url}#device-discovery-payload), the discovery payload needs to be published to the discovery topic. Copy the needed information from the fields below.", "data": { "discovery_topic": "Discovery topic", "discovery_payload": "Discovery payload:"