diff --git a/atom.xml b/atom.xml
index 931aed8ce2..be2d6b3054 100644
--- a/atom.xml
+++ b/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Home Assistant]]>
- 2016-09-10T21:40:15+00:00
+ 2016-09-11T01:32:24+00:00https://home-assistant.io/
@@ -13,6 +13,112 @@
Octopress
+
+ <![CDATA[0.28: Reload automation and groups, API documentation, car tracking, Pi-Hole stats]]>
+
+ 2016-09-10T06:00:00+00:00
+ https://home-assistant.io/blog/2016/09/10/notify-group-reload-api-pihole
+ It’s already time for 0.28 thanks to our super short release cycles. Now, it’ official…we hit 4000 stars on Github. That’s amazing. Sorry, not as amazing as all the stuff that was going on for 0.27 but still pretty awesome.
+
+
Reload automation rules
+
+
This release brings you a huge improvement of the automation and group handling. Both can be reloaded without a Home Assistant restart. The automations can be controlled directly from the frontend.
+
+
+
+
+
+
Raspberry Pi installation guide
+
Singleboard computers are very popular to run Home Assistant. To support this fact, the installation documentation for the Raspberry Pi devices was re-written to get users started as quickly as possible. @Landrash took the lead with on this tasks with help from @kellerza and @MartinHjelmare.
+
+
Climate and cover
+
There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…
+
+
API documentation
+
The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.
+
+
Configuration validation
+
The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!
+
+
Templating
+
data_template needs to be present in all notify templates for the future.
Device tracker: Fix TP-Link Archer C7 long passwords (@snikch)
+
+
+
Breaking changes
+
+
+
OpenweatherMap entity IDs are now like sensor.owm_temperature. Previously they were like sensor.weather_temperature. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
+
Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
+
Custom components extending BaseNotificationService need to be aware that kwargs.get(ATTR_TITLE) will now return None if a title has not been set, and will need to specify kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT) if they always require a title.
+
+
+
If you need help…
+
…don’t hesitate to use our Forum or join us for a little chat.
+
+]]>
+
+
<![CDATA[ESP8266 and MicroPython - Part 2]]>
@@ -1737,158 +1843,6 @@ target_dir /tmp
-]]>
-
-
-
- <![CDATA[iBeacons: How to track things that can’t track themselves (part II)]]>
-
- 2016-05-26T11:06:12+00:00
- https://home-assistant.io/blog/2016/05/26/ibeacons-how-to-track-things-that-cant-track-themselves-part-ii
- This post is by Home Assistant contributor Greg Dowling.
-
-
In Part 1 I talked about using iBeacons to improve presence tracking. In part 2 I’ll talk about how to track things like keys that can’t track themselves by using iBeacons.
-
-
Tracking things using iBeacons
-
In the first part I mentioned that iBeacons just send out I’m here packets, and we used this to trigger an update when your phone came close to a fixed beacon.
-
-
But beacons don’t have to be fixed.
-
-
Your phone knows roughly where it is located (based on mobile phone masts, Wi-Fi networks or GPS). If your phone sees an I’m here message then it knows the beacon is close.
-
-
If your phone can remember (or tell a server) where it was when it last saw the iBeacon - then it knows where the beacon was. So the result of this is that you can track where an iBeacon was - even though the iBeacon doesn’t have any tracking technology itself.
-
-
So if you put an iBeacon on your keys or in your car - then you can track them.
-
-
-
- Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
-
-
-
-
-
It’s easier to set up OwnTracks and HA to track a mobile beacon than the fixed beacon I discussed in Part 1, because you only need to tell OwnTracks about your iBeacon. You don’t need to configure HA at all.
-
-
OwnTracks currently only supports mobile beacons on iOS.
-
-
You set up the beacon the same way as we discussed in part 1. The only difference is that instead of calling the region the name of a location (eg -drive) you call it the name of the device you want to track (eg -keys). Remember the leading ‘-’ that makes the connection more reliable.
-
-
-
-
-
-
Once you’ve added the iBeacon - you should be able to see it on the OwnTracks region screen. If your phone can see the packets from that beacon, OwnTracks will turn the relevant Region red.
-
-
Because you turned Share on for the region, when OwnTracks sees the beacon it will send HA a message. HA will use this message to add the beacon as a tracked device if it hasn’t seen it before. So you should see a new device appear in HA called device_tracker.beacon_[name] - and its location will be where your phone thought it was when it last saw the beacon.
-
-
-
-
-
-
If your phone moves and sends HA a new location while it is still in range of the beacon - HA will update the location of the beacon. So if go for a drive in your car - you will see both your phone and the device_tracker.beacon_car move together.
-
-
If you park your car and go shopping - device_tracker.beacon_car will stop moving.
-
-
With the basic tracking working - you can use automation to do things like open your gates if your car comes home
HA updates the beacon and phone locations at slightly different times - so you don’t want the automation to trigger in the gap between the updates
-
I’ve found that beacons (especially the low power Estimote Nearables) can get disconnected for a few seconds so it’s best to wait a minute or so before deciding that you’ve left your keys behind)
-
-
-
Using both types of iBeacons at the same time
-
Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I’ve been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.
-
-
-
-
-
Long range / High power beacon
-
-
-
-
-
Waterproof beacon
-
-
Buying Beacons
-
This isn’t a buyer’s guide, but I just wanted to mention the iBeacons I’ve been using. I think you should be able to use any iBeacon with HA and OwnTracks. You generally can’t buy beacons in your local electronics shop - so I just wanted to briefly mention the two suppliers I’ve used so far.
-
-
I’ve bought quite a few iBeacons from a company called Blue Sense Networks. I work in the tech startup sector in the UK so I partly chose them because they are a local start-up who seemed worth supporting. The products, support and software all seem good. I use a number of their beacons - from a simple USB dongle, to a long range beacon. All their products have batteries that can be changed (or no batteries in the case of the externally powered USB device) - and you can configure all the parameters you’d want to using their software. I had one software issue, support got back to me at a weekend(!) - and the issue was resolved with a software release two days later.
-
-
All the beacons seem fine - and the long range unit does work over a longer range than my other beacons.
-
-
I bought some other beacons from a US/Polish startup called Estimote, who I think are better known. I bought a developer pack of 10 of their nearables which as well as being iBeacons also send out other data (orientation and motion) using their own protocol. This is interesting if you’re developing your own application, but for OwnTracks and HA they are just regular beacons. They are small and self adhesive - so you can stick them to things (like your keys). You can’t change all the parameters on these devices (UUID/Major/Minor are fixed) - and the batteries can’t be replaced. I also killed one of the estimote beacons (I assume the battery died) after I carried it around for a few months and dropped it many times! On the other hand they are well priced, small and waterproof!
-
-
I’ve mainly used these as devices to track rather that location beacons. Estimote also sell some slightly larger iBeacons with replaceable batteries. Estimote support responded quickly and were helpful when I couldn’t work out how to edit their beacon’s parameters (although the answer was you can’t yet).
-
-
The larger Blue Sense Network beacons seem to be better at maintaining a connection that the Estimotes - although that might be because I’m reluctant to turn the power to maximum and reduce the gap between sending packets on the Estimotes where I can’t replace the batteries!
-
-
Conclusion
-
As I said in part 1, I’ve found iBeacons to be a good way of improving presence detection. I also used them to track devices like my car and my keys that can’t track themselves.
-
-
I’m still experimenting, so I hope I can do more with iBeacons. I hope I’ve encouraged you do so the same. If you do please share your experiences.
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 5deffc7fb1..04b6e6b918 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
@@ -224,6 +224,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 24aee91ebd..833f8f27ab 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -200,6 +200,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 56e6f4f41b..a265f3a377 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -176,6 +176,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 1957ff7747..27c7ba3087 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -209,6 +209,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 23e6dc5f1c..a64b91244e 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -244,6 +244,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 a8352390d8..c7d340dafd 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -276,6 +276,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 756b37dc29..20eaf9699b 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -327,6 +327,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 e8a3b796da..12904621ba 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
@@ -283,6 +283,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 0420ebaf09..4c5323a46f 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
@@ -268,6 +268,12 @@ Support for Temper temperature sensors has been contributed by
+
@@ -291,12 +297,6 @@ Support for Temper temperature sensors has been contributed by
- 0.26: Foursquare, Fast.com, FFMPEG and GPSD
-
-
-
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 d2ab28c2f6..e0ac17ddfb 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
@@ -192,6 +192,12 @@
diff --git a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
index 57f8b75f19..d734c732a3 100644
--- a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
+++ b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
@@ -305,6 +305,12 @@ The automation and script syntax here is using a deprecated and no longer suppor
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 d604b8a83b..70b4274777 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
@@ -234,6 +234,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 8dc7be8522..08cd2816ee 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
@@ -219,6 +219,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 35a640b11a..2997360d05 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
@@ -199,6 +199,12 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index fd5466989f..924dd14d43 100644
--- a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
+++ b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
@@ -408,6 +408,12 @@ Home Assistant will keep track of historical values and allow you to integrate i
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 5e2ad9cdea..2a7f0ab5bb 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
@@ -210,6 +210,12 @@ This makes more sense as most people run Home Assistant as a daemon
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index 727bf3b577..4f8b07dd8c 100644
--- a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
+++ b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
@@ -225,6 +225,12 @@ This is where we’ll configure our task, so select the plus icon to select an a
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 119bc85328..20241c70b7 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
@@ -208,6 +208,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 86e4dec581..ee81264eff 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -219,6 +219,12 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
diff --git a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
index d91fe3cc0f..c3fe9c6c13 100644
--- a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
+++ b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
@@ -299,6 +299,12 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index ab4ba3fc61..9e030c18cf 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -218,6 +218,12 @@ Over a year ago I participated in the
+
@@ -241,12 +247,6 @@ Over a year ago I participated in the
- 0.26: Foursquare, Fast.com, FFMPEG and GPSD
-
-
-
diff --git a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
index daaa56c21b..e56e1dd1eb 100644
--- a/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
+++ b/blog/2016/07/16/sqlalchemy-knx-join-simplisafe/index.html
@@ -218,6 +218,12 @@
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 9a944a8704..68edbcce7a 100644
--- a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
+++ b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
@@ -235,6 +235,12 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index fa439948c9..0b49585ac4 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -322,6 +322,12 @@ If a module is missing then you need to download it from the
+
@@ -345,12 +351,6 @@ If a module is missing then you need to download it from the
- 0.26: Foursquare, Fast.com, FFMPEG and GPSD
-
-
-
diff --git a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
index 7a57fc04e0..5d087dab5c 100644
--- a/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
+++ b/blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
@@ -237,6 +237,12 @@
diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
index 19ba0e1516..05d85b2a4c 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -266,6 +266,12 @@ So, part 1 of ESP8266
It’s already time for 0.28 thanks to our super short release cycles. Now, it’ official…we hit 4000 stars on Github. That’s amazing. Sorry, not as amazing as all the stuff that was going on for 0.27 but still pretty awesome.
+
+
Reload automation rules
+
+
This release brings you a huge improvement of the automation and group handling. Both can be reloaded without a Home Assistant restart. The automations can be controlled directly from the frontend.
+
+
+
+
+
+
Raspberry Pi installation guide
+
Singleboard computers are very popular to run Home Assistant. To support this fact, the installation documentation for the Raspberry Pi devices was re-written to get users started as quickly as possible. @Landrash took the lead with on this tasks with help from @kellerza and @MartinHjelmare.
+
+
Climate and cover
+
There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…
+
+
API documentation
+
The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.
+
+
Configuration validation
+
The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!
+
+
Templating
+
data_template needs to be present in all notify templates for the future.
Device tracker: Fix TP-Link Archer C7 long passwords (@snikch)
+
+
+
Breaking changes
+
+
+
OpenweatherMap entity IDs are now like sensor.owm_temperature. Previously they were like sensor.weather_temperature. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
+
Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
+
Custom components extending BaseNotificationService need to be aware that kwargs.get(ATTR_TITLE) will now return None if a title has not been set, and will need to specify kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT) if they always require a title.
+
+
+
If you need help…
+
…don’t hesitate to use our Forum or join us for a little chat.
+
+
+
+
+
Comments
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/blog/archives/index.html b/blog/archives/index.html
index 09e7347ccd..cec814d5f0 100644
--- a/blog/archives/index.html
+++ b/blog/archives/index.html
@@ -2769,6 +2769,38 @@
+
+
+
+
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index 5a71749aa5..6528d64274 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Release-Notes | Home Assistant]]>
- 2016-09-10T21:40:15+00:00
+ 2016-09-11T01:32:24+00:00https://home-assistant.io/
@@ -13,6 +13,159 @@
Octopress
+
+ <![CDATA[0.28: Reload automation and groups, API documentation, car tracking, Pi-Hole stats]]>
+
+ 2016-09-10T06:00:00+00:00
+ https://home-assistant.io/blog/2016/09/10/notify-group-reload-api-pihole
+ Reload automation rules
+
+This release brings you a huge improvement of the [automation] and [group] handling. Both can be reloaded without a Home Assistant restart. The automations can be controlled directly from the frontend.
+
+
+
+
+
+### Raspberry Pi installation guide
+Singleboard computers are very popular to run Home Assistant. To support this fact, the [installation documentation][rpi] for the Raspberry Pi devices was re-written to get users started as quickly as possible. [@Landrash] took the lead with on this tasks with help from [@kellerza] and [@MartinHjelmare].
+
+### Climate and cover
+There are countless bugfixes included in this release which will make your experience with the `climate` and the `cover` platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to [@turbokongen], [@pvizeli], [@djbanks], [@danielperna84], and others the improvements on the code and the frontend side is continuing...
+
+### API documentation
+The [Home Assistant API Documentation](https://dev-docs.home-assistant.io/en/dev/) is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.
+
+### Configuration validation
+The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to [@kellerza], [@fabaff], [@Teagan42], and [@pvizeli] for your effort!
+
+### Templating
+`data_template` needs to be present in all notify templates for the future.
+
+```yaml
+action:
+ service: notify.telegram
+ data_template:
+ message: "Test from your Home"
+ data:
+ location:
+ latitude: ""
+ longitude: ""
+```
+
+Stay tuned for more details.
+
+### All changes
+
+
+
+- Light: Added bitfield to Flux LED since we are supporting effects ([@tchellomello])
+- Device tracker: [Owntracks] waypoint import ([@pavoni])
+- Climate: A lot of bugfix ([@turbokongen], [@pvizeli], [@djbanks])
+- Notify: Improvement of the title handling ([@lwis])
+- RFXtrx: Sensor cleanup ([@turbokongen])
+- Device tracker: Fix for BLE device tracker ([@open-homeautomation])
+- Device tracker: Allow 'None' MAC addresses to be loaded from `known_devices` file ([@kellerza])
+- Cover: Bugfixes ([@turbokongen], [@danielperna84])
+- Sensor: Support for displaying details about [crypto currencies][Coinmarketcap] ([@fabaff])
+- Device tracker: Support for [automatic] to track your vehicles ([@Teagan42])
+- Devie tracker: Add exclude option to [Nmap] device tracker ([@danieljkemp])
+- Device tracker: Improved login errors for Asus device tracker ([@kellerza])
+- Sensor: Support for displaying the status of [Xbox] Live accounts ([@mKerix])
+- Notify: Adding `link_names` for sending Slack message ([@salt-lick])
+- Binary sensor: Add the occupancy sensor class ([@robbiet480])
+- Fan: Add supoort for [MQTT fans][mqtt-fan] ([@robbiet480])
+- Docs: Add Sphinx API doc generation ([@bbangert])
+- Core: Allow reloading automation without restart ([@balloob])
+- Sensor: Added scale and offset to the [Temper] sensor ([@mKerix])
+- Sensor: New support for [Trend] sensor ([@pavoni])
+- Device tracker: Keep looking for new BLE devices ([@Bart274])
+- Switch: Added device state attributes and support for legacy firmware for D-Link switches ([@LinuxChristian])
+- Sensor: Improve 1-Wire device family detection ([@Ardetus])
+- Modbus: Update to be thread safe ([@persandstrom])
+- Camera: FFMpeg is abale to get the images ([@pvizeli])
+- Core: Reload groups without restart ([@balloob])
+- Core: Fix remove listener ([@balloob])
+- Sensor: Support for monitoring your [battery] on a Linux host ([@fabaff])
+- Core: Add support for complex template structures to `data_template` ([@pvizeli])
+- `check_config`: Improve yaml fault tolerance and handle border cases ([@kellerza])
+- Core: Add additional [template] for custom date formats ([@lwis])
+- Sensor: Support for getting stats from Pi-Hole systems ([@fabaff])
+- Modbus: New `write_registers` [Modbus] service ([@persandstrom])
+- Device tracker: Fix TP-Link Archer C7 long passwords ([@snikch])
+
+### Breaking changes
+
+- [OpenweatherMap] entity IDs are now like `sensor.owm_temperature`. Previously they were like `sensor.weather_temperature`. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
+- Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
+ - [OctoPrint] component
+ - mFi platform ([switch][mfi-switch] and [sensor][mfi-sensor])
+ - NX584 Alarm Control Panel
+ - Mediaplayer platforms [FireTV] and [MPD]
+ - [switch][command-line-switch] and the [cover][command-line-cover] `command_line` platforms
+- Custom components extending `BaseNotificationService` need to be aware that `kwargs.get(ATTR_TITLE)` will now return `None` if a title has not been set, and will need to specify `kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT)` if they always require a title.
+
+### If you need help...
+...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant).
+
+
+[@Ardetus]: https://github.com/Ardetus
+[@arsaboo]: https://github.com/arsaboo
+[@auchter]: https://github.com/auchter
+[@balloob]: https://github.com/balloob
+[@Bart274]: https://github.com/Bart274
+[@bbangert]: https://github.com/bbangert
+[@danieljkemp]: https://github.com/danieljkemp
+[@danielperna84]: https://github.com/danielperna84
+[@djbanks]: https://github.com/djbanks
+[@fabaff]: https://github.com/fabaff
+[@infamy]: https://github.com/infamy
+[@jnewland]: https://github.com/jnewland
+[@kellerza]: https://github.com/kellerza
+[@Landrash]: https://github.com/Landrash
+[@LinuxChristian]: https://github.com/LinuxChristian
+[@lwis]: https://github.com/lwis
+[@MartinHjelmare]: https://github.com/MartinHjelmare
+[@mKerix]: https://github.com/mKerix
+[@nkgilley]: https://github.com/nkgilley
+[@open-homeautomation]: https://github.com/open-homeautomation
+[@pavoni]: https://github.com/pavoni
+[@persandstrom]: https://github.com/persandstrom
+[@pvizeli]: https://github.com/pvizeli
+[@robbiet480]: https://github.com/robbiet480
+[@salt-lick]: https://github.com/salt-lick
+[@tchellomello]: https://github.com/tchellomello
+[@Teagan42]: https://github.com/Teagan42
+[@technicalpickles]: https://github.com/technicalpickles
+[@turbokongen]: https://github.com/turbokongen
+[@w1ll1am23]: https://github.com/w1ll1am23
+[@snikch]: https://github.com/snikch
+
+[modbus]: /components/modbus/
+[rpi]: /getting-started/installation-raspberry-pi/
+[MPD]: /components/media_player.mpd/
+[Coinmarketcap]: /components/sensor.coinmarketcap
+[template]: /topics/templating/
+[battery]: /components/sensor.linux_battery
+[group]: /components/group/
+[automation]: /components/automation/
+[Temper]: /components/sensor.temper/
+[mqtt-fan]: /components/fan.mqtt/
+[Xbox]: /components/sensor.xbox_live/
+[Nmap]: /components/device_tracker.nmap_scanner/
+[automatic]: /components/device_tracker.automatic/
+[Owntracks]: /components/device_tracker.owntracks/
+[OpenweatherMap]: /components/sensor.openweathermap/
+[OctoPrint]: /components/octoprint/
+[mfi-switch]: /components/switch.mfi/
+[mfi-sensor]: /components/sensor.mfi/
+[FireTV]: /components/media_player.firetv/
+[command-line-switch]: /components/switch.command_line/
+[command-line-cover]: /components/cover.command_line/
+]]>
+
+
<![CDATA[0.27 is here to break eggs and take names: notifications, Hue fakery, safety and unification come to Home Assistant]]>
@@ -614,109 +767,6 @@ Quick hot fix after we found a bug in the migrator where it wouldn't work with a
[yahoo-weather]: /components/sensor.yweather/
[Z-Wave]: /components/zwave/
[RFXtrx]: //components/rfxtrx/
-]]>
-
-
-
- <![CDATA[0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV]]>
-
- 2016-07-01T00:31:00+00:00
- https://home-assistant.io/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv
-
-
-- Support for [Envisalink] added ([alarm control panel][envi-alarm], [binary sensor][envi-binary-sensor], [sensor][envi-sensor]) ([@cinntax])
-- Support for [Homematic] added ([binary sensor][hm-binary-sensor], [light][hm-light], [rollershutter][hm-rollershutter], [sensor][hm-sensor], [switch][hm-switch]) ([@pvizeli], [@danielperna84])
-- New [HDMI-CEC] component ([@happyleavesaoc], [@lukas-hetzenecker])
-- Major rewrite of [Wink] which now pushes changes to Home Assistant ([@w1ll1am23])
-- Core: new add [reload core config service] ([@balloob])
-- Support for [persistent notifications] added ([@fabaff], [@balloob])
-- Garage door: [Z-Wave][zwave-garage-door] support added ([@turbokongen])
-- Rollershutter: [Z-Wave][zwave-rollershutter] support added ([@turbokongen])
-- Media Player: [Sony Bravia TV] now supported ([@aparraga])
-- Sensor: [Fixer.io] now supported ([@fabaff])
-- Garage door: Control any garage door using [Raspberry Pi GPIO pins] ([@kellerza])
-- Sensor: [OpenExchangeRates] support added ([@arsaboo])
-- Notify: [Pushover] now supports target device, sound, url and priority ([@dale3h])
-- Sensor: [Netatmo] now supports wind, battery and radio signals ([@Jypy])
-- Log successful and failed login attemps ([@fabaff])
-- Config: allow [extracting account info][secrets] into OS keyring or separate YAML file ([@kellerza])
-- Core: add option to not filter out duplicate states per entity ([@philipbl])
-- HTTP: Follow Mozilla SSL recommendations ([@danieljkemp], [@AlucardZero])
-- Light: [Z-Wave colorbulb][zwave-light] support added ([@armills])
-- Core: new elevation config option added ([@balloob])
-- Sensor: [OneWire] support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. ([@Ardetus])
-- Lock: [Vera] now supported ([@rhooper])
-- HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems ([@balloob])
-
-### Breaking changes
-
-- Homematic thermostat configuration has changed and now depends on the new [Homematic] component.
-
-### Hotfix 0.23.1 - July 2
-
-- Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug ([@rhooper])
-- HTTP - SSL: Check for OP_NO_COMPRESSION support before trying to use it ([@AlucardZero])
-- Wink: Downgraded pubnub to work around pycryptodome conflicts ([@w1ll1am23])
-
-### FAQ
-
-- `elevation: ` was introduced to the configuration for weather/sunrise data. For existing [configurations][elevation] add the value shown in the warning `[homeassistant.config] Incomplete core config. Auto detected elevation: 665` to your `configuration.yaml` file.
-
-[@AlucardZero]: https://github.com/AlucardZero/
-[@aparraga]: https://github.com/aparraga/
-[@Ardetus]: https://github.com/Ardetus/
-[@armills]: https://github.com/armills/
-[@arsaboo]: https://github.com/arsaboo/
-[@balloob]: https://github.com/balloob/
-[@cinntax]: https://github.com/cinntax/
-[@dale3h]: https://github.com/dale3h/
-[@danieljkemp]: https://github.com/danieljkemp/
-[@danielperna84]: https://github.com/danielperna84/
-[@fabaff]: https://github.com/fabaff/
-[@happyleavesaoc]: https://github.com/happyleavesaoc/
-[@Jypy]: https://github.com/Jypy/
-[@kellerza]: https://github.com/kellerza/
-[@lukas-hetzenecker]: https://github.com/lukas-hetzenecker/
-[@philipbl]: https://github.com/philipbl/
-[@pvizeli]: https://github.com/pvizeli/
-[@rhooper]: https://github.com/rhooper/
-[@turbokongen]: https://github.com/turbokongen/
-[@w1ll1am23]: https://github.com/w1ll1am23/
-[envi-alarm]: /components/alarm_control_panel.envisalink/
-[envi-binary-sensor]: /components/binary_sensor.envisalink/
-[envi-sensor]: /components/sensor.envisalink/
-[Envisalink]: /components/envisalink/
-[HDMI-CEC]: /components/hdmi_cec/
-[hm-binary-sensor]: /components/binary_sensor.homematic/
-[hm-light]: /components/light.homematic/
-[hm-rollershutter]: /components/rollershutter.homematic/
-[hm-sensor]: /components/sensor.homematic/
-[hm-switch]: /components/switch.homematic/
-[Homematic]: /components/homematic/
-[Netatmo]: /components/sensor.netatmo/
-[OneWire]: /components/sensor.onewire/
-[OpenExchangeRates]: /components/sensor.openexchangerates/
-[Pushover]: /components/notify.pushover/
-[secrets]: /topics/secrets/
-[Vera]: /components/lock.vera/
-[Wink]: /components/wink/
-[zwave-garage-door]: /components/garage_door.zwave/
-[zwave-light]: /components/light.zwave/
-[zwave-rollershutter]: /components/rollershutter.zwave/
-[Fixer.io]: /components/sensor.fixer/
-[persistent notifications]: /components/persistent_notification/
-[reload core config service]: /getting-started/customizing-devices/#reloading-customize
-[Sony Bravia TV]: /components/media_player.braviatv/
-[Raspberry Pi GPIO pins]: /components/garage_door.rpi_gpio/
-[elevation]: https://home-assistant.io/getting-started/basic/
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index c82f521fcf..cf71b954e3 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -98,6 +98,38 @@
It’s already time for 0.28 thanks to our super short release cycles. Now, it’ official…we hit 4000 stars on Github. That’s amazing. Sorry, not as amazing as all the stuff that was going on for 0.27 but still pretty awesome.
+
+
Reload automation rules
+
+
This release brings you a huge improvement of the automation and group handling. Both can be reloaded without a Home Assistant restart. The automations can be controlled directly from the frontend.
+
+
+
+
+
+
Raspberry Pi installation guide
+
Singleboard computers are very popular to run Home Assistant. To support this fact, the installation documentation for the Raspberry Pi devices was re-written to get users started as quickly as possible. @Landrash took the lead with on this tasks with help from @kellerza and @MartinHjelmare.
+
+
Climate and cover
+
There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…
+
+
API documentation
+
The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.
+
+
Configuration validation
+
The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!
+
+
Templating
+
data_template needs to be present in all notify templates for the future.
Device tracker: Fix TP-Link Archer C7 long passwords (@snikch)
+
+
+
Breaking changes
+
+
+
OpenweatherMap entity IDs are now like sensor.owm_temperature. Previously they were like sensor.weather_temperature. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
+
Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
+
Custom components extending BaseNotificationService need to be aware that kwargs.get(ATTR_TITLE) will now return None if a title has not been set, and will need to specify kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT) if they always require a title.
+
+
+
If you need help…
+
…don’t hesitate to use our Forum or join us for a little chat.
+
+
+
+
+
+
+
@@ -856,69 +994,6 @@ The first release of Micropython for ESP8266 was delivered a couple of weeks ago
-
-
-
-
This is the first blog post by Anton Kireyeu. A new contributor to Home Assistant who will focus on exploring and visualizing Home Assistant data.
-
-
As we learned in the recent blog post by Fabian, all operational data of your Home Assistant application is stored locally and is available for exploration. Our first steps were querying data with the DB Browser for SQLite, exporting the data extract as a CSV file and graphing in LibreOffice. But what else can be done with this data and what tools are there available?
-
-
This post will help you get set up using a few popular data scientist tools to allow you to locally process your data:
-
-
-
Pandas: an open source tool for data analysis for Python
This is the first blog post by Anton Kireyeu. A new contributor to Home Assistant who will focus on exploring and visualizing Home Assistant data.
+
+
As we learned in the recent blog post by Fabian, all operational data of your Home Assistant application is stored locally and is available for exploration. Our first steps were querying data with the DB Browser for SQLite, exporting the data extract as a CSV file and graphing in LibreOffice. But what else can be done with this data and what tools are there available?
+
+
This post will help you get set up using a few popular data scientist tools to allow you to locally process your data:
+
+
+
Pandas: an open source tool for data analysis for Python
This post is by Home Assistant contributor Greg Dowling.
-
-
In Part 1 I talked about using iBeacons to improve presence tracking. In part 2 I’ll talk about how to track things like keys that can’t track themselves by using iBeacons.
-
-
Tracking things using iBeacons
-
In the first part I mentioned that iBeacons just send out I’m here packets, and we used this to trigger an update when your phone came close to a fixed beacon.
-
-
But beacons don’t have to be fixed.
-
-
Your phone knows roughly where it is located (based on mobile phone masts, Wi-Fi networks or GPS). If your phone sees an I’m here message then it knows the beacon is close.
-
-
If your phone can remember (or tell a server) where it was when it last saw the iBeacon - then it knows where the beacon was. So the result of this is that you can track where an iBeacon was - even though the iBeacon doesn’t have any tracking technology itself.
-
-
So if you put an iBeacon on your keys or in your car - then you can track them.
-
-
-
- Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
-
This post is by Home Assistant contributor Greg Dowling.
+
+
In Part 1 I talked about using iBeacons to improve presence tracking. In part 2 I’ll talk about how to track things like keys that can’t track themselves by using iBeacons.
+
+
Tracking things using iBeacons
+
In the first part I mentioned that iBeacons just send out I’m here packets, and we used this to trigger an update when your phone came close to a fixed beacon.
+
+
But beacons don’t have to be fixed.
+
+
Your phone knows roughly where it is located (based on mobile phone masts, Wi-Fi networks or GPS). If your phone sees an I’m here message then it knows the beacon is close.
+
+
If your phone can remember (or tell a server) where it was when it last saw the iBeacon - then it knows where the beacon was. So the result of this is that you can track where an iBeacon was - even though the iBeacon doesn’t have any tracking technology itself.
+
+
So if you put an iBeacon on your keys or in your car - then you can track them.
+
+
+
+ Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
+
One of the main complaints that we receive is something along the lines “I read that X is possible yet I am unable to find it on the website.”. This post is to announce that we have taken the first steps to improve it by revamping the getting started and developers sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.
-
-
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and called it a website. Back then we had a whopping 11 components.
-
-
As Home Assistant grew, so did our documentation. Fabian Affolter does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our frequent releases! But despite all the efforts, the documentation outgrew our existing documentation organisation.
-
-
Today it has been almost 1.5 years since we started the website. We now have 264 components and platforms under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
-
-
Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.
One of the main complaints that we receive is something along the lines “I read that X is possible yet I am unable to find it on the website.”. This post is to announce that we have taken the first steps to improve it by revamping the getting started and developers sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.
+
+
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and called it a website. Back then we had a whopping 11 components.
+
+
As Home Assistant grew, so did our documentation. Fabian Affolter does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our frequent releases! But despite all the efforts, the documentation outgrew our existing documentation organisation.
+
+
Today it has been almost 1.5 years since we started the website. We now have 264 components and platforms under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
+
+
Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.
+
+
+
+
+
+
@@ -737,109 +786,6 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
-
-
-
-
-
-
-
-
The core of home automation is knowing what’s going on. The faster we know about a state change, the better we can serve the user. If you want to have your lights to turn on when you arrive at home, it doesn’t help if it only knows about it after you’ve already opened the door and manually (!!) turned on the light.
-
-
Each smart device consists of the ‘normal’ device and the piece that makes it ‘smart’: the connectivity. The connectivity part of a device can consists of either control, state or both.
-
-
State describes what a device is up to right now. For example, a light can be on with a red color and a medium brightness.
-
-
Control is about controlling the smart device by sending commands via an API. These commands can vary from configuring how a device works till mimicking how a user would interact with a device. A media player can allow skipping to the next track and a sensor could allow to configure its sensitivity or polling interval.
-
-
The Home Assistant APIs are setup to be as convenient as possible. However, a network is always as weak as it’s weakest link. In our case these are the integrations. Take for example controlling a light that does not report state. The only state Home Assistant can report on after sending a command is the assumed state: what do we expect the state of the light to be if the command worked.
-
-
We want our users to get the best home automation experience out there and this starts with making sure they have devices that work well with Home Assistant. That’s why we will start applying the following classifiers to our integrations:
-
-
-
-
-
Classifier
-
Description
-
-
-
-
Assumed State
-
- We are unable to get the state of the device. Best we can do is to assume the state based on our last command.
-
-
-
-
-
-
Cloud Polling
-
- Integration of this device happens via the cloud and requires an active internet connection. Polling the state means that an update might be noticed later.
-
-
-
-
-
-
Cloud Push
-
- Integration of this device happens via the cloud and requires an active internet connection. Home Assistant will be notified as soon as a new state is available.
-
-
-
-
-
-
Local Polling
-
- Offers direct communication with device. Polling the state means that an update might be noticed later.
-
-
-
-
-
-
Local Push
-
- Offers direct communication with device. Home Assistant will be notified as soon as a new state is available.
-
-
-
-
-
The background to how we got to these classifiers can be read after the break.
The core of home automation is knowing what’s going on. The faster we know about a state change, the better we can serve the user. If you want to have your lights to turn on when you arrive at home, it doesn’t help if it only knows about it after you’ve already opened the door and manually (!!) turned on the light.
+
+
Each smart device consists of the ‘normal’ device and the piece that makes it ‘smart’: the connectivity. The connectivity part of a device can consists of either control, state or both.
+
+
State describes what a device is up to right now. For example, a light can be on with a red color and a medium brightness.
+
+
Control is about controlling the smart device by sending commands via an API. These commands can vary from configuring how a device works till mimicking how a user would interact with a device. A media player can allow skipping to the next track and a sensor could allow to configure its sensitivity or polling interval.
+
+
The Home Assistant APIs are setup to be as convenient as possible. However, a network is always as weak as it’s weakest link. In our case these are the integrations. Take for example controlling a light that does not report state. The only state Home Assistant can report on after sending a command is the assumed state: what do we expect the state of the light to be if the command worked.
+
+
We want our users to get the best home automation experience out there and this starts with making sure they have devices that work well with Home Assistant. That’s why we will start applying the following classifiers to our integrations:
+
+
+
+
+
Classifier
+
Description
+
+
+
+
Assumed State
+
+ We are unable to get the state of the device. Best we can do is to assume the state based on our last command.
+
+
+
+
+
+
Cloud Polling
+
+ Integration of this device happens via the cloud and requires an active internet connection. Polling the state means that an update might be noticed later.
+
+
+
+
+
+
Cloud Push
+
+ Integration of this device happens via the cloud and requires an active internet connection. Home Assistant will be notified as soon as a new state is available.
+
+
+
+
+
+
Local Polling
+
+ Offers direct communication with device. Polling the state means that an update might be noticed later.
+
+
+
+
+
+
Local Push
+
+ Offers direct communication with device. Home Assistant will be notified as soon as a new state is available.
+
+
+
+
+
The background to how we got to these classifiers can be read after the break.
Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.
-
-
It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.
-
-
-
-
-
-
Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.
Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.
+
+
It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.
+
+
+
+
+
+
Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.
It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.
-
-
Line Charts
-James has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. See the demo for a live example.
-
-
-
-
-
-
ISY994 hub support
-Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
Logbook
- I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example.
-
It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.
+
+
Line Charts
+James has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. See the demo for a live example.
+
+
+
+
+
+
ISY994 hub support
+Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
Logbook
+ I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example.
+
One of the things that was missing in Home Assistant for a while was a way to communicate with users. Wouldn’t it be nice to get a message when important events happen like the lights being turned on while no one is home? Since the Home Assistant frontend runs as a web application on the phone, we have no way to bring ourselves to the front. This is where the new notify component comes in, powered by PushBullet.
-
-
The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome PushBullet but any other messaging platform can be easily added.
-
-
-
- A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
-
-
-
Read on to learn how to enable the notify component and integrate it with other components.
One of the things that was missing in Home Assistant for a while was a way to communicate with users. Wouldn’t it be nice to get a message when important events happen like the lights being turned on while no one is home? Since the Home Assistant frontend runs as a web application on the phone, we have no way to bring ourselves to the front. This is where the new notify component comes in, powered by PushBullet.
+
+
The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome PushBullet but any other messaging platform can be easily added.
+
+
+
+ A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
+
+
+
Read on to learn how to enable the notify component and integrate it with other components.
# Example configuration.yaml entryalarm_control_panel:platform:nx584
- host:ADDRESS
+ host:IP_ADDRESS
+ port:5007
Configuration variables:
-
host (Optional): This is the host connection string (host:port) for the nx584 server process. If unset, it is assumed to be localhost:5007, which will work if the server process is running on the same system as home-assistant.
+
host (Optional): The host where the nx584 server process is running. Defaults to localhost.
+
port (Optional): The port where the Alarm panel ist listening. Defaults to 5007.
diff --git a/components/binary_sensor.arest/index.html b/components/binary_sensor.arest/index.html
index 2ac8d7322d..84359bdb32 100644
--- a/components/binary_sensor.arest/index.html
+++ b/components/binary_sensor.arest/index.html
@@ -211,6 +211,9 @@ This sensor is not suitable for fast state changes because there is a high possi
diff --git a/components/binary_sensor.ffmpeg/index.html b/components/binary_sensor.ffmpeg/index.html
index b257af5121..43c68bb469 100644
--- a/components/binary_sensor.ffmpeg/index.html
+++ b/components/binary_sensor.ffmpeg/index.html
@@ -263,6 +263,9 @@ You need the ffmpeg binary in your system
diff --git a/components/binary_sensor.http/index.html b/components/binary_sensor.http/index.html
index cffadccb7b..957a82a703 100644
--- a/components/binary_sensor.http/index.html
+++ b/components/binary_sensor.http/index.html
@@ -244,6 +244,9 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
diff --git a/components/binary_sensor.nest/index.html b/components/binary_sensor.nest/index.html
index 82b566ef8b..e0afba4108 100644
--- a/components/binary_sensor.nest/index.html
+++ b/components/binary_sensor.nest/index.html
@@ -224,6 +224,9 @@ You must have the Nest component configured to u
The trend platform allows you to create sensors which show the trend of numeric state orstate_attributes from other entities. This sensor requires two updates of the underlying sensor to establish a trend - so it can take some time to show an accurate state. It can be useful as part of automations, where you want to base an action on a trend.
+
+
To enable Trend binary sensors in your installation, add the following to your configuration.yaml file:
The rpi platform allows you to integrate the Raspberry Pi camera into Home Assistant. This component uses the application raspistill to store the image from camera.
+
The rpi_camera platform allows you to integrate the Raspberry Pi camera into Home Assistant. This component uses the application raspistill to store the image from camera.
To enable this camera in your installation, add the following to your configuration.yaml file:
@@ -124,12 +124,6 @@
The given file_path must be an existing file because the camera platform setup make a writeable check on it.
-
Ensure that the user who is running Home Assistant is in the video group. Eg. for the user hass:
The honeywell cliamte platform let you control Honeywell Connected thermostats from Home Assistant.
+
The honeywell climate platform let you control Honeywell Connected thermostats from Home Assistant.
To set it up, add the following information to your configuration.yaml file:
diff --git a/components/cover.command_line/index.html b/components/cover.command_line/index.html
index 04613a2e95..ef0afb6bee 100644
--- a/components/cover.command_line/index.html
+++ b/components/cover.command_line/index.html
@@ -97,11 +97,11 @@
cover:-platform:command_linecovers:
- Garage door:
- opencmd:move_command up kitchen
- closecmd:move_command down kitchen
- stopcmd:move_command stop kitchen
- statecmd:state_command kitchen
+ garage_door:
+ command_open:move_command up garage
+ command_close:move_command down garage
+ command_stop:move_command stop garage
+ command_state:state_command garagevalue_template:>{% if value == 'open' %}100
@@ -117,13 +117,14 @@
covers (Required): The array that contains all command line covers.
-
entry (Required): Name of the command line cover. Multiple entries are possible.
+
identifier (Required): Name of the command line cover as slug. Multiple entries are possible.
-
opencmd (Required): The command to open the cover.
-
closecmd (Required): The action to close the cover.
-
stopcmd (Required): The action to stop the cover.
-
statecmd (Optional): If given, this will act as a sensor that runs in the background and updates the state of the cover. If the command returns a 0 the indicates the cover is fully closed, whereas a 100 indicates the cover is fully open.
-
value_template (optional - default: ‘{{ value }}’): if specified, statecmd will ignore the result code of the command but the template evaluating will indicate the position of the cover. For example, if your statecmd returns a string “open”, using value_template as in the example config above will allow you to translate that into the valid state 100.
+
command_open (Required): The command to open the cover.
+
command_close (Required): The action to close the cover.
+
command_stop (Required): The action to stop the cover.
+
command_state (Optional): If given, this will act as a sensor that runs in the background and updates the state of the cover. If the command returns a 0 the indicates the cover is fully closed, whereas a 100 indicates the cover is fully open.
+
value_template (optional - default: ‘{{ value }}’): if specified, command_state will ignore the result code of the command but the template evaluating will indicate the position of the cover. For example, if your command_state returns a string “open”, using value_template as in the example config above will allow you to translate that into the valid state 100.
+
friendly_name (Optional): The name used to display the cover in the frontend.
diff --git a/components/device_tracker.actiontec/index.html b/components/device_tracker.actiontec/index.html
index c87de7a55a..9c3de3f6f1 100644
--- a/components/device_tracker.actiontec/index.html
+++ b/components/device_tracker.actiontec/index.html
@@ -155,6 +155,9 @@ This device tracker needs telnet to be enabled on the router.
diff --git a/components/device_tracker.aruba/index.html b/components/device_tracker.aruba/index.html
index a77d3320d8..4214c67367 100644
--- a/components/device_tracker.aruba/index.html
+++ b/components/device_tracker.aruba/index.html
@@ -158,6 +158,9 @@ This device tracker needs telnet to be enabled on the router.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/device_tracker.bluetooth_le_tracker/index.html b/components/device_tracker.bluetooth_le_tracker/index.html
index 6d497e2e72..040341a5e3 100644
--- a/components/device_tracker.bluetooth_le_tracker/index.html
+++ b/components/device_tracker.bluetooth_le_tracker/index.html
@@ -148,6 +148,9 @@ Some BTLE devices (e.g. fitness trackers) are only visible to the devices that t
This tracker discovers new devices on boot and tracks bluetooth devices periodically based on interval_seconds value. It is not required to pair the devices with each other!
Devices discovered are stored with ‘bt_’ as the prefix for device mac addresses in known_devices.yaml.
-
-Requires PyBluez. If you are on Raspbian, make sure you first install bluetooth and libbluetooth-dev by running sudo apt install bluetooth libbluetooth-dev
-
-
To use the Bluetooth tracker in your installation, add the following to your configuration.yaml file:
device_tracker:
@@ -145,6 +141,9 @@ Requires PyBluez. If you are on Raspbian, make sure you first install Aruba
+
diff --git a/components/device_tracker.fritz/index.html b/components/device_tracker.fritz/index.html
index b5e4b4cfee..fd5c5a9416 100644
--- a/components/device_tracker.fritz/index.html
+++ b/components/device_tracker.fritz/index.html
@@ -156,6 +156,9 @@ It seems that it is not necessary to use it in current generation Fritz!Box rout
diff --git a/components/device_tracker.icloud/index.html b/components/device_tracker.icloud/index.html
index 3b5c598a2e..11385b6de8 100644
--- a/components/device_tracker.icloud/index.html
+++ b/components/device_tracker.icloud/index.html
@@ -158,6 +158,9 @@ If you have two-factor authentication enabled on your iCloud account you will no
diff --git a/components/device_tracker.luci/index.html b/components/device_tracker.luci/index.html
index 9e69dce39f..5c4db33d4a 100644
--- a/components/device_tracker.luci/index.html
+++ b/components/device_tracker.luci/index.html
@@ -157,6 +157,9 @@ Some installations have a s
max_gps_accuracy (Optional): Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account.
+
waypoints (Optional): Owntracks users can define waypoints (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is True, the Owntracks users who are in waypoint_whitelist can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to True.
+
waypoint_whitelist (Optional): A list of user names (as defined for Owntracks) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.
Using Owntracks with other device trackers
@@ -141,6 +147,13 @@
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.
+
Importing Owntracks waypoints as zones
+
By default, any Owntracks user connected to Home Assistant can export their waypoint definitions (from the Export - Export to Endpoint menu item) which will then be translated to zone definitions in Home Assistant. The zones will be named <user>-<device> - <waypoint name>. This functionality can be controlled in 2 ways:
+
+
+
The configuration variable waypoints can be set to False which will disable importing waypoints for all users.
+
The configuration variable waypoint_whitelist can contain a list of users who are allowed to import waypoints.
diff --git a/components/device_tracker.snmp/index.html b/components/device_tracker.snmp/index.html
index 828f2342cd..88defb78d1 100644
--- a/components/device_tracker.snmp/index.html
+++ b/components/device_tracker.snmp/index.html
@@ -168,6 +168,9 @@ This device tracker needs SNMP to be enabled on the router.
diff --git a/components/index.html b/components/index.html
index a8c51375d9..e694d4bcf5 100644
--- a/components/index.html
+++ b/components/index.html
@@ -103,7 +103,7 @@ Support for these components is provided by the Home Assistant community.
- All (399)
+ All (405)Featured
@@ -126,7 +126,7 @@ Support for these components is provided by the Home Assistant community.
Binary Sensor
- (23)
+ (24)
@@ -196,7 +196,7 @@ Support for these components is provided by the Home Assistant community.
Finance
- (3)
+ (4)
@@ -268,7 +268,7 @@ Support for these components is provided by the Home Assistant community.
Presence Detection
- (22)
+ (23)
@@ -282,7 +282,7 @@ Support for these components is provided by the Home Assistant community.
Social
- (4)
+ (5)
@@ -296,7 +296,7 @@ Support for these components is provided by the Home Assistant community.
System Monitor
- (9)
+ (11)
@@ -540,6 +540,20 @@ Support for these components is provided by the Home Assistant community.
+
+
# Example configuration.yaml entrymedia_player:platform:firetv
- host:localhost:5556
+ host:localhost
+ port:5556device:livingroom-firetvname:My Amazon Fire TV
@@ -132,13 +133,14 @@
Configuration variables:
-
host (Optional): Where firetv-server is running. Default is localhost:5556.
-
device (Optional): The device ID, default is default.
+
host (Optional): The host where firetv-server is running. Default is localhost.
+
port (Optional): The port where firetv-server is running. Default is 5556.
+
device (Optional): The device ID. Defaults to default.
name (Optional): The friendly name of the device, default is ‘Amazon Fire TV’.
-Note that python-firetv has support for multiple Amazon Fire TV devices. If you have more than one configured, be sure to specify the device id used. Run firetv-server -h and/or view the source for complete capabilities.
+Note that python-firetv has support for multiple Amazon Fire TV devices. If you have more than one configured, be sure to specify the device ID in device. Run firetv-server -h and/or view the source for complete capabilities.
@@ -158,6 +160,9 @@ Note that python-firetv has support for multiple Amazon Fire TV devices. If you
host (Required): The host name or address of the device that is running XBMC/Kodi
-
port (Required): The port number, default 8080
+
port (Optional): The port number. Defaults to 8080.
name (Optional): The name of the device used in the frontend.
username (Optional): The XBMC/Kodi HTTP username.
password (Optional): The XBMC/Kodi HTTP password.
diff --git a/components/media_player.mpchc/index.html b/components/media_player.mpchc/index.html
index 8b116bdfbb..3e81eda890 100644
--- a/components/media_player.mpchc/index.html
+++ b/components/media_player.mpchc/index.html
@@ -117,8 +117,8 @@ The MPC-HC web interface is highly insecure, and allows remote clients full play
Configuration variables:
-
host (Required): The host name or address of the device that is running MPC-HC
-
port (Required): The port number, default 13579
+
host (Required): The host name or address of the device that is running MPC-HC.
+
port (Optional): The port number. Defaults to 13579.
name (Optional): The name of the device used in the frontend.
@@ -139,7 +139,7 @@ The MPC-HC web interface is highly insecure, and allows remote clients full play
- Introduced in release: 0.25.0
+ Introduced in release: 0.25
This is a platform for
diff --git a/components/media_player.mpd/index.html b/components/media_player.mpd/index.html
index eb3c500b0d..c44c131dab 100644
--- a/components/media_player.mpd/index.html
+++ b/components/media_player.mpd/index.html
@@ -96,7 +96,7 @@
parity (Required): The parity for the serial connection.
+
Services
+
+
+
+
+
Service
+
Description
+
+
+
+
+
write_register
+
Write register. Requires unit, address and value fields. value can be either single value or an array
+
+
+
+
Building on top of Modbus
diff --git a/components/notify.file/index.html b/components/notify.file/index.html
index cc422e3d5b..758397940d 100644
--- a/components/notify.file/index.html
+++ b/components/notify.file/index.html
@@ -98,7 +98,7 @@
name:NOTIFIER_NAMEplatform:filefilename:FILENAME
- timestamp:1 or 0
+ timestamp:true or false
@@ -107,7 +107,7 @@
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.
filename (Required): Name of the file to use. The file will be created if it doesn’t exist and saved in your config/ folder.
-
timestamp (Optional): Setting timestamp to 1 adds a timestamp to every entry.
+
timestamp (Optional): Setting timestamp to True adds a timestamp to every entry.
diff --git a/components/notify.smtp/index.html b/components/notify.smtp/index.html
index c8ca59d389..4f1c71f9cd 100644
--- a/components/notify.smtp/index.html
+++ b/components/notify.smtp/index.html
@@ -100,7 +100,7 @@
server:MAIL_SERVERport:YOUR_SMTP_PORTsender:SENDER_EMAIL_ADDRESS
- starttls:1 or 0
+ starttls:true or falseusername:YOUR_SMTP_USERNAMEpassword:YOUR_SMTP_PASSWORDrecipient:YOUR_RECIPIENT
@@ -117,7 +117,8 @@
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. Defaults to 0.
+
starttls (Optional): Enables STARTTLS, eg. True or False. Defaults to False.
+
debug (Optional): Enables Debug, eg. True or False. Defaults to False.
To use the SMTP notification, refer to it in an automation or script like in this example:
The notification component supports specifying templates for both the message and the title. This will allow you to use the current state of Home Assistant in your notifications.
+
The notification component supports specifying templates with data_template. This will allow you to use the current state of Home Assistant in your notifications.
In an action of your automation setup it could look like this with a customized subject.
OctoPrint is a web interface for your 3D printer. This is the main component to integrate OctoPrint sensors, you will have to setup sensors and binary sensors separately.
-
To get started with the OctoPrint API, please follow the directions on their site. Once OctoPrint is configured you will need to add your API key and host to your configuration.yaml.
+
To get started with the OctoPrint API, please follow the directions on their site. Once OctoPrint is configured you will need to add your API key and host to your configuration.yaml.
diff --git a/components/sensor.fritzbox_callmonitor/index.html b/components/sensor.fritzbox_callmonitor/index.html
index e5a4c9d68e..8de9dc1d59 100644
--- a/components/sensor.fritzbox_callmonitor/index.html
+++ b/components/sensor.fritzbox_callmonitor/index.html
@@ -149,6 +149,12 @@ on TCP port 1012. It will assume the values idle
diff --git a/components/sensor.glances/index.html b/components/sensor.glances/index.html
index c3d6c012fc..03fbf9b4ed 100644
--- a/components/sensor.glances/index.html
+++ b/components/sensor.glances/index.html
@@ -198,6 +198,12 @@ Glances web server started on http://0.0.0.0:61208/
origin (Required): The stop ID of your origin station.
destination (Required): The stop ID of your destination station.
data (Required): The name of the ZIP file or folder containing the GTFS data. It must be located inside the gtfs folder of your configuration directory.
The linux_battery sensor platform is using the information stored in /sys/class/power_supply/ on your local Linux system to display details about the current state of your battery.
+
+
To setup a battery sensor to your installation, add the following to your configuration.yaml file:
name (Optional): Friendly name to use for the frontend. Default to “Battery”.
+
battery (Optional): Number of the battery. Default to 1.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/components/sensor.mfi/index.html b/components/sensor.mfi/index.html
index 2a64156e60..89f377af3a 100644
--- a/components/sensor.mfi/index.html
+++ b/components/sensor.mfi/index.html
@@ -100,8 +100,8 @@
port:PORTusername:USERNAMEpassword:PASSWORD
- use_tls:true
- verify_tls:true
+ ssl:true
+ verify_ssl:true
@@ -112,8 +112,8 @@
port (Optional): The port of your mFi controller. Defaults to 6443 for TLS, otherwise 6080.
username (Required): The mFi admin username.
password (Required): The mFi admin user’s password.
-
use_tls (Optional): If true, use TLS to contact the mFi controller. Defaults to true.
-
verify_tls (Optional): Set this to false if your mFi controller has a self-signed certificate. Defaults to true.
+
ssl (Optional): If True, use SSL/TLS to contact the mFi controller. Defaults to True.
+
verify_ssl (Optional): Set this to False if your mFi controller has a self-signed certificate. Defaults to True.
diff --git a/components/sensor.mqtt_room/index.html b/components/sensor.mqtt_room/index.html
index 69332a9b7a..78ae60b836 100644
--- a/components/sensor.mqtt_room/index.html
+++ b/components/sensor.mqtt_room/index.html
@@ -166,6 +166,9 @@ Instead of developing your own application, you can also use any of these alread
name (Optional): The name of the sensor. Default is ‘OctoPrint’.
monitored_conditions array (Required): States to monitor.
-
Current State (Text of current state)
-
Temperatures (Temperatures of all available tools)(print head, print bed, …) These will be displayed as tool0, tool1, … please refer to your OctoPrint frontend to associate tool number with actual device.
-
Job Percentage
+
Current State: Text of current state)
+
Temperatures: Temperatures of all available tools, eg. print, head, print bed, etc. These will be displayed as tool0, tool1, or toolN please refer to your OctoPrint frontend to associate the tool number with an actual device.
The speedtest sensor component uses the Speedtest.net web service to measure network bandwidth performance.
-
By default, it will run every hour. The user can change the update frequency in the config by defining the minute, hour, and day for a speedtest to run.
+
By default, it will run every hour. The user can change the update frequency in the configuration by defining the minute, hour, and day for a speedtest to run. For the server_id check the list of available servers.
To add a Speedtest.net sensor to your installation, add the following to your configuration.yaml file:
# Example configuration.yaml entrysensor:platform:temper
+ name:'MyTEMPer'
+ scale:1
+ offset:0
+
Since some of these sensors consistently show higher temperatures the scale and offset values can be used to fine-tune your sensor.
+The calculation follows the formula scale * sensor value + offset.
+
+
The TEMPer sensors can only be accessed as root by default. To fix the USB permissions on your system create the file /etc/udev/rules.d/99-tempsensor.rules and add the following line to it:
The wunderground platform uses Weather Underground as an source for current weather information.
+
The wunderground platform uses Weather Underground as a source for current weather information.
-Obtain WUnderground API here. Free account allows 500 requests per day or 10 per minute.
+Obtain a WUnderground API key here. A free account allows 500 requests per day or 10 per minute.
To add Wunderground to your installation, add the following to your configuration.yaml file:
@@ -137,21 +137,21 @@ Obtain WUnderground API here<
pws_id (Optional): You can enter a Personal Weather Station id. The current list of Wunderground PWS stations is available here. If you do not enter a PWS ID, the current location information (latitude and longitude) from your configuration.yaml will be used to display weather conditions.
monitored_conditions array (Required): Conditions to display in the frontend. The following conditions can be monitored.
weather: A human-readable text summary with picture from Wunderground.
temp_f: Current temperature in Fahrenheit
temp_c: Current temperature in Celsius
station_id: Your personal weather station (PWS) ID
-
feelslike_c: Feels like (or apparent) temperature in celsius
+
feelslike_c: Feels like (or apparent) temperature in Celsius
feelslike_f: Feels like (or apparent) temperature in Fahrenheit
-
feelslike_string: Text summary of how the current teperature feels like
+
feelslike_string: Text summary of how the current temperature feels like
heat_index_c: Heat index (combined effects of the temperature and humidity of the air) in Celsius
heat_index_f: Heat index (combined effects of the temperature and humidity of the air) in Fahrenheit
heat_index_string: Text summary of current heat index
-
dewpoint_c: Temperature in celsius below which water droplets begin to condense and dew can form
-
dewpoint_f: Temperature in fahrenheit below which water droplets begin to condense and dew can form
+
dewpoint_c: Temperature in Celsius below which water droplets begin to condense and dew can form
+
dewpoint_f: Temperature in Fahrenheit below which water droplets begin to condense and dew can form
The Xbox Live component is able to track Xbox profiles.
+
+
To use this sensor you need a free API key from XboxAPI.com.
+Please also make sure to connect your Xbox account on that site.
+
+
The configuration requires you to specify XUIDs which are the unique identifiers for profiles.
+These can be determined on XboxAPI.com by either looking at your own profile page or using their interactive documentation to search for gamertags.
+
+
To use the Xbox Live sensor in your installation, add the following to your configuration.yaml file:
diff --git a/components/switch.command_line/index.html b/components/switch.command_line/index.html
index 0072aff21f..12802f6c55 100644
--- a/components/switch.command_line/index.html
+++ b/components/switch.command_line/index.html
@@ -98,10 +98,11 @@
platform:command_lineswitches:kitchen_light:
- oncmd:switch_command on kitchen
- offcmd:switch_command off kitchen
- statecmd:query_command kitchen
+ command_on:switch_command on kitchen
+ command_off:switch_command off kitchen
+ command_state:query_command kitchenvalue_template:'{{value=="online"}}'
+ friendly_name:Kitchen switch
@@ -110,12 +111,13 @@
switches (Required): The array that contains all command switches.
-
entry (Required): Name of the command switch. Multiple entries are possible.
+
identifier (Required): Name of the command switch as slug. Multiple entries are possible.
-
oncmd (Required): The action to take for on.
-
offcmd (Required): The action to take for off.
-
statecmd (Optional): If given, this command will be run. Returning a result code 0 will indicate that the switch is on.
-
value_template (Optional): If specified, statecmd will ignore the result code of the command but the template evaluating to true will indicate the switch is on.
+
command_on (Required): The action to take for on.
+
command_off (Required): The action to take for off.
+
command_state (Optional): If given, this command will be run. Returning a result code 0 will indicate that the switch is on.
+
value_template (Optional): If specified, command_state will ignore the result code of the command but the template evaluating to true will indicate the switch is on.
+
friendly_name (Optional): The name used to display the switch in the frontend.
@@ -135,8 +137,8 @@
platform:command_lineswitches:arest_pin4:
- oncmd:"/usr/bin/curl-XGEThttp://192.168.1.10/digital/4/1"
- offcmd:"/usr/bin/curl-XGEThttp://192.168.1.10/digital/4/0"
+ command_on:"/usr/bin/curl-XGEThttp://192.168.1.10/digital/4/1"
+ command_off:"/usr/bin/curl-XGEThttp://192.168.1.10/digital/4/0"
@@ -153,7 +155,7 @@ This switch will shutdown your host immediately, there will be no confirmation.
platform:command_lineswitches:Home Assistant system shutdown:
- offcmd:"/usr/sbin/poweroff"
+ command_off:"/usr/sbin/poweroff"
@@ -166,8 +168,8 @@ This switch will shutdown your host immediately, there will be no confirmation.
platform:command_lineswitches:VLC:
- oncmd:"cvlc1.mp3vlc://quit&"
- offcmd:"pkillvlc"
+ command_on:"cvlc1.mp3vlc://quit&"
+ command_off:"pkillvlc"
@@ -180,9 +182,9 @@ This switch will shutdown your host immediately, there will be no confirmation.
platform:command_lineswitches:foscam_motion:
- oncmd:'curl-k"https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=1&usr=admin&pwd=password"'
- offcmd:'curl-k"https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=0&usr=admin&pwd=password"'
- statecmd:'curl-k--silent"https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=getMotionDetectConfig&usr=admin&pwd=password"|grep-oP"(?<=isEnable>).*?(?=</isEnable>)"'
+ command_on:'curl-k"https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=1&usr=admin&pwd=password"'
+ command_off:'curl-k"https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=setMotionDetectConfig&isEnable=0&usr=admin&pwd=password"'
+ command_state:'curl-k--silent"https://ipaddress:443/cgi-bin/CGIProxy.fcgi?cmd=getMotionDetectConfig&usr=admin&pwd=password"|grep-oP"(?<=isEnable>).*?(?=</isEnable>)"'value_template:'{{value=="1"}}'
diff --git a/components/switch.dlink/index.html b/components/switch.dlink/index.html
index d5a664778c..d42c65ffac 100644
--- a/components/switch.dlink/index.html
+++ b/components/switch.dlink/index.html
@@ -107,6 +107,7 @@
name:D-Link plugusername:YOUR_USERNAMEpassword:YOUR_PASSWORD
+ use_legacy_protocol:False
@@ -117,6 +118,7 @@
name (Optional): The name to use when displaying this switch.
username (Required): The username for your plug. Defaults to admin.
password (Required): The password for your plug. Default password is the PIN inlcuded on the configuration card.
+
use_legacy_protocol (Optional): Enable limited support for legacy firmware protocols (Tested with v1.24).
host (Required): IP address of your switch, eg. 192.168.1.10.
-
mac (Optional): MAC address of the switch, eg “AA:BB:CC:DD:EE:FF”. This is required if the switch is connected to a different subnet to the machine running Home Assistant
+
discovery (Optional): Whether to discover sockets (default true).
+
switches (Optional):
+
+
host (Required): IP address of your socket, eg. 192.168.1.10.
+
mac (Optional): MAC address of the socket, eg “AA:BB:CC:DD:EE:FF”. This is required if the socket is connected to a different subnet to the machine running Home Assistant
Assume that you have an enocean wall switch and some Philips Hue lamps. The enocean wall swtich will fire the event button_pressed and pass along several parameters which is used to turn on/off the lamps.
diff --git a/cookbook/foscam_away_mode_PTZ/index.html b/cookbook/foscam_away_mode_PTZ/index.html
index c8042cf272..3c28f02778 100644
--- a/cookbook/foscam_away_mode_PTZ/index.html
+++ b/cookbook/foscam_away_mode_PTZ/index.html
@@ -211,6 +211,9 @@ The following outlines examples of the switch, services, and scripts required to
Components that interact with devices are called “Entity Components”. They are structured in core- and platform logic. This allows the same logic to handle a light to be used by different brands.
+
Components that interact with devices are called “Entity Components”. They are structured in core- and platform logic. This allows the same logic to handle a light to be used by different brands.
For example, the built-in switch component consists of various platforms in homeassistant/components/switch/. The file __init__.py contains the core logic of all platform and the vendor_name.py files only the relevant platform code.
@@ -104,11 +104,11 @@
One of the rules for Home Assistant is that platform logic should never interface directly with devices but use a third-party Python 3 library to do so. This way Home Assistant is able to share code with the Python community and we can keep the project maintainable.
-
To integrate the third-party library you create an Entity class for your device. Entities are Home Assistant’s representation of lights, switches, sensors, etc. and are derived from the Entity Abstract Class. This abstract class contains logic for integrating most standard features into your entities, such as visibility, entity IDs, updates, and much more.
+
To integrate the third-party library you create an Entity class for your device. Entities are Home Assistant’s representation of lights, switches, sensors, etc. and are derived from the Entity Abstract Class. This abstract class contains logic for integrating most standard features into your entities, such as visibility, entity IDs, updates, and much more.
Requirements and dependencies
-
Platforms can specify dependencies and requirements the same way as a component does.
diff --git a/developers/architecture_components/index.html b/developers/architecture_components/index.html
index 17cc5d102c..88263fa25e 100644
--- a/developers/architecture_components/index.html
+++ b/developers/architecture_components/index.html
@@ -102,7 +102,7 @@ Diagram showing interaction between components and the Home Assistant core.
These components will track devices within a specific domain and consist of a core part and platform-specific logic. These components make their information available via the State Machine and the Event Bus. The component will also register services in the Service Registry to expose control of the devices.
-
For example, one of the built-in components is the switch component. This component is responsible for interaction with different types of switches.
+
For example, one of the built-in components is the switch component. This component is responsible for interaction with different types of switches.
A platform provides support for a particular kind/brand of device. For example, a switch could use a WeMo or Orvibo platform, and a light component might interact with the Hue or LiFX platform.
@@ -210,6 +210,7 @@ Diagram showing interaction between components and the Home Assistant core.
diff --git a/developers/component_discovery/index.html b/developers/component_discovery/index.html
index cbf4aebe21..5c472b4a51 100644
--- a/developers/component_discovery/index.html
+++ b/developers/component_discovery/index.html
@@ -189,6 +189,7 @@ This option is only available to built-in components.
diff --git a/developers/component_generic_discovery/index.html b/developers/component_generic_discovery/index.html
index 8b7d8ad3ac..9078d001b5 100644
--- a/developers/component_generic_discovery/index.html
+++ b/developers/component_generic_discovery/index.html
@@ -227,6 +227,7 @@ In the past, this was achieved by adding your component to the Austin
diff --git a/developers/development_environment/index.html b/developers/development_environment/index.html
index f4777659af..462231c5ff 100644
--- a/developers/development_environment/index.html
+++ b/developers/development_environment/index.html
@@ -179,6 +179,7 @@ If you are using Windows as a development platform ensure you have the correct M
diff --git a/developers/frontend/index.html b/developers/frontend/index.html
index 678174c60e..6976b87f6a 100644
--- a/developers/frontend/index.html
+++ b/developers/frontend/index.html
@@ -221,6 +221,7 @@ Do not use development mode in production. Home Assistant uses aggressive cachin
diff --git a/developers/index.html b/developers/index.html
index 898e4d7fc1..4444ee30c5 100644
--- a/developers/index.html
+++ b/developers/index.html
@@ -162,6 +162,7 @@ Diagram showing interaction between components and the Home Assistant core.
diff --git a/developers/multiple_instances/index.html b/developers/multiple_instances/index.html
index 0487d5aceb..a65087f390 100644
--- a/developers/multiple_instances/index.html
+++ b/developers/multiple_instances/index.html
@@ -188,6 +188,7 @@ Because each slave maintains its own Service Registry it is possible to have mul
diff --git a/developers/rest_api/index.html b/developers/rest_api/index.html
index 994f35646a..438c8aa857 100644
--- a/developers/rest_api/index.html
+++ b/developers/rest_api/index.html
@@ -638,6 +638,7 @@ If your client does not support DELETE HTTP requests you can add an
diff --git a/getting-started/installation-raspberry-pi/index.html b/getting-started/installation-raspberry-pi/index.html
index c802217cd9..a6bd1707e5 100644
--- a/getting-started/installation-raspberry-pi/index.html
+++ b/getting-started/installation-raspberry-pi/index.html
@@ -7,26 +7,26 @@
- Installation on a Raspberry Pi - Home Assistant
+ Raspbian Lite on a Raspberry Pi - Home Assistant
-
+
-
+
-
+
-
-
+
+
@@ -83,29 +83,147 @@
- Installation on a Raspberry Pi
+ Raspbian Lite on a Raspberry Pi
-
Home Assistant requires the Raspberry Pi to run Raspbian Jessie. This version was released on September 24, 2015 and comes by default with Python 3.4 which is required for Home Assistant.
+
Installation
-
Execute the following code in a console:
+
This installation of Home Assistant requires the Raspberry Pi to run Raspbian Lite.
+The installation will be installed in a Virtual Environment with minimal overhead. Instructions assume this is a new installation of Raspbian Lite.
-
$ sudo pip3 install homeassistant
-$ hass
+
Connect to the Raspberry Pi over ssh. Default password is raspberry.
Add an account for Home Assistant called homeassistant.
+Since this account is only for running Home Assistant the extra arguments of -rm is added to create a system account and create a home directory.
+
$ sudo useradd -rm homeassistant
+
+
+
+
Next we will create a directory for the installation of Home Assistant and change the owner to the homeassistant account.
Start Home Assistant for the first time. This will complete the installation, create the .homeasssistant configuration directory in the /home/homeassistant directory and install any basic dependencies.
+
(homeassistant_venv)$ hass
+
+
+
+
You can now reach your installation on your raspberry pi over the web interface on http://ipaddress:8123.
+For instruction on how to configure Home Assistant continue on with Configuring Home Assistant.
+
+
Raspberry Pi Hardware Specific Components
+
+
Some components that are specific for the Raspberry Pi can require some further configuration outside of Home Assistant. All commands below are assumed to be executed with the pi account. For full documentation of these components refer to the components page.
+
+
Bluetooth Tracker
+
The Bluetooth tracker will work on a Raspberry Pi 3 with the built-in Bluetooth module or with a USB Bluetooth device on any of the other Raspberry Pi’s.
+
+
Install the following external dependencies.
+
$ sudo apt-get install bluetooth libbluetooth-dev
+
The Raspberry Pi Camera is a specific camera for the Raspberry Pi boards. For more information about the camera I suggest reading the documentation from the Raspberry Pi foundation.
+
+
To use the camera it needs to be enabled with the raspi-config utility.
+
$ sudo raspi-config
+
+
+
Select Enable camera choose <Yes> and hit Enter, then go to Finish and you’ll be prompted to reboot.
+After reboot add your homeassistant account to the video group.
Each of the following devices are connected to the GPIO pins on the Raspberry Pi.
+For more details about the GPIO layout, visit the documentation from the Raspberry
+Pi foundation.
+Since these are not normally used some extra permission will need to be added.
+In general the permission that is needed is granted by adding the homeassistant account to the gpio group.
The One wire sensor requires that support for it is enabled on the Raspberry Pi and that the One Wire device is connected to GPIO pin 4.
+To enable One Wire support add the following line to the end of /boot/config.txt
diff --git a/getting-started/z-wave/index.html b/getting-started/z-wave/index.html
index 936b736261..a518a9fb95 100644
--- a/getting-started/z-wave/index.html
+++ b/getting-started/z-wave/index.html
@@ -170,6 +170,12 @@ Instead of make install, you can alternat
+
Or, on macOS, use:
+
+
$ ls /dev/cu.usbmodem*
+
+
+
Depending on what’s plugged into your USB ports, the name found above may change. You can lock in a name, such as /dev/zwave, by following these instructions.
There is not currently a site search for Home-Assistant.io but it’s in the works. For now, you can use this Google link which will narrow your search to this specific site.
+
Roadmap
There is no explicit roadmap available but the public tracker can give you some insight into what is going on.
diff --git a/images/screenshots/automation-switches.png b/images/screenshots/automation-switches.png
new file mode 100644
index 0000000000..7f43b85660
Binary files /dev/null and b/images/screenshots/automation-switches.png differ
diff --git a/images/supported_brands/automatic.png b/images/supported_brands/automatic.png
new file mode 100644
index 0000000000..6f7382bc6e
Binary files /dev/null and b/images/supported_brands/automatic.png differ
diff --git a/images/supported_brands/pi_hole.png b/images/supported_brands/pi_hole.png
new file mode 100644
index 0000000000..7d2c70b3c1
Binary files /dev/null and b/images/supported_brands/pi_hole.png differ
diff --git a/images/supported_brands/xbox-live.png b/images/supported_brands/xbox-live.png
new file mode 100644
index 0000000000..f606acd982
Binary files /dev/null and b/images/supported_brands/xbox-live.png differ
diff --git a/index.html b/index.html
index b238929efa..780309805d 100644
--- a/index.html
+++ b/index.html
@@ -115,11 +115,11 @@ Home Assistant is an open-source home automation platform running on Python 3. T
ESP8266 and MicroPython - Part 2
August 31, 2016
@@ -148,11 +153,6 @@ Home Assistant is an open-source home automation platform running on Python 3. T
August 27, 2016
diff --git a/topics/templating/index.html b/topics/templating/index.html
index 335b5cff4d..3968db070b 100644
--- a/topics/templating/index.html
+++ b/topics/templating/index.html
@@ -119,7 +119,7 @@ The frontend has a template editor developer tool to help develop and debug temp
msg_who_is_home:sequence:-service:notify.notify
- data:
+ data_template:message:>{% if is_state('device_tracker.paulus', 'home') %}Ha, Paulus is home!
@@ -158,6 +158,7 @@ The frontend has a template editor developer tool to help develop and debug temp
Filter round(x) will convert the input to a number and round it to x decimals.
Filter timestamp_local will convert an UNIX timestamp to local time/data.
Filter timestamp_utc will convert an UNIX timestamp to UTC time/data.
+
Filter timestamp_custom(format_string, local_boolean) will convert an UNIX timestamp to a custom format, the use of a local timestamp is default, supporting Python format options.
+
- Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
-
-
-
-
-
+ 
+
-
-- Support for [Envisalink] added ([alarm control panel][envi-alarm], [binary sensor][envi-binary-sensor], [sensor][envi-sensor]) ([@cinntax])
-- Support for [Homematic] added ([binary sensor][hm-binary-sensor], [light][hm-light], [rollershutter][hm-rollershutter], [sensor][hm-sensor], [switch][hm-switch]) ([@pvizeli], [@danielperna84])
-- New [HDMI-CEC] component ([@happyleavesaoc], [@lukas-hetzenecker])
-- Major rewrite of [Wink] which now pushes changes to Home Assistant ([@w1ll1am23])
-- Core: new add [reload core config service] ([@balloob])
-- Support for [persistent notifications] added ([@fabaff], [@balloob])
-- Garage door: [Z-Wave][zwave-garage-door] support added ([@turbokongen])
-- Rollershutter: [Z-Wave][zwave-rollershutter] support added ([@turbokongen])
-- Media Player: [Sony Bravia TV] now supported ([@aparraga])
-- Sensor: [Fixer.io] now supported ([@fabaff])
-- Garage door: Control any garage door using [Raspberry Pi GPIO pins] ([@kellerza])
-- Sensor: [OpenExchangeRates] support added ([@arsaboo])
-- Notify: [Pushover] now supports target device, sound, url and priority ([@dale3h])
-- Sensor: [Netatmo] now supports wind, battery and radio signals ([@Jypy])
-- Log successful and failed login attemps ([@fabaff])
-- Config: allow [extracting account info][secrets] into OS keyring or separate YAML file ([@kellerza])
-- Core: add option to not filter out duplicate states per entity ([@philipbl])
-- HTTP: Follow Mozilla SSL recommendations ([@danieljkemp], [@AlucardZero])
-- Light: [Z-Wave colorbulb][zwave-light] support added ([@armills])
-- Core: new elevation config option added ([@balloob])
-- Sensor: [OneWire] support extended with support for DS18S20, DS1822, DS1825 and DS28EA00 temperature sensors + support for bus masters which use fuse to mount device tree. ([@Ardetus])
-- Lock: [Vera] now supported ([@rhooper])
-- HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems ([@balloob])
-
-### 
-One of the graphs created with this tutorial.
-
- Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
-
-
-
-
I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. 
- A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
-
+
+ 
-