Also, the media player was extended by @maddox to support the play media command.
+This has been implemented for the iTunes platform.
+]]>
+
+
- 2015-10-05T07:49:00-07:00
+ 2015-10-05T21:49:00-07:00https://home-assistant.io/blog/2015/10/05/home-assistant-goes-geo-with-owntracksA few weeks have past and it is time again for another release: version 0.7.4. This time we’re very
glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map.
@@ -61,7 +94,7 @@ short summary of highlights:
- 2015-09-19T07:47:00-07:00
+ 2015-09-19T21:47:00-07:00https://home-assistant.io/blog/2015/09/19/alarm-sonos-and-itunes-supportIt’s like someone opened a can of rock solid developers and emptied it above our
chat channel because it exploded with
@@ -2459,55 +2492,6 @@ YAML allows the use of lists, which should make the configuration file a bit mor
A connection can go stale in Chrome without any event handler being called. This happens when a device goes into standby. For computers this is rare but for phones this occurs quite often. This has been solved by sending a regular ping from the server. The frontend will assume the connection has gone stale when it hasn’t heard any communication for a while. Sending a ping will also help the server detect broken connections and clean them up.
Another issue that I encountered is that Safari and Firefox would not fire the open event when the connection has been opened but when the first message has been received. To work around this the server will now fire a ping when the connection gets opened.
-]]>
-
-
-
-
-
- 2015-02-08T09:01:23-08:00
- https://home-assistant.io/blog/2015/02/08/looking-at-the-past
- Ever since the launch of Home Assistant you have been able to track the state of your house. But the view has always been limited to what the current state is. Not what it was. Today we are going to change that by introducing two brand new components:
-
-
-
Recorder component that will record every event to a SQLite database
-
History component that will query and aggregate the recorded events
-
-
-
-
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
-
-
Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.
-
-
The history component will be enabled for new users by default. For current users, run scripts/update to upgrade to the latest version and add [history] to your home-assistant.conf file.
-Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
-
-
-
-
-
-
-
-
-
Tracking history is an exciting next step for Home Assistant and will power the next generation of features. Here a list of some of the cool things that can now be build:
-
-
-
Time Machine: explore the state of your house at any point in the past
-
Smart Home: analyze behavior and use it to automate your house
-
Summarize usage of the different components of your house
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 186acf16f4..56566d9973 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
@@ -277,6 +277,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 fbe2474306..4466449031 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -257,6 +257,12 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html b/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html
index 57d3165c86..051e976a6a 100644
--- a/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html
+++ b/blog/2015/03/01/home-assistant-migrating-to-yaml/index.html
@@ -222,6 +222,12 @@ YAML allows the use of lists, which should make the configuration file a bit mor
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index 2bc08dc60a..c3f1ea1af4 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -223,6 +223,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 e0a65a7bea..e5c3a01e64 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -269,6 +269,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 66380c7403..7e7aa64f7f 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -342,6 +342,12 @@ James Cole has also contributed support for the
diff --git a/blog/2015/04/25/release-notes/index.html b/blog/2015/04/25/release-notes/index.html
index a6da1e5f0f..0de280bc56 100644
--- a/blog/2015/04/25/release-notes/index.html
+++ b/blog/2015/04/25/release-notes/index.html
@@ -358,6 +358,12 @@ James has also contributed support for integrating Transmission into Home Assist
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index c81e574743..7b056876ac 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -384,6 +384,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 d2b33b7f34..62159502e1 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -463,6 +463,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 96634d0e78..97f4accfab 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
@@ -407,6 +407,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 6ebda76c93..6f5095a348 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
@@ -370,6 +370,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -393,12 +399,6 @@ Support for Temper temperature sensors has been contributed by
- Using MQTT with Home Assistant
-
-
-
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 e0a0258877..52a50d9bc1 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
@@ -248,6 +248,12 @@ Home Assistant support to integrate your Ver
diff --git a/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html b/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html
index 0f03dffafd..f8e9ca6499 100644
--- a/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html
+++ b/blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html
@@ -517,6 +517,12 @@ The MQTT support was added to H
Also, the media player was extended by @maddox to support the play media command.
+This has been implemented for the iTunes platform.
+]]>
+
+
- 2015-10-05T07:49:00-07:00
+ 2015-10-05T21:49:00-07:00https://home-assistant.io/blog/2015/10/05/home-assistant-goes-geo-with-owntracksA few weeks have past and it is time again for another release: version 0.7.4. This time we’re very
glad to be able to introduce brand new integration with OwnTracks to allow tracking of people on a map.
@@ -61,7 +94,7 @@ short summary of highlights:
- 2015-09-19T07:47:00-07:00
+ 2015-09-19T21:47:00-07:00https://home-assistant.io/blog/2015/09/19/alarm-sonos-and-itunes-supportIt’s like someone opened a can of rock solid developers and emptied it above our
chat channel because it exploded with
@@ -354,113 +387,6 @@ verisure:
smartplugs: 1
thermometers: 0
-]]>
-
-
-
-
-
- 2015-08-09T18:01:00-07:00
- https://home-assistant.io/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support
- It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to @balloob. If you’re a developer, make sure you read up on the deprecation notices. @fabaff did another great round of documentating all the various components.
-
-
MQTT Support
-
-The big new addition in this release is the support for the MQTT protocol by @fabaff with some help from @balloob. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (see the example) and also support for the automation component has been added. For more information, see the MQTT component page.
-
-
# Example configuration.yaml entry
-mqtt:
- broker: IP_ADDRESS_BROKER
- # All the other options are optional:
- port: 1883
- keepalive: 60
- qos: 0
- username: your_username
- password: your_secret_password
-
-
-
-
-
-
Raspberry PI GPIO Support
-
-@gbarba has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.
-
-
# Example configuration.yaml entry
-switch:
- platform: rpi_gpio
- ports:
- 11: Fan Office
- 12: Light Desk
-
-
-
ASUSWRT based routers
-
-@persandstrom has contributed support to do prescence detection using ASUSWRT based routers.
Logitech Squeezebox media player support
-
-@persandstrom also contributed support for the Logitech Squeezebox media player. This allows you to control your Logitech Squeezebox from Home Assistant.
Slack notification support
-
-@jamespcole has contributed a Slack platform for the notification platform. This allows you to deliver messages to any channel.
RFXtrx sensor support
-@danielhiversen has contributed support for RFXtrx sensors. It supports sensors that communicate in the frequency range of 433.92 MHz.
Also, the media player was extended by @maddox to support the play media command.
+This has been implemented for the iTunes platform.
+
+
+
+
+
+
@@ -121,7 +206,7 @@
- October 5, 2015
+ October 5, 2015
@@ -218,7 +303,7 @@ short summary of highlights:
- September 19, 2015
+ September 19, 2015
@@ -878,104 +963,6 @@ The big new addition in this release is the support for the MQTT protocol by
-
-
-
-
-
This release includes some architectural changes by me. The first is that the frontend is now based on a NuclearJS JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.
-
-
IP Camera Support
-James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.
-
-
Home Assistant will route the requests to your camera via the server allowing you to expose IP camera’s inside your network via the Home Assistant app.
-
-
1
-2
-3
-4
-5
-6
-7
-
# Example configuration.yaml entry
-camera:
-platform:generic
-name:my sample camera
-username:MY_USERNAME
-password:MY_PASSWORD
-still_image_url:http://194.218.96.92/jpg/image.jpg
-
-
-
-
-
-
-To update to the latest version, run scripts/update. Please report any issues on GitHub.
-
This release includes some architectural changes by me. The first is that the frontend is now based on a NuclearJS JavaScript backend. This has greatly helped to organize and optimize the frontend code. Another change is that Home Assistant will now install dependencies on-demand instead of installing dependencies for all supported devices.
+
+
IP Camera Support
+James has worked very hard to add support for IP cameras to Home Assistant which is included in this release. The initial release focusses on providing generic IP camera support. This means that any webcam that can exposes a JPEG image via a url can be integrated.
+
+
Home Assistant will route the requests to your camera via the server allowing you to expose IP camera’s inside your network via the Home Assistant app.
+
+
1
+2
+3
+4
+5
+6
+7
+
# Example configuration.yaml entry
+camera:
+platform:generic
+name:my sample camera
+username:MY_USERNAME
+password:MY_PASSWORD
+still_image_url:http://194.218.96.92/jpg/image.jpg
+
+
+
+
+
+
+To update to the latest version, run scripts/update. Please report any issues on GitHub.
+
Ever since the launch of Home Assistant you have been able to track the state of your house. But the view has always been limited to what the current state is. Not what it was. Today we are going to change that by introducing two brand new components:
-
-
-
Recorder component that will record every event to a SQLite database
-
History component that will query and aggregate the recorded events
-
-
-
-
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
-
-
Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.
-
-
The history component will be enabled for new users by default. For current users, run scripts/update to upgrade to the latest version and add [history] to your home-assistant.conf file.
-Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
-
Ever since the launch of Home Assistant you have been able to track the state of your house. But the view has always been limited to what the current state is. Not what it was. Today we are going to change that by introducing two brand new components:
+
+
+
Recorder component that will record every event to a SQLite database
+
History component that will query and aggregate the recorded events
+
+
+
+
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
+
+
Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.
+
+
The history component will be enabled for new users by default. For current users, run scripts/update to upgrade to the latest version and add [history] to your home-assistant.conf file.
+Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
+
+
+
+
+
+
diff --git a/components/device_tracker.actiontec.html b/components/device_tracker.actiontec.html
index 002cb2eaf7..6234b33120 100644
--- a/components/device_tracker.actiontec.html
+++ b/components/device_tracker.actiontec.html
@@ -144,7 +144,7 @@ This device tracker needs telnet to be enabled on the router.
Configuration variables:
-
host (Required): The IP address of your router, e.g. 192.168.1.1.
+
host (Required): The IP address of your router, eg. 192.168.1.1.
username (Required: The username of an user with administrative privileges, usually admin.
password (Required): The password for your given admin account.
home_interval (Optional): If the home_interval is set then the component will not let a device be AWAY if it has been HOME in the last home_interval minutes. This is in addition to the 3 minute wait built into the device_tracker component.
diff --git a/components/device_tracker.thomson.html b/components/device_tracker.thomson.html
index a33c22dd53..f43d58ab65 100644
--- a/components/device_tracker.thomson.html
+++ b/components/device_tracker.thomson.html
@@ -127,6 +127,15 @@ Thomson produced networking equipment (under the brand name SpeedTouch) till 201
+
Configuration variables:
+
+
+
host (Required): The IP address of your router, eg. 192.168.1.1.
+
username (Required: The username of an user with administrative privileges, usually admin.
+
password (Required): The password for your given admin account.
-The Plex platform allows you to connect a Plex Media Server to Home Assistant.
-It will allow you to control media playback and see the current playing item.
+The Plex platform allows you to connect a Plex Media Server to Home Assistant. It will allow you to control media playback and see the current playing item.
+
+
To add Plex to your installation, add the following to your configuration.yaml file:
12
@@ -117,17 +118,24 @@ It will allow you to control media playback and see the current playing item.4
56
-7
# Example configuration.yaml entrymedia_player:platform:plex
-# The name of the backend device (Under Plex Media Server > settings > server)name:plex_server
-user:your_username
-password:your_secure_password
+user:YOUR_USERNAME
+password:YOUR_PASSWORD
+
Configuration variables:
+
+
+
nameRequired: The name of the backend device (Under Plex Media Server > settings > server)
+
userRequired: The username for your Pley server.
+
passwordRequired: The password for your Plex server.
+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:
+
+
+
You need a Telegram bot. Please follow those instructions to create one and get the token. Keep in mind that bots are not allowed to contact users. You need to make the first contactwith your user.
+
The chat ID of an user
+
+
+
+
An easy way to get your chat ID is described below:
To enable Telegram notifications in your installation, add the following to your configuration.yaml file:
+
+
1
+2
+3
+4
+5
+6
+7
+
# Example configuration.yaml entry
+notify:
+name:NOTIFIER_NAME
+platform:telegram
+# Get those by creating a new bot on https://core.telegram.org/bots
+api_key:ABCDEFGHJKLMNOPQRSTUVXYZ
+chat_id:YOUR_CHAT_ID
+
+
+
+
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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.arest.html b/components/sensor.arest.html
index 43aa4b5d0f..d5f973475c 100644
--- a/components/sensor.arest.html
+++ b/components/sensor.arest.html
@@ -9,7 +9,7 @@
- aREST support - Home Assistant
+ aREST sensor support - Home Assistant
@@ -18,7 +18,7 @@
-
+
@@ -101,7 +101,7 @@
- aREST Support
+ aREST Sensor Support
diff --git a/components/sensor.command_sensor.html b/components/sensor.command_sensor.html
index 89fe843917..c1dfa0c636 100644
--- a/components/sensor.command_sensor.html
+++ b/components/sensor.command_sensor.html
@@ -196,7 +196,7 @@ is of interest. Add something similar to your configuration.yaml fi
Use an external script
-
The example is doing the same as the aREST sensor but with an external Python script. It should give you an idea about interacting with devices which are exposing a REST API.
+
The example is doing the same as the aREST sensor but with an external Python script. It should give you an idea about interacting with devices which are exposing a RESTful API.
The one-line script to retrieve a value is shown below. Of course would it be possible to use this directly in the configuration.yaml file but need extra care about the quotation marks.
-The arest switch platform allows you to toggle pins of your devices (like Arduino boards with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the aREST RESTful framework.
+The arest switch platform allows you to toggle pins of your devices (like Arduino boards with a ethernet/wifi connection, ESP8266 based devices, and the Raspberry Pi) running the aREST RESTful framework.
To use your aREST enabled device in your installation, add the following to your configuration.yaml file:
@@ -136,7 +136,7 @@ The arest switch platform allows you to toggle pins of your devices (like Arduin
Configuration variables:
-
resource (Required): IP address and schema of the device that is exposing an aREST API, e.g. http://192.168.1.10.
+
resource (Required): IP address and schema of the device that is exposing an aREST API, eg. http://192.168.1.10.
pins (Required): An array with all used pins of your board.
diff --git a/components/switch.command_switch.html b/components/switch.command_switch.html
index a3b795565a..c2c1569f02 100644
--- a/components/switch.command_switch.html
+++ b/components/switch.command_switch.html
@@ -147,6 +147,12 @@ A switch platform that issues specific commands when it is turned on and off. Th
+
Examples
+
+
In this section you find some real life examples of how to use this switch.
+
+
aREST device
+
The example below is doing the same as the aREST switch. The commandline tool [curl](http://curl.haxx.se/) is used to toogle a pin which is controllable through REST.
1
@@ -166,6 +172,32 @@ A switch platform that issues specific commands when it is turned on and off. Th
+
Shutdown your local host
+
+
This switch will shutdown your system that is hosting Home Assistant.
+
+
+This switch will shudown your host immediately, there will be no confirmation.
+
+
+
+
+
+
1
+2
+3
+4
+5
+6
+
# Example configuration.yaml entry
+switch:
+platform:command_switch
+switches:
+Home Assistant system shutdown:
+offcmd:"/usr/sbin/poweroff"
+