From d4d09d9c63bce0ba284a55d4c25124a58947855f Mon Sep 17 00:00:00 2001 From: Nicholas Westerhausen Date: Sat, 24 Nov 2018 07:39:20 -0500 Subject: [PATCH] Make configuration.yaml more generic (#7607) Example configuration should not include optional configuration. To make the names configuration clearer, add a second example. --- source/_components/sensor.onewire.markdown | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/source/_components/sensor.onewire.markdown b/source/_components/sensor.onewire.markdown index 9f28de6ad70..73633a4900c 100644 --- a/source/_components/sensor.onewire.markdown +++ b/source/_components/sensor.onewire.markdown @@ -66,8 +66,6 @@ To enable One wire sensors in your installation, add the following to your `conf # Example configuration.yaml entry sensor: - platform: onewire - names: - some_id: your name ``` {% configuration %} @@ -81,3 +79,15 @@ mount_dir: type: string {% endconfiguration %} +### Configuration Example + +When `onewire` is added to Home Assistant, it will generate an ID for the sensor. You can specify a friendly name for the sensor with the name configuration option. + +```yaml +# Named sensor configuration.yaml entry +sensor: + - platform: onewire + names: + GENERATED_ID: FRIENDLY_NAME +``` +