- 2016-01-29T13:42:31+00:00
+ 2016-01-30T09:10:02+00:00https://home-assistant.io/
@@ -13,6 +13,53 @@
Octopress
+
+
+
+ 2016-01-30T08:22:00+00:00
+ https://home-assistant.io/blog/2016/01/30/insteon-lifx-twitter-and-zigbee
+ Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
+
+
I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
+
+
This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.
+
+
+
+Example of the new views in the frontend. Learn more.
+
I hope that this post could give you some ideas about the usage Home Assistant and MQTT. If you are working on a cool project that includes Home Assistant, please let us now.
-]]>
-
-
-
-
-
- 2015-08-31T21:12:00+00:00
- https://home-assistant.io/blog/2015/08/31/version-7-revamped-ui-and-improved-distribution
- As Home Assistant is gaining more and more users we started to feel the pain from not having a proper release mechanism. We had no version numbering and required users to checkout the source using Git to get started. On top of that, as the number of devices that we support keeps raising, so did the number of dependencies that are used. That’s why we decided to change the way we roll. From now on:
-
-
-
Each release will have a version number, starting with version 0.7. This was chosen because it shows that we have been around for some time but are not considering ourselves to be fully stable.
-
Each release will be pushed to PyPi. This will be the only supported method of distribution.
-
Home Assistant is available after installation as a command-line utility hass.
-
The default configuration location has been moved from config in the current working directory to ~/.homeassistant (%APPDATA%/.homeassistant on Windows).
-
Requirements for components and platforms are no longer installed into the current Python environment (being virtual or not) but will be installed in <config-dir>/lib.
-
-
-
A huge shout out to Ryan Kraus for making this all possible. Please make sure you read the full blog post for details on how to migrate your existing setup.
-
-
And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face lift. We already looked pretty good but lacked proper form of organization for users with many devices. The new UI moves away from a card per entity and has cards per group and domain instead. The demo has been updated so give it a spin.
It If you want to have the configuration in a different location, for example /home/paulus/home-assistant-config, you will have to point Home Assistant at this configuration folder when launching:
MQTT Sensors and Switches
-@sfam has blessed us with two more MQTT platforms to extend our integration with MQTTT: sensor and switch. Both platforms require the MQTT component to be connected to a broker.
DHT temperature and humidty sensors
-@MakeMeASandwich has contributed support for DHT temperature and humidity sensors. It allows you to get the current temperature and humidity from a DHT11, DHT22, or AM2302 device.
diff --git a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
index 7e9547d397..d5feb46127 100644
--- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
+++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
@@ -257,6 +257,12 @@ This article will try to explain how they all relate.
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index 6243dd32e4..1122723185 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -233,6 +233,12 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index 5dd23f1c0b..b913d3e54a 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -209,6 +209,12 @@ The old logo, the new detailed logo and the new simple logo.
diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html
index 40d3ad58df..13ab80b48a 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -248,6 +248,12 @@ An initial version of voice control for Home Assistant has landed. The current i
diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html
index 7219b5d00a..d73f194059 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -285,6 +285,12 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index 69a3b6bb57..bbe2c5368b 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -323,6 +323,12 @@ Before diving into the newly supported devices and services, I want to highlight
diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html
index 68c28c8eec..0171880b39 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -376,6 +376,12 @@ This switch platform allows you to control your motion detection setting on your
diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
index a57a957d23..fc0ff78cd9 100644
--- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
+++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
@@ -328,6 +328,12 @@ Fabian has added support for Forecast.io to g
diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
index 0dd8cea3db..ad8b8a3d9c 100644
--- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
+++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
@@ -317,6 +317,12 @@ Support for Temper temperature sensors has been contributed by
+
diff --git a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
index 2c021f5ade..6cfb87a0f5 100644
--- a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
+++ b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
@@ -277,6 +277,12 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
index 39cdf97735..ed8da675a9 100644
--- a/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
+++ b/blog/2015/09/19/alarm-sonos-and-itunes-support/index.html
@@ -256,6 +256,12 @@ Automation has gotten a lot of love. It now supports conditions, multiple trigge
diff --git a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
index 2f0c58acbe..0cf6761efb 100644
--- a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
+++ b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
@@ -232,6 +232,12 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index 9b9c0c86a5..5d6257e5b9 100644
--- a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
+++ b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
@@ -243,6 +243,12 @@ This makes more sense as most people run Home Assistant as a daemon
Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
+
+
I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
+
+
This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.
+
+
+
+Example of the new views in the frontend. Learn more.
+
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index b8e8711402..9a42e45f76 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2016-01-29T13:42:31+00:00
+ 2016-01-30T09:10:02+00:00https://home-assistant.io/
@@ -13,6 +13,53 @@
Octopress
+
+
+
+ 2016-01-30T08:22:00+00:00
+ https://home-assistant.io/blog/2016/01/30/insteon-lifx-twitter-and-zigbee
+ Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
+
+
I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
+
+
This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.
+
+
+
+Example of the new views in the frontend. Learn more.
+
Re-install platform and component dependencies after a Home Assistant version upgrade (@balloob)
-]]>
-
-
-
-
-
- 2015-10-26T18:10:00+00:00
- https://home-assistant.io/blog/2015/10/26/firetv-and-radiotherm-now-supported
- After two weeks of hard work I’m proud to announce the release of Home Assistant v0.7.6. For this release the main focus was bugs, test coverage and documentation. And we exceeded expectations on all three fronts. Bugs have been squashed, test coverage increased to 85% and thanks to the hard work by @fabaff and myself the component section on the website has gotten a complete revamp.
-
-
As part of this release we did some cleanup which introduced backwards incompatible changes:
-
-
Heat Control thermostat no longer includes scheduling features.
-This feature has been removed completely. Use the automation component instead to control target temperature.
-
-
Config changed for calling a service from a script.
-execute_service: has been replaced with service:. See component page for example. The old method will continue working for some time.
-
-
Scenes can no longer be turned off.
-It is no longer possible to turn a scene off after it has been activated. The way it worked was unpredictable and causes a lot of confusion.
-
-
Downloader treats relative paths now relative to the config dir instead of the current working dir.
-This makes more sense as most people run Home Assistant as a daemon
Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
+
+
I would like to give a shout out to Greg Dowling (@pavoni) as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
+
+
This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See the demo to see this in action and read more in the group documentation how to get started.
+
+
+
+Example of the new views in the frontend. Learn more.
+
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members in our Gitter chat room and last week PyPI counted 5063 downloads.
-
-
The idea was to anonymously collect some details about the usage of the different parts of Home Assistant and a little bit about the environment its running in.
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members in our Gitter chat room and last week PyPI counted 5063 downloads.
+
+
The idea was to anonymously collect some details about the usage of the different parts of Home Assistant and a little bit about the environment its running in.
As Home Assistant is gaining more and more users we started to feel the pain from not having a proper release mechanism. We had no version numbering and required users to checkout the source using Git to get started. On top of that, as the number of devices that we support keeps raising, so did the number of dependencies that are used. That’s why we decided to change the way we roll. From now on:
-
-
-
Each release will have a version number, starting with version 0.7. This was chosen because it shows that we have been around for some time but are not considering ourselves to be fully stable.
-
Each release will be pushed to PyPi. This will be the only supported method of distribution.
-
Home Assistant is available after installation as a command-line utility hass.
-
The default configuration location has been moved from config in the current working directory to ~/.homeassistant (%APPDATA%/.homeassistant on Windows).
-
Requirements for components and platforms are no longer installed into the current Python environment (being virtual or not) but will be installed in <config-dir>/lib.
-
-
-
A huge shout out to Ryan Kraus for making this all possible. Please make sure you read the full blog post for details on how to migrate your existing setup.
-
-
And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face lift. We already looked pretty good but lacked proper form of organization for users with many devices. The new UI moves away from a card per entity and has cards per group and domain instead. The demo has been updated so give it a spin.
As Home Assistant is gaining more and more users we started to feel the pain from not having a proper release mechanism. We had no version numbering and required users to checkout the source using Git to get started. On top of that, as the number of devices that we support keeps raising, so did the number of dependencies that are used. That’s why we decided to change the way we roll. From now on:
+
+
+
Each release will have a version number, starting with version 0.7. This was chosen because it shows that we have been around for some time but are not considering ourselves to be fully stable.
+
Each release will be pushed to PyPi. This will be the only supported method of distribution.
+
Home Assistant is available after installation as a command-line utility hass.
+
The default configuration location has been moved from config in the current working directory to ~/.homeassistant (%APPDATA%/.homeassistant on Windows).
+
Requirements for components and platforms are no longer installed into the current Python environment (being virtual or not) but will be installed in <config-dir>/lib.
+
+
+
A huge shout out to Ryan Kraus for making this all possible. Please make sure you read the full blog post for details on how to migrate your existing setup.
+
+
And while Ryan was fixing distribution, I have been hard at work in giving Home Assistant a face lift. We already looked pretty good but lacked proper form of organization for users with many devices. The new UI moves away from a card per entity and has cards per group and domain instead. The demo has been updated so give it a spin.
It has only been a little over a week since Theodor introduced YAML support for Home Assistant but so much has already happened that it is time for a summary of recent changes. Before mentioning the highlights I want to thank andythigpen, jamespcole and theolind for numerous bug fixes, enhancements and new contributions. Thanks!
-
-
Monitor local resources.
-Theodor has contributed a new sensor platform to allow you to monitor disk usage, memory usage, CPU usage and running processes. This platform has superseded the process component which is now considered deprecated.
-There is now experimental support for connecting Z-Wave networks using a Z-Wave USB stick. Right now it only integrates Z-Wave sensors into Home Assistant. Our goal is to get this tested by more people before adding support for other Z-Wave devices.
-
-
The new component is built on top of python-openzwave. This package is currently not distributed on PyPi so we’ve added a script scripts/build_python_openzwave to install it on your machine. Alternatively you can use the Docker image which is ready to go.
-
-
The development was done using an AEON Z-Wave USB stick and an AEON Z-Wave MultiSensor.
-
-
-
# Example configuration.yaml entry
-zwave:
- usb_path: /dev/ttyUSB0
-
-
-
-
-
Voice control
-An initial version of voice control for Home Assistant has landed. The current implementation consists of two parts.
-
-
The first part is a component called conversation that exposes the service conversation/process. This service is capable of processing text and translating them into commands for devices. For now it will only support commands in the format of Turn <Friendly Name> <on/off>.
-
-
The second part is an upgrade to the frontend to use the speech-to-text in Chrome to allow users to speak commands. If you’re using Chrome, you can test this out in the demo.
-
-
-
# Example configuration.yaml entry
-conversation:
-
It has only been a little over a week since Theodor introduced YAML support for Home Assistant but so much has already happened that it is time for a summary of recent changes. Before mentioning the highlights I want to thank andythigpen, jamespcole and theolind for numerous bug fixes, enhancements and new contributions. Thanks!
+
+
Monitor local resources.
+Theodor has contributed a new sensor platform to allow you to monitor disk usage, memory usage, CPU usage and running processes. This platform has superseded the process component which is now considered deprecated.
+There is now experimental support for connecting Z-Wave networks using a Z-Wave USB stick. Right now it only integrates Z-Wave sensors into Home Assistant. Our goal is to get this tested by more people before adding support for other Z-Wave devices.
+
+
The new component is built on top of python-openzwave. This package is currently not distributed on PyPi so we’ve added a script scripts/build_python_openzwave to install it on your machine. Alternatively you can use the Docker image which is ready to go.
+
+
The development was done using an AEON Z-Wave USB stick and an AEON Z-Wave MultiSensor.
+
+
+
# Example configuration.yaml entry
+zwave:
+ usb_path: /dev/ttyUSB0
+
+
+
+
+
Voice control
+An initial version of voice control for Home Assistant has landed. The current implementation consists of two parts.
+
+
The first part is a component called conversation that exposes the service conversation/process. This service is capable of processing text and translating them into commands for devices. For now it will only support commands in the format of Turn <Friendly Name> <on/off>.
+
+
The second part is an upgrade to the frontend to use the speech-to-text in Chrome to allow users to speak commands. If you’re using Chrome, you can test this out in the demo.
+
+
+
# Example configuration.yaml entry
+conversation:
+
+
+
+
+
+
+
+
+
@@ -597,50 +684,11 @@ This article will try to explain how they all relate.
-
-
-
-
I finally took the time to setup a simple website to help people getting started with Home Assistant. The process was super smooth thanks to the great tools Jekyll and Octopress and the great services GitHub Pages and CloudFlare.
I finally took the time to setup a simple website to help people getting started with Home Assistant. The process was super smooth thanks to the great tools Jekyll and Octopress and the great services GitHub Pages and CloudFlare.
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/arduino/index.html b/components/arduino/index.html
index 5b7ac5e88d..efd0683f40 100644
--- a/components/arduino/index.html
+++ b/components/arduino/index.html
@@ -187,6 +187,9 @@ A word of caution: The Arduino boards are not storing states. This means that wi
Time can be triggered in many ways. The most common is to specify after and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. For example, by only setting minutes in the config to 5 it will trigger every hour when it is 5 minutes past whole. You cannot use after together with hour, minute or second.
+
Time can be triggered in many ways. The most common is to specify after and trigger at a specific point in time each day. Alternatively, you can also match if the hour, minute or second of the current time has a specific value. You can prefix the value with a / to match whenever the value is divisible by that number. You cannot use after together with hour, minute or second.
automation:
trigger:
platform: time
- # All following are optional.
+ # Matches every hour at 5 minutes past whole
+ minutes: 5
+ seconds: 0
+
+automation 2:
+ trigger:
+ platform: time# When 'after' is used, you cannot also match on hour, minute, seconds.# Military time format.
- # after: '15:32:00'
- hours: 0
- minutes: 5
+ after: '15:32:00'
+
+automation 3:
+ trigger:
+ platform: time
+ # You can also match on interval. This will match every 5 minutes
+ minutes: '/5'seconds: 0
-
The above example will trigger every hour on the 5 (2:05, 3:05, 4:05, etc).
-
Zone trigger
Zone triggers can trigger when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. Currently this is limited to the OwnTracks platform.
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 919fc401c3..7da9c78384 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -178,14 +178,20 @@ This sensor is not suitable for fast state changes because there is a high possi
monitored_conditions array (Required): States to monitor.
+
+
+
You must have the Nest component configured to use this sensor.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/binary_sensor.rest/index.html b/components/binary_sensor.rest/index.html
index 964c6026f1..80ba26eed4 100644
--- a/components/binary_sensor.rest/index.html
+++ b/components/binary_sensor.rest/index.html
@@ -186,14 +186,20 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/binary_sensor.rpi_gpio/index.html b/components/binary_sensor.rpi_gpio/index.html
index d3f4f3557f..70f6966c24 100644
--- a/components/binary_sensor.rpi_gpio/index.html
+++ b/components/binary_sensor.rpi_gpio/index.html
@@ -211,9 +211,15 @@ To avoid having to run Home Assistant as root when using this component, run a R
A ZigBee binary sensor in this context is a device connected to one of the digital input pins on a ZigBee module. The states reported by such a device are limited to ‘on’ or ‘off’. By default, a binary sensor is considered ‘on’ when the ZigBee device’s digital input pin is held ‘high’ and considered ‘off’ when it is held ‘low’. This behaviour can be inverted by setting the on_state configuration variable to low.
+
+
To configure a digital input as a binary sensor, use the following variables:
+
+
+
name (Required): The name you’d like to give the binary sensor in Home Assistant.
+
platform (Required): Set to zigbee.
+
pin (Required): The number identifying which pin to use.
+
address: The long 64bit address of the remote ZigBee device whose digital input pin you’d like to sample. Do not include this variable if you want to sample the local ZigBee device’s pins.
+
on_state: Either high (default) or low, depicting whether the binary sensor is considered ‘on’ when the pin is ‘high’ or ‘low’.
This platform offers presence detection by looking at connected devices to a ASUSWRT based router.
+
The asuswrt platform offers presence detection by looking at connected devices to a ASUSWRT based router.
This device tracker needs telnet to be enabled on the router.
diff --git a/components/device_tracker.owntracks/index.html b/components/device_tracker.owntracks/index.html
index 9a176c9355..acf89b98d0 100644
--- a/components/device_tracker.owntracks/index.html
+++ b/components/device_tracker.owntracks/index.html
@@ -123,8 +123,40 @@
There is no further configuration needed for tracking Owntracks devices.
+
Using Owntracks with other device trackers
Owntracks can also be used with other device trackers, such as Nmap or Netgear. To do this, fill in the mac field to the Owntracks entry in known_devices.yaml with the MAC address of the device you want to track. This way the state of the device will be determined by the source that reported last.
+
Using Owntracks regions
+
Owntracks can track regions, and send region entry and exit information to Home Assistant(HA). You set up a region in the Owntracks app which you should name the same as your HA Zone, and then make sure to turn on the share option for the region in the owntracks app. Please see the owntracks documentation
+
+
Home Assistant will use the enter and leave messages to set your zone location. Your location will be set to the center of zone when you enter. Location updates from OwnTracks will be ignored while you are inside a zone.
+
+
When you exit a zone, Home Assistant will start using location updates to track you again. To make sure that Home Assistant correctly exits a zone (which it calculates based on your GPS co-ordinates), you may want to set your Zone radius in HA to be slightly smaller that the Owntracks region radius.
+
+
Using Owntracks regions - forcing Owntracks to update using iBeacons
+
When run in the usual significant changes mode (which is kind to your phone battery), Owntracks sometimes doesn’t update your location as quickly as you’d like when you arrive at a zone. This can be annoying if you want to trigger an automation when you get home. You can improve the situation using iBeacons.
+
+
iBeacons are simple bluetooth devices that send out an “I’m here” message. They are supported by IOS and some Android devices. Owntracks explain more here
+
+
When you enter an iBeacon region, Owntracks will send a region enter message to HA as described above. So if you want to have an event triggered when you arrive home, you can put an iBeacon outside your front door. If you set up an OwnTracks iBeacon region called home then getting close to the beacon will trigger an update to HA that will set your zone to be home.
+
+
When you exit an iBeacon region HA will switch back to using GPS to determine your location. Depending on the size of your zone, and the accuracy of your GPS location this may change your HA zone.
+
+
Sometimes Owntracks will lose connection with an iBeacon for a few seconds. If you name your beacon starting with - Owntracks will wait longer before deciding it has exited the beacon zone. HA will ignore the - when it matches the Owntracks region with Zones. So if you call your Owntracks region -home then HA will recognise it as home, but you will have a more stable iBeacon connection.
+
+
Using Owntracks iBeacons to track devices
+
iBeacons don’t need to be stationary. You could put one on your key ring, or in your car.
+
+
When your phone sees a mobile iBeacon that it knows about, it will tell HA the location of that iBeacon. If your phone moves while you are connected to the iBeacon, HA will update the location of the iBeacon. But when your phone loses the connection, HA will stop updating the iBeacon location.
+
+
To use mobile iBeacons with HA, you just set up a region that doesn’t match your Zone names. If HA sees an entry event for a iBeacon region that doesn’t match a Zone name (say keys) - it will start tracking it, calling the device device_tracker.beacon_keys).
+
+
This allows you to write zone automations for devices that can’t track themselves (for example alert me if I leave the house and my keys are still at home). Another example would be open the gates if my car arrives home.
+
+
Using mobile and fixed iBeacons together
+
You can use iBeacons of both types together, so if you have a Zone drive with an iBeacon region called -drive and you arrive home with a mobile iBeacon called -car, then device_tracker.beacon_car will be set to a state of drive.
Groups allow the user to combine multiple entities into one.
+
Groups allow the user to combine multiple entities into one. A group can be promoted to a view by setting the view option to yes. This will make the group available as a new tab in the frontend.
Check the Set State page from the Developer Tools and browse the Current entities: listing for all available entities.
icon (Optional): An optional icon to show in the Frontend.
+
view (Optional): If yes then the entry will be shown as a view.
+
entities array or comma delimited string (Required): List of entites to group.
+
+
+
+
+Example of groups shown as views in the frontend.
+
+
If all entities are switches or lights they can be controlled as one with a switch at the top of the card. Grouped states should share the same type of states (ON/OFF or HOME/NOT_HOME).
diff --git a/components/index.html b/components/index.html
index 8f4f549be0..3f6cef5c9b 100644
--- a/components/index.html
+++ b/components/index.html
@@ -391,7 +391,7 @@ Support for these components is provided by the Home Assistant community.
-
Command binary sensor
+
Command line binary sensor
Binary Sensor
@@ -699,6 +699,18 @@ Support for these components is provided by the Home Assistant community.
+
+
username (Required): The username that used to access the Insteon interface.
+
password (Required): The password that used to access the Insteon interface.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/isy994/index.html b/components/isy994/index.html
index 602455df48..359689d518 100644
--- a/components/isy994/index.html
+++ b/components/isy994/index.html
@@ -213,6 +213,9 @@ The ISY994 controller is manufactured by MySensors
+
A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered ‘on’ when the ZigBee device’s digital output is held ‘high’ and considered ‘off’ when it is held ‘low’. This behaviour can be inverted by setting the on_state configuration variable to low.
+
+
To configure a digital output pin as a light, use the following variables:
+
+
+
name (Required): The name you’d like to give the light in Home Assistant.
+
platform (Required): Set to zigbee.
+
pin (Required): The number identifying which pin to use.
+
address: The long 64bit address of the remote ZigBee device whose digital output pin you’d like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
+
on_state: Either high (default) or low, depicting whether the digital output pin is pulled high or low when the light is turned on.
diff --git a/components/mqtt/index.html b/components/mqtt/index.html
index 8ca8000753..a7062f1ff1 100644
--- a/components/mqtt/index.html
+++ b/components/mqtt/index.html
@@ -355,6 +355,9 @@ Home Assistant will automatically load the correct certificate if you connect to
The MySensors project combines Arduino boards with NRF24L01 radio boards to build sensor networks. The component will automatically add all available switches and sensors to Home Assistant.
+
Configuration
+
Integrate your Serial MySensors Gateway by adding the following to your configuration.yaml file:
@@ -130,10 +132,10 @@
port (Required): The port where your board is connected to your Home Assistant host.
-
debug (Optional): Enable or disable verbose debug logging.
-
persistence (Optional): Enable or disable local persistence of sensor information. If this is disabled, then each sensor will need to send presentation messages after Home Assistant starts.
+
debug (Optional): Enable or disable verbose debug logging. Default is false.
+
persistence (Optional): Enable or disable local persistence of sensor information. If this is disabled, then each sensor will need to send presentation messages after Home Assistant starts. Default is true.
persistence_file (Optional): Path to a file to save sensor information. The file extension determines the file type. Currently supported file types are ‘pickle’ and ‘json’.
-
version (Optional): Specifies the MySensors protocol version to use (ex. 1.4, 1.5).
+
version (Optional): Specifies the MySensors protocol version to use. Supports 1.4 and 1.5. Default is 1.4.
If you are using an original Arduino the port will be named ttyACM*. The exact number can be determined with the command shown below.
@@ -144,6 +146,29 @@
+
Presentation
+
+
Present a MySensors sensor or actuator, by following these steps:
+
+
+
Connect your gateway to your computer.
+
Configure the MySensors component in configuration.yaml.
+
Start hass.
+
Wait for “gateway started” in the log output.
+
Write and upload your MySensors sketch to the sensor. Make sure you:
+
+
Either use a manual node id, or AUTO for requesting a node id from the controller, in gw.begin().
+
Send sketch name.
+
Present the sensor’s S_TYPE.
+
Send at least one initial value per V_TYPE.
+
+
+
Start the sensor.
+
+
+
Visit the library api of MySensors for more information.
The Nest component is the main component to integrate all Nest related platforms. Besides this component you will have to setup your thermostat and any connected sensors separately.
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index 57f9b13b49..f7cc25930a 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -168,6 +168,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
username (Required): Enter your the Google email address you have signed up for Google Voice with. Go to https://www.google.com/voice to setup your Google Voice account.
+
password (Required): Enter the password associated with the above email. Go to https://www.pushbullet.com/ to retrieve your API key.
+
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
+
+
Usage
+
+
Google Voice is a notify platform and thus can be controlled by calling the notify service as described here. It will send a notification to all devices listed in the notification target.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/notify.instapush/index.html b/components/notify.instapush/index.html
index 42438adc1b..b8408e25bb 100644
--- a/components/notify.instapush/index.html
+++ b/components/notify.instapush/index.html
@@ -180,6 +180,9 @@
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
-
Usage
+
Usage
-
PushBullet is a notify platform and thus can be controlled by calling the notify service as described here. It will send a notification to all devices registered in the PushBullet account. An optional target parameter can be given to PushBullet to specify specific account’s devices, contacts or channels.
+
PushBullet is a notify platform and thus can be controlled by calling the notify service as described here. It will send a notification to all devices registered in the PushBullet account. An optional target parameter can be given to PushBullet to specify specific account’s devices, contacts or channels.
@@ -166,7 +165,7 @@
If using targets, your own account’s email address functions as ‘send to all devices’. All targets are verified (if exists) before sending, except email.
The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.
+
The smtp platform allows you to deliver notifications from Home Assistant to an e-mail recipient.
To enable notification by e-mail in your installation, add the following to your configuration.yaml file:
@@ -131,13 +131,13 @@
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
-
server (Required): SMTP server which is used to end the notifications. For Google Mail, eg. smtp.gmail.com. Keep in mind that Google has some extra layers of protection which need special attention (Hint: ‘Less secure apps’).
-
port (Required): The port that the SMTP server is using, eg. 587 for Google Mail and STARTTLS or 465/993 depending on your SMTP servers.
-
sender (Required): E-Mail address of the sender.
-
username (Required): Username for the SMTP account.
-
password (Required):Password for the SMTP server that belongs to the given username. If the password contains a colon it need to be wrapped in apostrophes.
+
server (Optional): SMTP server which is used to end the notifications. For Google Mail, eg. smtp.gmail.com. Keep in mind that Google has some extra layers of protection which need special attention (Hint: ‘Less secure apps’). Defaults to localhost.
+
port (Optional): The port that the SMTP server is using, eg. 587 for Google Mail and STARTTLS or 465/993 depending on your SMTP servers. Defaults to 25.
+
sender (Optional): E-mail address of the sender.
+
username (Optional): Username for the SMTP account.
+
password (Optional):Password for the SMTP server that belongs to the given username. If the password contains a colon it need to be wrapped in apostrophes.
recipient (Required): Recipient of the notification.
-
starttls (Optional): Enables STARTTLS, eg. 1 or 0.
+
starttls (Optional): Enables STARTTLS, eg. 1 or 0. Defaults to 0.
This platform is fragile and not able to catch all exceptions in a smart way because of the large number of possible configuration combinations.
@@ -179,6 +179,9 @@ which need special attention. By default, the usage by external applications, es
The telegram platform uses Telegram to delivery notifications from Home Assistant to your Android device, your Windows phone, or your iOS device.
+
The telegram platform uses Telegram to delivery notifications from Home Assistant to your Android device, your Windows phone, or your iOS device.
-
The requirement are:
+
The requirements are:
You need a Telegram bot. Please follow those instructions to create one and get the token for your bot. Keep in mind that bots are not allowed to contact users. You need to make the first contact with your user. Meaning that you need to send a message to the bot from your user.
The twitter platform uses Twitter to delivery notifications from Home Assistant.
+
+
Go to Twitter Apps and create an application. Visit “Keys and Access Tokens” of the application to get the details (“Consumer Key”, “Consumer Secret”, and “Access Token Secret” which needs to be generated).
+
+
To add Twitter to your installation, add the following to your configuration.yaml file:
name (Optional): Setting the optional parameter name allows multiple notifiers to be created. The default value is notify. The notifier will bind to the service notify.NOTIFIER_NAME.
+
consumer_key (Required): Your “Consumer Key” (API Key) for the application.
+
consumer_secret (Required): Your “Consumer Secret” (API Secret) for the application.
+
access_token_secret (Required): Your “Access Token Secret” for the application.
diff --git a/components/sensor.dht/index.html b/components/sensor.dht/index.html
index 61638061ba..9123496795 100644
--- a/components/sensor.dht/index.html
+++ b/components/sensor.dht/index.html
@@ -175,6 +175,9 @@ As this requires access to the GPIO, you will need to run Home Assistant as root
diff --git a/components/sensor.efergy/index.html b/components/sensor.efergy/index.html
index 91676f63f1..c99375e219 100644
--- a/components/sensor.efergy/index.html
+++ b/components/sensor.efergy/index.html
@@ -192,9 +192,15 @@ negative number of minutes your timezone is ahead/behind UTC time.
diff --git a/components/sensor.glances/index.html b/components/sensor.glances/index.html
index 38309c09ef..3cdf1f8a63 100644
--- a/components/sensor.glances/index.html
+++ b/components/sensor.glances/index.html
@@ -233,9 +233,15 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/components/sensor.modbus/index.html b/components/sensor.modbus/index.html
index dd0de1d1f8..9152fe2af1 100644
--- a/components/sensor.modbus/index.html
+++ b/components/sensor.modbus/index.html
@@ -229,9 +229,15 @@ Each named register will create an integer sensor and each named bit will create
monitored_conditions array (Required): States to monitor.
+
+
+
You must have the Nest component configured to use this sensor.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.netatmo/index.html b/components/sensor.netatmo/index.html
index 856a1827df..37d6d43d30 100644
--- a/components/sensor.netatmo/index.html
+++ b/components/sensor.netatmo/index.html
@@ -234,9 +234,15 @@ The Home Assistant NetAtmo platform has only be tested with the classic indoor a
To enable One wire sensors in your installation, add the following to your configuration.yaml file:
+
+
+
# Example configuration.yaml entry
+sensor:
+ platform: onewire
+ names:
+ some_id: your name
+
+
+
+
+
Configuration variables:
+
+
+
names array (Optional): ID and friendly name of your sensors.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.rest/index.html b/components/sensor.rest/index.html
index edab6a493d..c3a781b62e 100644
--- a/components/sensor.rest/index.html
+++ b/components/sensor.rest/index.html
@@ -263,9 +263,15 @@ Make sure that the URL matches exactly your endpoint or resource.
The analog input pins on an XBee (non-Pro) will read 0V to 1.2V. This is translated by the xbee-helper library into a percentage. The maximum voltage your ZigBee device will read is configurable using the max_volts configuration variable.
+
+
To configure an analog input pin sensor, use the following variables:
+
+
+
name (Required): The name you’d like to give the sensor in Home Assistant.
+
platform (Required): Set to zigbee.
+
type (Required): Set to analog.
+
pin (Required): The number identifying which pin to sample.
+
address: The long 64bit address of the remote ZigBee device whose analog input pin you’d like to sample. Do not include this variable if you want to sample the local ZigBee device’s pins.
+
max_volts: The maximum voltage which the analog input pin is able to read. Default: 1.2
+
+
+
Example
+
+
+
sensor:
+ - name: My Analog Input
+ platform: zigbee
+ type: analog
+ pin: 0
+ address: 0013A2004233D138
+
The XBee Pro (and perhaps other third party modules) contains a thermometer device which can be read by using the TP AT command. To set this up as a temperature sensor device in Home Assistant use the following config variables:
+
+
+
name (Required): The name you’d like to give the temperature sensor in Home Assistant
+
platform (Required): Set to zigbee
+
type (Required): Set to temperature
+
address: The long 64bit address of the remote ZigBee device whose temperature sensor you’d like to sample. Do not include this variable if you want to sample the local ZigBee device’s temperature.
+
+
+
Example
+
+
+
sensor:
+ - name: Living Room Temperature
+ platform: zigbee
+ type: temperature
+ address: 0013A20050E752C5
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.zwave/index.html b/components/sensor.zwave/index.html
index a72ff3d23f..efbc4f97c2 100644
--- a/components/sensor.zwave/index.html
+++ b/components/sensor.zwave/index.html
@@ -174,9 +174,15 @@
diff --git a/components/switch.command_switch/index.html b/components/switch.command_switch/index.html
index 33007be357..c7a07e8d18 100644
--- a/components/switch.command_switch/index.html
+++ b/components/switch.command_switch/index.html
@@ -266,6 +266,9 @@ This switch will shutdown your host immediately, there will be no confirmation.
diff --git a/components/switch.modbus/index.html b/components/switch.modbus/index.html
index a30a26ce1a..b6361780fe 100644
--- a/components/switch.modbus/index.html
+++ b/components/switch.modbus/index.html
@@ -244,6 +244,9 @@ Each named bit will create a switch.
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index 424a16376e..a193b869d2 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -217,6 +217,9 @@ Make sure that the URL matches exactly your endpoint or resource.
diff --git a/components/switch.rpi_gpio/index.html b/components/switch.rpi_gpio/index.html
index 338b5b207b..470b8fcdb6 100644
--- a/components/switch.rpi_gpio/index.html
+++ b/components/switch.rpi_gpio/index.html
@@ -218,6 +218,9 @@ If you are not running Raspbian Jessie, you will need to run Home Assistant as r
A ZigBee switch in this context is a device connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a switch is considered ‘on’ when the ZigBee device’s digital output is held ‘high’ and considered ‘off’ when it is held ‘low’. This behaviour can be inverted by setting the on_state configuration variable to low.
+
+
To configure a digital output pin as a switch, use the following variables:
+
+
+
name (Required): The name you’d like to give the switch in Home Assistant.
+
platform (Required): Set to zigbee.
+
pin (Required): The number identifying which pin to use.
+
address: The long 64bit address of the remote ZigBee device whose digital output pin you’d like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
+
on_state: Either high (default) or low, depicting whether the digital output pin is pulled high or low when the switch is turned on.
Telldus Live is a cloud platform that connects to your Tellstick connected gear at home.
+
The tellduslive component let you connect to Telldus Live. It’s cloud platform that connects to your Tellstick connected gear at home.
-
To get started using Telldus Live, you will have to obtain developer keys from here.
+
To get started using Telldus Live, you will have to obtain developer keys from (https://api.telldus.com/keys/index)[developer-keys].
+
+
To integrate your Telldus Live with Home Assistant, add the following section to your configuration.yaml file:
# Example configuration.yaml entrytellduslive:
- public_key: XX
- private_key: XX
- token: XX
- token_secret: XX
+ public_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+ private_key: ABCDEFGHJKLMNOPQRSTUVXYZ
+ token: ABCDEFGHJKLMNOPQRSTUVXYZ
+ token_secret: ABCDEFGHJKLMNOPQRSTUVXYZ
+
Configuration variables:
+
+
+
public_key (Required): The public key for the Telldus Live service.
+
private_key (Required): The private key for the Telldus Live service.
+
token (Required): The token for the Telldus Live service.
+
token_secret (Required): The token secret for the Telldus Live service.
+
+
+
Tellstick Net devices can be auto discovered using this method.
+
+
It might be possible to communicate with the Tellstick Net device directly, bypassing the Tellstick Live service. This however is poorly documented and yet not fully supported.
+
+
+API requests to certain methods are limited to one request every 10 minutes.
+
diff --git a/components/wink/index.html b/components/wink/index.html
index 7f49cfc43c..c97592dd20 100644
--- a/components/wink/index.html
+++ b/components/wink/index.html
@@ -181,6 +181,9 @@ The Wink hub can only be accessed via the cloud. This means it requires an activ
ZigBee integration for Home Assistant allows you to utilise modules such as the XBee as wireless General Purpose Input/Output (GPIO) devices. The component requires a local ZigBee device to be connected over a serial port. Through this it will send and receive commands to and from other devices on the ZigBee mesh network.
+
+
There is currently support for the following device types within Home Assistant:
+ Restart Home Assistant if Wemo Switch Is Not Detected
+
+
+
+
+
+
Restart Home Assistant
+
+
This configuration example is restarting Home Assistant if a WeMo switch is not detected. An additional MQTT switch is present for stopping Home Assistant and can be triggered by IFTTT. The running batch script will automatically restart Home Assistant if the process isn’t found anymore.
The else part is used to have the sensor keep it’s last state if the newest iCloud update doesn’t have any battery state in it (which happens sometimes). Otherwise the sensor will be blank.
+
+
While running the Owntracks device tracker you can retrieve the battery level with a MQTT sensor.