In addition to the APCUPSd Sensor devices, you may also create a device which is simply “on” when the UPS status is online and “off” at all other times.
-To enable this sensor, add the following lines to your configuration.yaml file:
To enable this sensor, you first have to set up apcupsd, and add the following lines to your configuration.yaml file:
# Example configuration.yaml entry
binary_sensor:
diff --git a/components/camera.netatmo/index.html b/components/camera.netatmo/index.html
index 73c6c94017..6f905bc779 100644
--- a/components/camera.netatmo/index.html
+++ b/components/camera.netatmo/index.html
@@ -91,7 +91,7 @@
The netatmo camera platform is consuming the information provided by a Netatmo Welcome camera. This component allows you to view the current photo created by the Camera.
-To enable the Netatmo camera, add the following lines to your configuration.yaml:
+To enable the Netatmo camera, you first have to set up netatmo, and add the following lines to your configuration.yaml:
# Example configuration.yaml entry
camera:
diff --git a/components/http/index.html b/components/http/index.html
index 68c992fe09..e31042d991 100644
--- a/components/http/index.html
+++ b/components/http/index.html
@@ -129,7 +129,7 @@ It’s HIGHLY recommended that you set the api_p
All requests need to be sent to the endpoint of the device and must be POST.
-If you want to host static files on your site this canbe done by making a www directory under the .htomassistant configuration path. Then static files in .homeassistant/www/ can be accessed by using http://your.domain:8123/local/
+If you want to use Home Assistant to host or serve static files then create a directory called www under the .homeassistant configuration path. The static files in .homeassistant/www/ can be accessed by the following URL http://your.domain:8123/local/.
diff --git a/components/sensor.apcupsd/index.html b/components/sensor.apcupsd/index.html
index f5bcdaf590..a79de99d8f 100644
--- a/components/sensor.apcupsd/index.html
+++ b/components/sensor.apcupsd/index.html
@@ -91,7 +91,7 @@
The apcupsd sensor platform allows you to monitor a UPS (battery backup) by using data from the apcaccess command.
-To use this sensor platform, you first have to set up apcupsd and add the following to your configuration.yaml file:
+To use this sensor platform, you first have to set up apcupsd, and add the following to your configuration.yaml file:
# Example configuration.yaml entry
sensor:
diff --git a/components/sensor.netatmo/index.html b/components/sensor.netatmo/index.html
index 318be0a293..9263706c43 100644
--- a/components/sensor.netatmo/index.html
+++ b/components/sensor.netatmo/index.html
@@ -91,7 +91,7 @@
The netatmo sensor platform is consuming the information provided by a Netatmo device.
-To enable the Netatmo sensor, add the following lines to your configuration.yaml:
+To enable the Netatmo sensor, you first have to set up netatmo, and add the following lines to your configuration.yaml:
# Example configuration.yaml entry
sensor:
@@ -131,7 +131,7 @@
Configuration variables:
- - station (Optionnal): The name of the weather station. Needed if several stations are associated with the account.
+ - station (Optional): The name of the weather station. Needed if several stations are associated with the account.
- modules (Required): Modules to use. Multiple entries allowed.
- module_name array (Required): Name of the module.
@@ -161,8 +161,7 @@
Find your modules name
-You can find your modules name in your online NetAtmo account. These names can be found and changed in parameters (See screenshot)
-You have to provide these name in your Home Assistant configuration file.
+You can find your modules name in your online NetAtmo account. These names can be found and changed in parameters. You have to provide these name in your Home Assistant configuration.yaml file.
diff --git a/components/switch.netio/index.html b/components/switch.netio/index.html
index b15f754602..248d005df4 100644
--- a/components/switch.netio/index.html
+++ b/components/switch.netio/index.html
@@ -93,17 +93,17 @@
To use Netio devices in your installation, add the following to your configuration.yaml file:
-# Example configuration.yaml entry
-switch:
- - platform: netio
- host: 192.168.1.43
- port: 1234
- username: user
- password: pwd
- outlets:
- 1: Free
- 2: TV
- 4: Lamp
+# Example configuration.yaml entry
+switch:
+ - platform: netio
+ host: 192.168.1.43
+ port: 1234
+ username: user
+ password: pwd
+ outlets:
+ 1: Free
+ 2: TV
+ 4: Lamp
diff --git a/components/switch.pulseaudio_loopback/index.html b/components/switch.pulseaudio_loopback/index.html
index 675f9a268b..2f82619d1d 100644
--- a/components/switch.pulseaudio_loopback/index.html
+++ b/components/switch.pulseaudio_loopback/index.html
@@ -89,24 +89,24 @@
- The goal behind this switch is to allow a very flexible whole home audio system based upon PulseAudio.
+ The goal behind this switch is to allow a very flexible whole home audio system based upon PulseAudio.
-For example, for a system with a 7.1 surround sound card, and 3 instances of mpd running, it is possible to quickly route the output of any mpd instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is ‘on’, the loopback module is loaded. When the switch is ‘off’, the module is not loaded.
+For example, for a system with a 7.1 surround sound card, and 3 instances of MPD running, it is possible to quickly route the output of any MPD instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is on, the loopback module is loaded. When the switch is off, the module is not loaded.
-The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of mpd or PulseAudio.
+The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of MPD or PulseAudio.
-This component uses a TCP connection to control a local or remote PulseAudio server- so there are no local dependencies.
+This component uses a TCP connection to control a local or remote PulseAudio server. So there are no local dependencies.
To enable this switch, add the following lines to your configuration.yaml file:
# Example configuration.yaml entry
switch:
- platform: pulseaudio_loopback
- name: mpd1 -> bedroom
- host: 127.0.0.1
- port: 4712
- source_name: mpd1.monitor
- sink_name: bedroom
+ - platform: pulseaudio_loopback
+ name: mpd1 -> bedroom
+ host: 127.0.0.1
+ port: 4712
+ source_name: mpd1.monitor
+ sink_name: bedroom
@@ -123,8 +123,7 @@
-This component relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with
-this component, module-cli-protocol must be loaded on the PulseAudio server.
+This component relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with this component, module-cli-protocol must be loaded on the PulseAudio server.
diff --git a/sitemap.xml b/sitemap.xml
index ccd04f5a9b..4a32f47c67 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1980,62 +1980,62 @@
https://home-assistant.io/demo/frontend.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/index.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00
https://home-assistant.io/static/mdi-demo.html
-2016-09-04T09:45:43+00:00
+2016-09-04T09:50:28+00:00