From 4ff8107c739bf161d5003c05675fbe59c433749d Mon Sep 17 00:00:00 2001 From: Otto Winter Date: Tue, 6 Mar 2018 21:18:27 +0100 Subject: [PATCH] Fix MQTT discovery object_id docs (#4761) * Fix MQTT discovery object_id docs * Update format --- source/_docs/mqtt/discovery.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/mqtt/discovery.markdown b/source/_docs/mqtt/discovery.markdown index a0f3737cbce..51eae400c43 100644 --- a/source/_docs/mqtt/discovery.markdown +++ b/source/_docs/mqtt/discovery.markdown @@ -44,7 +44,7 @@ The discovery topic need to follow a specific format: - ``: One of the supported components, eg. `binary_sensor`. - ``: (*Optional*) id of the node providing the topic. -- ``: The ID of the device. This will become the `entity_id` in Home Assistant. +- ``: "The ID of the device. This is only to allow for separate topics for each device and is not used for the `entity_id`." - `<>`: The topic `config` or `state` which defines the current action. The payload 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`.