From 3ab0bbc0e2ef5df4588a27df39908dd2a6947e42 Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Thu, 24 Sep 2015 15:42:38 -0400 Subject: [PATCH 1/4] Added line about sensor, sensor 2, 3, etc.. Since we don't have an actual sensor page, I think this is the best place for it to go so new users will get the gist of the format. --- source/getting-started/devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/devices.markdown b/source/getting-started/devices.markdown index caf9128ce9c..32dce060521 100644 --- a/source/getting-started/devices.markdown +++ b/source/getting-started/devices.markdown @@ -14,7 +14,7 @@ routers, Belkin WeMo switches, Philips Hue bridges and Sonos speakers in your ne [the discovery component]({{site_root}}/components/discovery.html) enabled (which is by default). See the [components overview page](/components/) to find installation instructions for your devices -and services. +and services. Many components use the `sensor` platform. Sensors need to be added into the `configuration.yaml` as `sensor:`, `sensor 2:`, `sensor 3:`, etc. There should not be gaps in the sequence or your sensors might not load correctly. To get the most out of automation, it is useful to setup the following things: From 7025cdb35b31270e59bbcf166b8995aabffedfc4 Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Thu, 24 Sep 2015 16:39:36 -0400 Subject: [PATCH 2/4] Add comment clarifying that options are optional. Add comment clarifying that customize options are optional. --- source/getting-started/devices.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/getting-started/devices.markdown b/source/getting-started/devices.markdown index 32dce060521..0d522344b1a 100644 --- a/source/getting-started/devices.markdown +++ b/source/getting-started/devices.markdown @@ -51,6 +51,7 @@ of these parameters. This can be done by adding the following config to the `hom homeassistant: # Add this to your existing configuration + # Only the `entity_id` is required. All other options are optional. customize: some.entity_id: hidden: true From 2298141ea7736c7ee7140dc7fb5db0c4c69c9e20 Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Fri, 25 Sep 2015 11:10:27 -0400 Subject: [PATCH 3/4] Added additional Note Added catch-all note the show the format applies to most other components. -I didn't initially write it in since I am hoping the new dash format used in the automation component would spread to others like sensor. --- source/getting-started/devices.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/getting-started/devices.markdown b/source/getting-started/devices.markdown index 0d522344b1a..36c79538cdc 100644 --- a/source/getting-started/devices.markdown +++ b/source/getting-started/devices.markdown @@ -15,6 +15,9 @@ routers, Belkin WeMo switches, Philips Hue bridges and Sonos speakers in your ne See the [components overview page](/components/) to find installation instructions for your devices and services. Many components use the `sensor` platform. Sensors need to be added into the `configuration.yaml` as `sensor:`, `sensor 2:`, `sensor 3:`, etc. There should not be gaps in the sequence or your sensors might not load correctly. +

+Most components that support multiple entries within the `configuration.yaml` follow the `component:`, `component 2:` format. +

To get the most out of automation, it is useful to setup the following things: From a362cec256f0273be29138eabbf4a90eb5c8efda Mon Sep 17 00:00:00 2001 From: Carlo Costanzo Date: Fri, 25 Sep 2015 17:56:58 -0400 Subject: [PATCH 4/4] Updated with Updated with --- source/getting-started/devices.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/getting-started/devices.markdown b/source/getting-started/devices.markdown index 36c79538cdc..c467f6e61b8 100644 --- a/source/getting-started/devices.markdown +++ b/source/getting-started/devices.markdown @@ -16,7 +16,7 @@ routers, Belkin WeMo switches, Philips Hue bridges and Sonos speakers in your ne See the [components overview page](/components/) to find installation instructions for your devices and services. Many components use the `sensor` platform. Sensors need to be added into the `configuration.yaml` as `sensor:`, `sensor 2:`, `sensor 3:`, etc. There should not be gaps in the sequence or your sensors might not load correctly.

-Most components that support multiple entries within the `configuration.yaml` follow the `component:`, `component 2:` format. +Most components that support multiple entries within the configuration.yaml follow the component:, component 2: format.

To get the most out of automation, it is useful to setup the following things: