Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
+
+
Rock on.
+
+
+
+
+
Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
Automation: support for old deprecated config has been removed
+
+
+
Tellstick configuration has changed
+
+
+
+
+
tellstick:
+ signal_repetitions: X
+
+
+
+
+
+
Vera configuration has changed
+
+
+
+
vera:
+ vera_controller_url: http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
+
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
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 0b7fe3e62e..4a27a6ba74 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
@@ -258,6 +258,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 8bd74d5814..d83a751e68 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -234,6 +234,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 bde0b10ad0..1f29b45b8f 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -210,6 +210,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 e59680edec..f6881e9b48 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -249,6 +249,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 bbc8920645..bd1d4ddc81 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -286,6 +286,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 be0e201a03..5582dbe7a0 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -324,6 +324,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 7be771e1ca..fccf7021a8 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -377,6 +377,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 fcf2fce4e8..cde4566927 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
@@ -329,6 +329,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 b1b22bbbd7..9c9aed2f9a 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
@@ -318,6 +318,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -341,12 +347,6 @@ Support for Temper temperature sensors has been contributed by
- 0.13: Speedtest.net, Bloomsky, Splunk and Garage Doors
-
-
-
diff --git a/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html b/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
index 7dad57f212..f886d77a26 100644
--- a/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
+++ b/blog/2015/08/17/verisure-and-modern-tp-link-router-support/index.html
@@ -228,6 +228,12 @@
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 32ba2dd08e..40f6454225 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
@@ -278,6 +278,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 c1174352a8..a3487d49da 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
@@ -257,6 +257,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 21f7d8e323..5903b87cf9 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
@@ -233,6 +233,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 5c24449033..4e8cbb2840 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
@@ -244,6 +244,12 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index 6eec3b9f06..ea1ec85f60 100644
--- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
+++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
@@ -242,6 +242,12 @@ Example of the new views in the frontend. Learn mor
diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html
index 9d8aad2034..f52908e8e6 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -253,6 +253,12 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
+
+
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
+
+
Rock on.
+
+
+
+
+
Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
Automation: support for old deprecated config has been removed
+
+
+
Tellstick configuration has changed
+
+
+
+
+
tellstick:
+ signal_repetitions: X
+
+
+
+
+
+
Vera configuration has changed
+
+
+
+
vera:
+ vera_controller_url: http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
+
+
+
+
+
+
+
+
Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 23a8acf676..bf86529aeb 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -122,6 +122,38 @@
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 77343ba20f..b0218d0053 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
- 2016-03-26T07:13:31+00:00
+ 2016-03-26T08:09:04+00:00https://home-assistant.io/
@@ -13,6 +13,73 @@
Octopress
+
+
+
+ 2016-03-26T07:10:00+00:00
+ https://home-assistant.io/blog/2016/03/26/embedded-mqtt-broker-uber-yamaha-growl
+ Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
+
+
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
+
+
Rock on.
+
+
+
+
+
Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
Automation: support for old deprecated config has been removed
+
+
+
Tellstick configuration has changed
+
+
+
+
+
tellstick:
+ signal_repetitions: X
+
+
+
+
+
+
Vera configuration has changed
+
+
+
+
vera:
+ vera_controller_url: http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
+
+
+
+]]>
+
+
@@ -218,49 +285,6 @@ Example of the new views in the frontend. Nest component.
Entity IDs for Z-Wave devices are now generated in a deterministic way causing all IDs to change starting this release. This is a one time change.
-]]>
-
-
-
-
-
- 2016-01-17T23:20:00+00:00
- https://home-assistant.io/blog/2016/01/17/extended-support-for-diy-solutions
- First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
-
-
Party people, 0.16 is here! The big thing with this release is that we have completely removed the barrier to get started by MQTT by being able to launch an embedded MQTT server: hbMQTT. Just add mqtt: to your config and a broker is launched and connected with Home Assistant. See the documentation for more info.
+
+
Further in this release a bunch of cool new stuff, bug fixes and rewrites for the Vera and Tellstick component (see breaking changes section at bottom for this!).
+
+
Rock on.
+
+
+
+
+
Device Tracker - OwnTracks: Allow entry into passive zones using iBeacons (@pavoni)
Automation: support for old deprecated config has been removed
+
+
+
Tellstick configuration has changed
+
+
+
+
+
tellstick:
+ signal_repetitions: X
+
+
+
+
+
+
Vera configuration has changed
+
+
+
+
vera:
+ vera_controller_url: http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
+
+
+
+
+
+
+
+
+
@@ -792,81 +891,6 @@ Example of the new views in the frontend. Learn mor
Read on →
-
First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
First release of 2016 and we are on 🔥! The main repository has passed 2500 ⭐ on GitHub (2596 ⭐ as of now). This release also has a record number of 20 contributors all working on improving and extending Home Assistant. With the continued growth, I am very excited to see what 2016 will bring us 🤘.
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.
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.
A minor bug fix release to fix some issues that have come up since the last release. Please upgrade as soon as possible by running git pull from the Home Assistant directory.
-
-
This release is a major milestone in our test coverage as we’ve crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.
-
-
As we didn’t want to just push out bug fixes, this release includes a few additions:
-
-
-
Support for modern TP-Link routers like the ArcherC9 line has been contributed by @chrisvis.
-
Improved support for MQTT topic subscriptions has been contributed by @qrtn
-
-
-
Verisure Support
- Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
A minor bug fix release to fix some issues that have come up since the last release. Please upgrade as soon as possible by running git pull from the Home Assistant directory.
+
+
This release is a major milestone in our test coverage as we’ve crossed into the 80s! It has to be noted that this covers mainly the core and automation components. Platforms that communicate with IoT devices have been excluded.
+
+
As we didn’t want to just push out bug fixes, this release includes a few additions:
+
+
+
Support for modern TP-Link routers like the ArcherC9 line has been contributed by @chrisvis.
+
Improved support for MQTT topic subscriptions has been contributed by @qrtn
+
+
+
Verisure Support
+ Home Assistant support to integrate your Verisure alarms, hygrometers, sensors and thermometers has been contributed by @persandstrom.
Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
-
-
The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
Home Assistant is now using YAML for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
+
+
The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
diff --git a/components/binary_sensor.rpi_gpio/index.html b/components/binary_sensor.rpi_gpio/index.html
index f9cadd7803..280a22b284 100644
--- a/components/binary_sensor.rpi_gpio/index.html
+++ b/components/binary_sensor.rpi_gpio/index.html
@@ -289,6 +289,9 @@ To avoid having to run Home Assistant as root when using this component, run a R
diff --git a/components/ifttt/index.html b/components/ifttt/index.html
index d4c2a1bc2e..ca9234fc8e 100644
--- a/components/ifttt/index.html
+++ b/components/ifttt/index.html
@@ -233,6 +233,9 @@ You need to setup a unique trigger for each event you sent to IFTTT.
diff --git a/components/index.html b/components/index.html
index fef7500b31..a25652bbfa 100644
--- a/components/index.html
+++ b/components/index.html
@@ -932,6 +932,20 @@ Support for these components is provided by the Home Assistant community.
+
+
diff --git a/components/media_player.firetv/index.html b/components/media_player.firetv/index.html
index 46fe3b0a46..8d1633ecf2 100644
--- a/components/media_player.firetv/index.html
+++ b/components/media_player.firetv/index.html
@@ -224,6 +224,9 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
diff --git a/components/media_player.samsungtv/index.html b/components/media_player.samsungtv/index.html
index e6ef3b3bd9..39854b0d6f 100644
--- a/components/media_player.samsungtv/index.html
+++ b/components/media_player.samsungtv/index.html
@@ -204,6 +204,9 @@ The two letters at the beginning of the model number represent the region, UE is
diff --git a/components/media_player.squeezebox/index.html b/components/media_player.squeezebox/index.html
index cd9b5121b6..2799a3cc57 100644
--- a/components/media_player.squeezebox/index.html
+++ b/components/media_player.squeezebox/index.html
@@ -195,6 +195,9 @@ This lets you control Squeezebox hardware like the Classic, Transporter, Duet, B
This will automatically search your network for Yamaha receivers. It will add a media player device for each one.
+
Currently the only controls that are available is Power On/Off, Mute, and Volume control. Other functions such as source select are in progress of being developed.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/media_player/index.html b/components/media_player/index.html
index af40a473ba..27bae56cb1 100644
--- a/components/media_player/index.html
+++ b/components/media_player/index.html
@@ -118,7 +118,7 @@
Services
Media control services
-
Available services: turn_off, volume_up, volume_down, media_play_pause, media_play, media_pause, media_next_track
The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are three options, each with various degrees of ease of setup and privacy.
+
The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are four options, each with various degrees of ease of setup and privacy.
+
+
Use the embedded broker
+
+
Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the HBMQTT broker is started and Home Asssistant connects to it. Default settings for the embedded broker:
+
+
+
+
+
Setting
+
Value
+
+
+
+
+
Host
+
localhost
+
+
+
Port
+
1883
+
+
+
Version
+
3.1
+
+
+
User
+
homeassistant
+
+
+
Password
+
Your API password
+
+
+
Websocket port
+
8080
+
+
+
+
+
If you want to customize the settings of the embedded broker, use embedded: and the values shown in the HBMQTT Broker configuration.
+
+
+
# Example configuration.yaml entry
+mqtt:
+ embedded:
+ # Your HBMQTT config here. Example at:
+ # http://hbmqtt.readthedocs.org/en/latest/references/broker.html#broker-configuration
+
+
+
Run your own
@@ -263,7 +314,7 @@ Home Assistant will automatically load the correct certificate if you connect to
Testing your setup
-
For debugging purposes mosquitto is shipping commandline tools to send and recieve MQTT messages. For sending test messages to a broker running on localhost:
+
The mosquitto broker package is shipping commandline tools to send and recieve MQTT messages. As an alternative have a look at hbmqtt_pub and hbmqtt_sub which are provied by HBMQTT. For sending test messages to a broker running on localhost check the example below:
$ mosquitto_pub -h 127.0.0.1 -t home-assistant/switch/1/on -m "Switch is ON"
@@ -271,6 +322,22 @@ Home Assistant will automatically load the correct certificate if you connect to
+
If you are using the embeeded MQTT broker, the command looks a little different because you need to add the MQTT protocol version.
+
+
+
$ mosquitto_pub -V mqttv311 -t hello -m world
+
+
+
+
+
or if you are using a API password.
+
+
+
$ mosquitto_pub -V mqttv311 -u homeassistant -P <your api password> -t "hello" -m world
+
+
+
+
Another way to send MQTT messages by hand is to use the “Developer Tools” in the Frontend. Choose “Call Service” and then mqtt/mqtt_send under “Available Services”. Enter something similar to the example below into the “Service Data” field.
@@ -298,6 +365,16 @@ Home Assistant will automatically load the correct certificate if you connect to
+
For the embeeded MQTT broker the command looks like the sample below.
+
+
+
$ mosquitto_sub -V mqttv311 -t # -v
+
+
+
+
+
Add the username homeassistant and your API password if needed.
+
Processing JSON
The MQTT switch and sensor platforms support processing JSON over MQTT messages and parse them using JSONPath. JSONPath allows you to specify where in the JSON the value resides that you want to use. The following examples will always return the value 100.
diff --git a/components/notify.free_mobile/index.html b/components/notify.free_mobile/index.html
index ed7f10235f..916f8d41ad 100644
--- a/components/notify.free_mobile/index.html
+++ b/components/notify.free_mobile/index.html
@@ -178,6 +178,9 @@ If you disable and re-enable the SMS API option, please be sure to update your t
GNTP is a specification for sending and receiving notifications between computers. The most well known server implementations are Growl for Mac and Growl for Windows.
+
+
To use GNTP notifications, add the following to your configuration.yaml file:
GNTP will attempt to connect to a local server running on port 23053 if no hostname is provided.
+
+
Configuration variables:
+
+
+
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.
+
app_name (Optional): The application name that will be displayed on every notification and will be registered with the server.
+
app_icon (Optional): The icon that will be displayed on every notification. You can provide a HTTP URL or a file:// URL. File URLs only work if Home Assistant and the GNTP server are running on the same machine. If no app_icon is set a local copy of the Home Assistant logo will be used. If you choose to use a HTTP URL please make the maximum image size 150 px by 150 px as Growl for Mac will sometimes timeout when registering.
+
hostname (Optional): The hostname or IP address of the GNTP server to contact.
+
password (Optional): The password to authenticate to the GNTP server with.
+
port (Optional): The port that the GNTP server runs on. The specification states that servers should not allow users to use any port other than 23053 but port is provided here just in case.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/notify.google_voice/index.html b/components/notify.google_voice/index.html
index 1e1bf634c1..4c355a6534 100644
--- a/components/notify.google_voice/index.html
+++ b/components/notify.google_voice/index.html
@@ -191,6 +191,9 @@
api_key (Required): Enter the API key for MessageBird. Go to https://www.messagebird.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.
+
sender (Optional): Setting the optional parameter sender. This will be the sender of the SMS. It may be either a telephone number (e.g. +4915112345678) or a text with a maximum length of 11 characters. Defaults to HA.
+
+
+
Usage
+
+
MessageBird is a notify platform and thus can be controlled by calling the notify service as described here. It will send a notification to the specified mobile phone number(s).
+
+
Example service payload
+
+
+
{
+ "message": "A message for many people",
+ "target": [ "+49123456789", "+43123456789" ]
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/notify.mqtt/index.html b/components/notify.mqtt/index.html
index f15abb22c4..8a7e98ef39 100644
--- a/components/notify.mqtt/index.html
+++ b/components/notify.mqtt/index.html
@@ -202,6 +202,9 @@
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index f8f14112fc..21ca42f85f 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -189,6 +189,9 @@ which need special attention. By default, the usage by external applications, es
The bitcoin platform displays various details about the Bitcoin network.
-
-
If you have an online wallet from Blockchain.info the sensor is capable to show your current balance.
-
-
You need to enable the API access for your online wallet to get the balance. To do that log in and move to ‘Account Setting’, choose ‘IP Restrictions’, and check ‘Enable Api Access’. You will get an email message from blockchain.info where you must authorize the API access.
+
The bitcoin sensor platform displays various details about the Bitcoin network.
To add the Bitcoin sensor to your installation, add a selection of the available display options to your configuration.yaml file:
diff --git a/components/sensor.efergy/index.html b/components/sensor.efergy/index.html
index 5e12be40b9..7612b4c305 100644
--- a/components/sensor.efergy/index.html
+++ b/components/sensor.efergy/index.html
@@ -274,6 +274,9 @@ 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 e1d1a14ebe..40a27347a3 100644
--- a/components/sensor.glances/index.html
+++ b/components/sensor.glances/index.html
@@ -318,6 +318,9 @@ Glances web server started on http://0.0.0.0:61208/
diff --git a/components/sensor.http/index.html b/components/sensor.http/index.html
index f4f6174808..4d55cb1339 100644
--- a/components/sensor.http/index.html
+++ b/components/sensor.http/index.html
@@ -302,6 +302,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/sensor.modbus/index.html b/components/sensor.modbus/index.html
index 5de244b365..4037db75a8 100644
--- a/components/sensor.modbus/index.html
+++ b/components/sensor.modbus/index.html
@@ -311,6 +311,9 @@ Each named register will create an integer sensor and each named bit will create
diff --git a/components/sensor.netatmo/index.html b/components/sensor.netatmo/index.html
index 2e286cc9f2..eeb76bea68 100644
--- a/components/sensor.netatmo/index.html
+++ b/components/sensor.netatmo/index.html
@@ -330,6 +330,9 @@ The Home Assistant NetAtmo platform has only be tested with the classic indoor,
diff --git a/components/sensor.rest/index.html b/components/sensor.rest/index.html
index 94894a4170..91c5e0d8ec 100644
--- a/components/sensor.rest/index.html
+++ b/components/sensor.rest/index.html
@@ -360,6 +360,9 @@ Make sure that the URL matches exactly your endpoint or resource.
The uber sensor will give you time and price estimates for all available Uber products at the given start_latitude and start_longitude.The ATTRIBUTES are used to provide extra information about products, such as estimated trip duration, distance and vehicle capacity. By default, 2 sensors will be created for each product at the given start location, one for pickup time and one for current price. The sensor is powered by the official Uber API.
+
+
You must create an application here to obtain a server_token.
+
+
To enable this sensor, add the following lines to your configuration.yaml file:
start_latitude (Required): The starting latitude for a trip.
+
start_longitude (Required): The starting longitude for a trip.
+
end_latitude (Optional): The ending latitude for a trip. While end_latitude is optional, it is strongly recommended to provide an end_latitude/end_longitude when possible as you will get more accurate price and time estimates.
+
end_longitude (Optional): The ending longitude for a trip. While end_longitude is optional, it is strongly recommended to provide an end_latitude/end_longitude when possible as you will get more accurate price and time estimates.
product_ids (Options): A list of Uber product UUIDs. If provided, sensors will only be created for the given product IDs. Please note that product IDs are region and some times even more specific geographies based. The easiest way to find a UUID is to click on a sensor in the Home Assistant frontend and look for “Product ID” in the attributes.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.vera/index.html b/components/sensor.vera/index.html
index ed3d26c019..e233911ec4 100644
--- a/components/sensor.vera/index.html
+++ b/components/sensor.vera/index.html
@@ -285,6 +285,9 @@
diff --git a/components/switch.hikvision/index.html b/components/switch.hikvision/index.html
index da4c7a0419..9ee50c4768 100644
--- a/components/switch.hikvision/index.html
+++ b/components/switch.hikvision/index.html
@@ -192,6 +192,9 @@ Currently works using default https port only.
diff --git a/components/switch.modbus/index.html b/components/switch.modbus/index.html
index b8e82195cb..c1f3cf0c88 100644
--- a/components/switch.modbus/index.html
+++ b/components/switch.modbus/index.html
@@ -230,6 +230,9 @@ Each named bit will create a switch.
diff --git a/components/switch.mqtt/index.html b/components/switch.mqtt/index.html
index 17eadecde5..95645fe8bc 100644
--- a/components/switch.mqtt/index.html
+++ b/components/switch.mqtt/index.html
@@ -240,6 +240,9 @@ Make sure that your topic match exact. some-topic/ and some-t
The goal behind this switch is to allow a very flexible whole home audio system based upon PulseAudio.
+
+
For example, for a system with a 7.1 surround sound card, and 3 instances of mpd running, it is possible to quickly route the output of any mpd instance to any of the 8 possible (4 stereo) channels on the sound card, by loading/unloading a loopback module. This loading/unloading functionality is provided by this component. When the switch is ‘on’, the loopback module is loaded. When the switch is ‘off’, the module is not loaded.
+
+
The benefit of this approach is that this audio routing can occur without modifying the design-time configuration of mpd or PulseAudio.
+
+
This component uses a TCP connection to control a local or remote PulseAudio server- so there are no local dependencies.
+
+
To enable this switch, add the following lines to your configuration.yaml file:
sink_name (Required): The name of the Pulseaudio sink that will recieve the audio.
+
source_name (Required): The name of the Pulseaudio source that will supply the audio.
+
name (Optional): Name of the switch.
+
host (Optional): The IP address or host name of the PulseAudio server. If not specified, 127.0.0.1 is used.
+
port (Optional): The port that Pulseaudio is listening on. Defaults to 4712.
+
buffer_size (Optional): How much data to load from Pulseaudio at once. Default is 1KB.
+
tcp_timeout (Optional): How long to wait for a response from Pulseaudio before giving up. Default is 3 seconds.
+
+
+
+This component relies on raw TCP commands to PulseAudio. In order for PulseAudio to accept commands with
+this component, module-cli-protocol must be loaded on the PulseAudio server.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/switch.rest/index.html b/components/switch.rest/index.html
index fa8b849957..15c262274d 100644
--- a/components/switch.rest/index.html
+++ b/components/switch.rest/index.html
@@ -206,6 +206,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 9460e98439..e3f399a773 100644
--- a/components/switch.rpi_gpio/index.html
+++ b/components/switch.rpi_gpio/index.html
@@ -204,6 +204,9 @@ If you are not running Raspbian Jessie, you will need to run Home Assistant as r
# Example configuration.yaml entry
-switch:
- platform: tellstick
-
-sensor:
- platform: tellstick
-
-# All dimmers will be picked up as lights.
-light:
- platform: tellstick
+tellstick:
+ signal_repetitions: X
vera:
+ vera_controller_url: http://192.168.1.161:3480/
+ # Optional to exclude devices - this is a list of vera device ids
+ exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
+ # Optional to import switches as lights - this is a list of vera device ids
+ lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
+
+
+
diff --git a/components/zwave/index.html b/components/zwave/index.html
index d28be8ed44..08b342836e 100644
--- a/components/zwave/index.html
+++ b/components/zwave/index.html
@@ -231,6 +231,37 @@ Depending on what’s plugged into your USB ports, the name found above may chan
The entity_id and scene_id of all triggered events can be seen in the console output.
+
Services
+
+
The Z-Wave component exposes two services to help maintain the network.
+
+
+
+
+
Service
+
Description
+
+
+
+
+
add_node
+
+
+
+
remove_node
+
+
+
+
heal_network
+
+
+
+
soft_reset
+
+
+
+
+
diff --git a/images/supported_brands/ethernet.png b/images/supported_brands/ethernet.png
new file mode 100644
index 0000000000000000000000000000000000000000..6f507b4ac946bf731f78e3401cb98aea3d34fbc0
GIT binary patch
literal 635
zcmeAS@N?(olHy`uVBq!ia0vp^2_VeD1|%QND7OGoY)RhkE(}8pX7+2iB`GtXjiOti+F{I+w+q;fl(t$F^KjxcWs9^9kzts9D
z(Z;D*`Ryg`3YO~Dsy3yjUD^B>IM`x+c4@TEy#C|ZeVb2z54@RV`2K$?51%2wisvLC
z+M;cj^K*~#1MUL0ISkwh_IqcPZ)2-tDnDRaz-rU;*ZKJY)(_GZAAh{AVA_|LX42*S
z;5Uny)z`;tKSHX1$eXMC>93pmxb0N