From 5eeeb7aa281630c4f92bf1f30a8d4a6b1a7425b8 Mon Sep 17 00:00:00 2001 From: Erik Montnemery Date: Thu, 19 Mar 2020 16:41:58 +0100 Subject: [PATCH] Remove implicit setting of state_topic (#12441) --- source/_docs/mqtt/discovery.markdown | 8 -------- 1 file changed, 8 deletions(-) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index 80a80e20815..cdee9b31d7e 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -61,14 +61,6 @@ 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: - -```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. The `` level can be used by clients to only subscribe to their own (command) topics by using one wildcard topic like `/+//+/set`.