jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-19 07:17:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove implicit setting of state_topic (#12441)

Browse Source
This commit is contained in:
Erik Montnemery 2020-03-19 16:41:58 +01:00 committed by GitHub
parent 4ea84c6d12
commit 5eeeb7aa28
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
source/_docs/mqtt/discovery.markdown
View File

@ -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
<discovery_prefix>/<component>/[<node_id>/]<object_id>/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 `<node_id>` level can be used by clients to only subscribe to their own (command) topics by using one wildcard topic like `<discovery_prefix>/+/<node_id>/+/set`.