A configuration section of an automation requires a trigger and an action section. condition and condition_type are optional. To keep this page compact, all following sections will not show the full configuration but only the relevant part.
# Example of entry in configuration.yaml automation: @@ -173,12 +179,6 @@
Triggers
Triggers are what starts the processing of an automation rule. It is possible to specify multiple triggers for the same rule. Once a trigger starts, Home Assistant will validate the conditions, if any, and call the action.
@@ -329,9 +329,9 @@Conditions
-Conditions are an optional part of an automation rule and be used to prevent an action from happening when triggered. Conditions look very familiar to triggers but are very different. A trigger will look at events happening at the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is on or off.
+Conditions are an optional part of an automation rule and be used to prevent an action from happening when triggered. Conditions look very similar to triggers but are very different. A trigger will look at events happening in the system while a condition only looks at how the system looks right now. A trigger can observe that a switch is being turned on. A condition can only see if a switch is currently on or off.
-An automation rule can have mulitiple conditions. By default the action will only fire if all conditions pass. An optional key condition_type: 'or' can be set on the automation rule to fire action if any condition matches. In the example below, the automation would trigger if the time is before 05:00 OR after 20:00.
An automation rule can have multiple conditions. By default the action will only fire if all conditions pass. An optional key condition_type: 'or' can be set on the automation rule to fire action if any condition matches. In the example below, the automation would trigger if the time is before 05:00 OR after 20:00.
automation: @@ -356,18 +356,17 @@Numeric state condition
-Attempts to parse the state of specified entity as a number and triggers if value is above and/or below a threshold.
+This type of condition attempts to parse the state of specified entity as a number and triggers if the value matches all of the above or below thresholds.
+Eitheraboveorbelow, or both need to be specified. If both are used, the condition is true when the value is >=before*and** <after.
+You can optionally use avalue_templateto make the value of the entity the same type of value as the condition.@@ -387,7 +386,6 @@ hours: 1 minutes: 10 seconds: 5 -automation: condition: platform: numeric_state entity_id: sensor.temperature - # At least one of the following required above: 17 below: 25 - # Optional - value_template: '{{ state.attributes.battery }}'
Template condition
-The template condition will test if given template renders a value equal to true. This is achieved by having the template result in a true boolean expression or by having the template render ‘true’.
+The template condition will test if the given template renders a value equal to true. This is achieved by having the template result in a true boolean expression or by having the template render ‘true’.
automation: @@ -459,7 +457,7 @@Actions
-When an automation rule fires, it calls a service. For this service you can specify an entity id it should apply to and optional service parameters (to specify for example the brightness).
+When an automation rule fires, it calls a service. For this service you can specify the entity_id that it should apply to and optional service parameters (to specify for example the brightness).
-automation: @@ -487,11 +485,11 @@If you want to specify multiple services to be called or include a delay, have a look at the script component. If you want to describe how certain entities should look, check out the scene component.
+If you want to specify multiple services to be called, or to include a delay, have a look at the script component. If you want to describe the desired state of certain entities, check out the scene component.
Troubleshooting
-You can verify that your automation rules are being initialized correctly by watching both the realtime logs and also the logbook. The realtime logs will show the rules being initialized (once for each trigger):
+You can verify that your automation rules are being initialized correctly by watching both the realtime logs (
homeassistant.login the configuration directory) and also the Logbook. The realtime logs will show the rules being initialized (once for each trigger), example:-INFO [homeassistant.components.automation] Initialized rule Rainy Day @@ -502,7 +500,7 @@ INFO [homeassistant.components.automation] Initialized rule Rain is overThe Logbook component will show a line entry when an automation is triggered. You can look at the previous entry to determine which trigger in the rule triggered the event.
+The Logbook component will show a line entry when an automation is triggered. You can look at the previous entry to determine which trigger in the rule triggered the event.
diff --git a/components/conversation/index.html b/components/conversation/index.html index a4a3f1bb8f..4b33d87918 100644 --- a/components/conversation/index.html +++ b/components/conversation/index.html @@ -130,6 +130,10 @@
+
+Apple iPhones do not support this feature in any browser. +
+ diff --git a/components/http/index.html b/components/http/index.html index 1b34c7fad5..3b036cfcc9 100644 --- a/components/http/index.html +++ b/components/http/index.html @@ -139,11 +139,11 @@On top of the
-httpcomponent is a REST API and a Python API available.The
+httpplatforms are not a real platform within the meaning of the terminology used around Home Assistant. Home Assistant’s REST API is consuming and proceeding messages received over HTTP.The
httpplatforms are not real platforms within the meaning of the terminology used around Home Assistant. Home Assistant’s REST API sends and receives messages over HTTP.To use those kind of sensors in your installation no configuration in Home Assistant is needed. All configuration is done on the devices themselves. This means that you must be able to edit the target URL or endpoint and the payload. The entity will be created after the first message has arrived.
-All requests needs to be sent to the endpoint of the device and must be POST.
+All requests need to be sent to the endpoint of the device and must be POST.
diff --git a/components/input_boolean/index.html b/components/input_boolean/index.html index c08ee33945..0e2925888a 100644 --- a/components/input_boolean/index.html +++ b/components/input_boolean/index.html @@ -119,7 +119,7 @@@@ -137,6 +137,27 @@# Example configuration.yaml entry input_boolean: notify_home: - name: Notify when someome arrives home + name: Notify when someone arrives home initial: off icon: mdi:carPick an icon that you can find on materialdesignicons.com to use for your input and prefix the name with
+mdi:. For examplemdi:car,mdi:ambulance, ormdi:motorbike.Here’s an example of an automation using the above input_boolean. This action will only occur if the switch is on.
+ +diff --git a/components/logger/index.html b/components/logger/index.html index 9036b1f1a9..c75df7d40a 100644 --- a/components/logger/index.html +++ b/components/logger/index.html @@ -113,11 +113,11 @@+++automation: + alias: Arriving home + trigger: + platform: state + entity_id: binary_sensor.motion_garage + to: 'on' + condition: + platform: state + entity_id: input_boolean.notify_home + state: 'on' + action: + service: notify.pushbullet + data: + title: "" + message: "Honey, I'm home!" +
-The logger component lets one define the level of logging activities in Home Assistant.
+The logger component lets you define the level of logging activities in Home Assistant.
To enable the logger in your installation, add the following to your
-configuration.yamlfile:By default log all messages and ignore log event lowest than critical for custom omponents.
+By default log all messages and ignore events lower than critical for specified components.
-# Example configuration.yaml entry @@ -130,7 +130,7 @@By default ignore all messages lowest than critical and log event for custom components.
+By default ignore all messages lower than critical and log event for specified components.
# Example configuration.yaml entry @@ -148,7 +148,7 @@Possible log severities are:
-
- citical
+- critical
- fatal
- error
- warning
diff --git a/components/scene/index.html b/components/scene/index.html index f208c58f6c..6198ee0bc7 100644 --- a/components/scene/index.html +++ b/components/scene/index.html @@ -113,9 +113,7 @@
-A user can create scenes that capture the states you want certain entities to be. For example a scene can contain that light A should be turned on and light B should be bright red.
- -Scenes can be activated using the service
+scene.turn_on.You can create scenes that capture the states you want certain entities to be. For example a scene can specify that light A should be turned on and light B should be bright red.
+# Example configuration.yaml entry @@ -138,6 +136,24 @@Scenes can be activated using the service
+ +scene.turn_on(there is no ‘scene.turn_off’ service).+ diff --git a/components/sensor.tcp/index.html b/components/sensor.tcp/index.html index 01fa0be23e..4e2ba6d2c2 100644 --- a/components/sensor.tcp/index.html +++ b/components/sensor.tcp/index.html @@ -179,7 +179,7 @@+++# Example automation +... +automation: + trigger: + platform: state + entity_id: device_tracker.sweetheart + from: 'not_home' + to: 'home' + action: + service: scene.turn_on + entity_id: scene.romantic +hddtemp
-The tool
+hddtempcollects the temperatur of your harddisks.The tool
hddtempcollects the temperature of your harddisks.$ hddtemp diff --git a/components/weblink/index.html b/components/weblink/index.html index aac1d9a450..3ab2aca78d 100644 --- a/components/weblink/index.html +++ b/components/weblink/index.html @@ -113,9 +113,9 @@
-The
+weblinkscomponent allows you to display links in the Home Assistant frontend.The
-weblinkcomponent allows you to display links in the Home Assistant frontend.To use this component in your installation, add the following to your
+configuration.yamlfile:To use this component in your installation, add something like the following to your
configuration.yamlfile:# Example configuration.yaml entry diff --git a/developers/architecture/index.html b/developers/architecture/index.html index 006df3901c..aa863618f3 100644 --- a/developers/architecture/index.html +++ b/developers/architecture/index.html @@ -136,7 +136,7 @@- The Event Bus facilitates the firing and listening of events. This is the beating heart of Home Assistant.
- The State Machine keeps track of the states of things. Fires a
state_changedevent when a state has been changed.- The Service Registry listens on the event bus for
-call_serviceevents and allows other code to register services.- The Timer will send every 1 second a
+time_changedevent on the event bus.- The Timer will send a
time_changedevent every 1 second on the event bus.@@ -146,16 +146,18 @@ Overview of the Home Assistant core architecture
-Home Assistant can be extended by components. Each component is responsible for a specific domain within Home Assistant. Components can listen for- or trigger events, offer services and maintain states. Components are written in Python and can do all the goodness that Python has to offer. Out of the box, Home Assistant offers a bunch of built-in components.
+Home Assistant can be extended by components. Each component is responsible for a specific domain within Home Assistant. Components can listen for or trigger events, offer services and maintain states. Components are written in Python and can do all the goodness that Python has to offer. Out of the box, Home Assistant offers a bunch of built-in components.
-We can differentiate between two different types ofcomponents within Home Assistant.
+We can differentiate between two different types of components within Home Assistant.
Components that interact with an Internet of Things domain
-These components will track devices within a specific domain and exist of a core part and platform specific logic. These components make their information available via the State Machine and the Event Bus. The component will also register services in the Service Registry to expose control of the devices.
+These components will track devices within a specific domain and consist of a core part and platform-specific logic. These components make their information available via the State Machine and the Event Bus. The component will also register services in the Service Registry to expose control of the devices.
For example, one of the built-in components is the
+switchcomponent. This component is responsible for interaction with different types of switches.A platform provides support for a particular kind/brand of device. For example, a switch could use a WeMo or Orvibo platform, and a light component might interact with the Hue or LiFX platform.
+If you are planning to add support for a new platform, please check out the add new platform section.
Components that respond to events that happen within Home Assistant
@@ -201,7 +203,7 @@ Overview of the full Home Assistant architecture with a couple of loaded components and platforms. -Component’s platform logic uses 3rd party Python libraries to communicate with the devices. This is done so that we can leverage great device libraries that are out there in the Python community.
+The platform logic for components uses 3rd party Python libraries to communicate with the devices. This is done so that we can leverage great device libraries that are out there in the Python community.
Multiple connected instances
@@ -214,7 +216,7 @@ Overview of the Home Assistant architecture for multiple devices. -A slave instance can be started with the following code and has the same support for components as a master-instance.
+A slave instance can be started with the following code and has the same support for components as a master instance.
import homeassistant.remote as remote @@ -237,7 +239,7 @@ hass.block_till_stopped()-Because each slave maintains its own ServiceRegistry it is possible to have multiple slaves respond to one service call. +Because each slave maintains its own Service Registry it is possible to have multiple slaves respond to one service call.
diff --git a/developers/website/index.html b/developers/website/index.html index a76d1b64a2..e8171968c4 100644 --- a/developers/website/index.html +++ b/developers/website/index.html @@ -117,7 +117,7 @@The home of Home Assistant is https://home-assistant.io. This is the place where we provide documentation and additional details about Home Assistant for end users and developers.
-home-assistant.io is using Octopress. To get more details, please checkout the documentation. That means that creating a new page is simple. The pages are written in markdown, you don’t need to care about HTML or alike.
+home-assistant.io is using the Octopress framework for Jekyll. To get more details, please checkout the documentation. That means that creating a new page is simple. The pages are written in markdown, you don’t need to care about HTML or alike.
To work on the website the process is no different to working on Home Assistant itself.
@@ -132,7 +132,7 @@For a platform page it would be the fastest way to make a copy of an existing page and edit it. The component overview is generated automatically, so there is no need to add a link to that your page.
Code
-To take advantage of the build-in features of Octopress to display code snipplets, just use the default markdown syntax. Please use
+$and#if it’s a command and to differ from output.To take advantage of the built-in features of Octopress to display code snippets, just use the default markdown syntax. Please use
$and#if it’s a command and to differ from output.-Here goes the code... @@ -140,7 +140,7 @@If you want to display line numbers, add the following snipplets somewhere on your page.
+If you want to display line numbers, add the following snippet somewhere on your page.
@@ -167,7 +167,7 @@ -{::options coderay_line_numbers="table" /}Not everything (product, component, etc.) has a logo, to show something for internal parts of Home Assistant we are using the Material Design Icons.
+Not everything (product, component, etc.) has a logo. To show something for internal parts of Home Assistant we are using the Material Design Icons.
diff --git a/getting-started/configuration/index.html b/getting-started/configuration/index.html index c4f35de335..7657a84477 100644 --- a/getting-started/configuration/index.html +++ b/getting-started/configuration/index.html @@ -117,11 +117,12 @@Home Assistant will create a configuration folder when it is run for the first time. The location of the folder differs between operating systems: on OS X/Linux it’s
-~/.homeassistantand on Windows it’s%APPDATA%/.homeassistant. If you want to use a different folder for configuration, runhass --config path/to/config.Inside your configuration folder is the file
+configuration.yaml. This is the main file that contains which components will be loaded and what their configuration is. An example configuration file is located here.Inside your configuration folder is the file
configuration.yaml. This is the main file that contains which components will be loaded and what their configuration is.
+This file contains YAML code, which is explained briefly in the configuration troubleshooting page. An example configuration file is located here.When launched for the first time, Home Assistant will write a default configuration enabling the web interface and device discovery. It can take up to a minute for your devices to be discovered and show up in the interface.
-If you are running into trouble while configuring Home Assistant, have a look at the configuration troubleshoot page.
+If you run into trouble while configuring Home Assistant, have a look at the configuration troubleshooting page.
You will have to restart Home Assistant for changes in
configuration.yamlto take effect. @@ -154,7 +155,7 @@Password protecting the web interface
-The first thing you want to add is a password for the web interface. Use your favourite text editor to open the file
+/config/configuration.yamland add the following to the bottom:The first thing you want to add is a password for the web interface. Use your favourite text editor to open the file
/config/configuration.yamland add the following to thehttpsection:http: @@ -167,13 +168,13 @@Setting up your phone or tablet
-Home Assistant runs as a self hosted web application and contains support to be added to your homescreen. If you’re on Android you can follow the visual guide. For other devices, open Home Assistant on your mobile browser and tap on the add to homescreen option.
+Home Assistant runs as a self-hosted web application and contains support to be added to your home screen. If you’re on Android you can follow the visual guide. For other devices, open Home Assistant on your mobile browser and tap the add to home screen option.
Remote access
To make Home Assistant accessible while away from home, you will have to setup port forwarding from your router to port 8123 on the computer that is hosting Home Assistant. Instructions on how to do this can be found by searching
-<Router model> port forwarding instructions.Some internet service providers will only offer dynamic IPs. This can cause you to be unable to access Home Assistant while away. You can solve this by using a free Dynamic DNS service like DuckDNS.
+Some Internet service providers will only offer dynamic IPs. This can cause you to be unable to access Home Assistant while away. You can solve this by using a free Dynamic DNS service like DuckDNS.
Next step: Setting up devices »
diff --git a/getting-started/troubleshooting-configuration/index.html b/getting-started/troubleshooting-configuration/index.html index ffeab5eea4..c02da72285 100644 --- a/getting-started/troubleshooting-configuration/index.html +++ b/getting-started/troubleshooting-configuration/index.html @@ -115,36 +115,37 @@
-It can happen that you run into trouble while configuring Home Assistant. A component is not showing up or is acting weird. This page will discuss a few of the most common problems.
+It can happen that you run into trouble while configuring Home Assistant. Perhaps a component is not showing up or is acting strangely. This page will discuss a few of the most common problems.
Before we dive into common issues, make sure you know where your configuration directory is. Home Assistant will print out the configuration directory it is using when starting up.
-Whenever a component or configuration option results in a warning, it will be stored in
+home-assistant.log. This file is reset on start of Home Assistant.Whenever a component or configuration option results in a warning, it will be stored in
home-assistant.login the configuration directory. This file is reset on start of Home Assistant.YAML
-Home Assistant uses the YAML syntax for configuration. YAML can be confusing at start but it is really powerful in allowing you to express complex configurations.
+Home Assistant uses the YAML syntax for configuration. YAML can be confusing to start with but is really powerful in allowing you to express complex configurations.
-The basics of YAML are lists and lookup tables containing key-value pairs. Lists will have each item start with a
+-while lookup tables will have the formatkey: value. The last value for a key is used in case you specify a duplicate key.The basics of YAML are block collections and mappings containing key-value pairs. Collections will have each item start with a
-while mappings will have the formatkey: value. The last value for a key is used in case you specify a duplicate key.
+Note that the indentation is an important part of specifying relationships using YAML.--# A list +# A collection - hello - how - are - you -# Lookup table +# Lookup mapping beer: ice cold # <-- will be ignored because key specified twice beer: warm wine: room temperature water: cold -# Nesting tables +# Nesting mappings (note the indentation) device_tracker: platform: mqtt -# Nesting a list of tables in a table +# Nesting a collection of mappings in a mapping sensor: - platform: mqtt state_topic: sensor/topic @@ -154,11 +155,11 @@Indentation is used to specify which objects are nested under one anohter. Getting the right indentation can be tricky if you’re not using an editor with a fixed width font. Tabs are not allowed to be used for indentation. You can test your configuration using online YAML parser or YAML Lint.
+Indentation is used to specify which objects are nested under one another. Getting the right indentation can be tricky if you’re not using an editor with a fixed width font. Tabs are not allowed to be used for indentation.
- To learn more about the quirks of YAML, read YAML IDIOSYNCRASIES by SaltStack.
-- You can test your configuration using this online YAML parser.
+- You can test your configuration using this online YAML parser or YAML Lint.
My component does not show up
@@ -167,21 +168,21 @@Problems with the configuration
-+
configuration.yamldoes not allow multiple sections to have the same name. If you want a specific platform to be loaded twice, append a number/string to the name or use this style.
configuration.yamldoes not allow multiple sections to have the same name. If you want a specific platform to be loaded twice, append a number or string to the name or nest them using this style.-sensor: platform: forecast - [...] + ... sensor 2: platform: bitcoin - [...] + ...Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to
+home-assistant.log. You can have a look at the component page for instructions how to setup the components.Another common problem is that a required configuration setting is missing. If this is the case, the component will report this to
home-assistant.log. You can have a look at the component page for instructions on how to setup the components.If you find any errors or want to expand the documentation, please let us know.
@@ -189,7 +190,7 @@Almost all components have external dependencies to communicate with your devices and services. Sometimes Home Assistant is unable to install the necessary dependencies. If this is the case, it should show up in
-home-assistant.log.First step is trying to restart Home Assistant and see if the problem persists. If it does, please report it so we can investigate what is going on.
+The first step is trying to restart Home Assistant and see if the problem persists. If it does, look at the log to see what the error is. If you can’t figure it out, please report it so we can investigate what is going on.
Problems with components
@@ -210,7 +211,7 @@@@ -224,13 +225,13 @@ - platform: mqtt name: "Door Motion" state_topic: "door/motion" - [...] + ...- platform: hyperion host: 192.168.1.98 - [...] + ...-Whenever you report an issue, be aware that we are a group of volunteers that do not have access to every single device in the world nor unlimited time to fix every problem out there. +Whenever you report an issue, be aware that we are volunteers who do not have access to every single device in the world nor unlimited time to fix every problem out there.
diff --git a/getting-started/troubleshooting/index.html b/getting-started/troubleshooting/index.html index dfeed120f0..f9340751e9 100644 --- a/getting-started/troubleshooting/index.html +++ b/getting-started/troubleshooting/index.html @@ -115,12 +115,12 @@
-It can happen that you run into trouble while installing Home Assistant. This page is here to help you figure out the most common problems.
+It can happen that you run into trouble while installing Home Assistant. This page is here to help you solve the most common problems.
pip3: command not found
This utility should have been installed as part of the Python 3.4 installation. Check if Python 3.4 is installed by running
-python3 --version. If it is not installed, download it here.If you are able to successfully run
+python3 --versionbut notpip3, run the following command instead to install Home Assistant:If you are able to successfully run
python3 --versionbut notpip3, install Home Assistant by running the following command instead:$ python3 -m pip install homeassistant @@ -129,7 +129,7 @@No module named pip
-Pip should come bundled with the latest Python 3 but is ommitted by some distributions. If you are unable to run
+python3 -m pip --versionyou can installpipby downloading the installer and run it with Python 3:Pip should come bundled with the latest Python 3 but is omitted by some distributions. If you are unable to run
python3 -m pip --versionyou can installpipby downloading the installer and running it with Python 3:$ python3 get-pip.py @@ -178,7 +178,7 @@ $ iptables-save > /etc/network/iptables.rules # your rules may be saved elseRun the development version
-If you want to stay on top of the development of Home Assistant then you can upgrade to the
+devbranch. This can result in an unstable system, loss of data, etc, etc.If you want to stay on top of the development of Home Assistant then you can upgrade to the
devbranch. This can result in an unstable system, loss of data, etc. etc.$ pip3 install --upgrade git+git://github.com/balloob/home-assistant.git@dev diff --git a/sitemap.xml b/sitemap.xml index d6d2a7c706..419e330779 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1323,630 +1323,630 @@https://home-assistant.io/components/alarm_control_panel.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/alarm_control_panel.manual.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/alarm_control_panel.mqtt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/arduino.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/automation.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/browser.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/camera.foscam.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/camera.generic.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/configurator.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/conversation.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_sun_light_trigger.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.actiontec.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.aruba.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.asuswrt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.ddwrt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.locative.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.luci.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.mqtt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.netgear.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.nmap_scanner.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.owntracks.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.snmp.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.thomson.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.tomato.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.tplink.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/device_tracker.ubus.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/discovery.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/downloader.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/ecobee.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/group.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/history.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/ifttt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/ifttt.manything.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/introduction.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/isy994.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/keyboard.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.blinksticklight.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.hue.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.hyperion.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.limitlessled.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.rfxtrx.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.tellstick.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.vera.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/light.wink.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/lock.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/lock.wink.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/logbook.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.cast.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.denon.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.firetv.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.itunes.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.kodi.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.mpd.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.plex.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.sonos.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/media_player.squeezebox.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/modbus.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/mqtt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.file.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.instapush.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.nma.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.pushbullet.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.pushover.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.slack.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.smtp.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.syslog.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.telegram.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/notify.xmpp.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/rfxtrx.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/scene.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/script.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.arduino.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.arest.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.bitcoin.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.command_sensor.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.cpuspeed.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.dht.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.ecobee.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.efergy.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.forecast.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.glances.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.modbus.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.mqtt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.mysensors.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.openweathermap.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.rest.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.rfxtrx.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.rpi_gpio.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.sabnzbd.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.speedtest.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.swiss_public_transport.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.systemmonitor.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.tellstick.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.temper.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.time_date.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.transmission.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.vera.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.wink.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sensor.worldclock.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/shell_command.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/simple_alarm.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/sun.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.arduino.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.arest.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.command_switch.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.edimax.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.hikvision.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.modbus.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.mqtt.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.pulseaudio_loopback.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.rest.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.rfxtrx.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.rpi_gpio.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.tellstick.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.transmission.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.vera.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.wemo.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/switch.wink.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/tellstick.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/thermostat.ecobee.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/thermostat.heat_control.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/thermostat.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/thermostat.nest.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/thermostat.radiotherm.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/vera.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/verisure.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/wink.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/zone.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/components/zwave.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/demo/frontend.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/demo/index.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/add_new_platform.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/api.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/architecture.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/creating_components.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/credits.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/frontend.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/python_api.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/rest_api.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/developers/website.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/android.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/automation.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/autostart.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/configuration.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/devices.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/presence-detection.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/templating.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/troubleshooting-configuration.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/getting-started/troubleshooting.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00 https://home-assistant.io/static/mdi-demo.html -2016-03-27T16:52:26+00:00 +2016-03-28T03:55:48+00:00
