From 4e9d459aec8e0cb1b65f4d043673ff2251b2635e Mon Sep 17 00:00:00 2001 From: VivantSenior <49829548+VivantSenior@users.noreply.github.com> Date: Sat, 16 Nov 2019 20:25:53 +0100 Subject: [PATCH] Change in just a layout (#11178) --- source/_docs/mqtt/discovery.markdown | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index debd51fb9f2..dab05ec8b67 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -60,7 +60,13 @@ The discovery topic need to follow a specific format: The payload must be a JSON dictionary and will be checked like an entry in your `configuration.yaml` file if a new device is added. This means that missing variables will be filled with the platform's default values. All configuration variables which are *required* must be present in the initial payload send to `/config`. -If the integration is `alarm_control_panel`, `binary_sensor`, or `sensor` and the mandatory `state_topic` is not present in the payload, `state_topic` will be automatically set to //[/]/state. The automatic setting of `state_topic` is deprecated and may be removed in a future version of Home Assistant. +If the integration is `alarm_control_panel`, `binary_sensor`, or `sensor` and the mandatory `state_topic` is not present in the payload, `state_topic` will be automatically set to: + +```text +//[/]/state +``` + +The automatic setting of `state_topic` is deprecated and may be removed in a future version of Home Assistant. An empty payload will cause a previously discovered device to be deleted.