Site updated at 2016-07-24 17:39:50 UTC
This commit is contained in:
Travis CI
parent
2d9a218a1b
commit
29118ce15d
1007 changed files with 168343 additions and 140 deletions
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Community | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/community/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -20,11 +20,11 @@
|
|||
<id>https://home-assistant.io/blog/2016/06/01/community-highlights</id>
|
||||
<content type="html"><![CDATA[<p>Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our <a href="https://gitter.im/home-assistant/home-assistant">chat room</a> and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.</p>
|
||||
|
||||
<h3>{% linkable_title SceneGen - cli for making scenes %}</h3>
|
||||
<h3><a class='title-link' name='scenegen---cli-for-making-scenes' href='#scenegen---cli-for-making-scenes'></a> SceneGen - cli for making scenes </h3>
|
||||
|
||||
<p><a href="https://github.com/acockburn/scenegen">SceneGen</a> is a new command line utility developed by <a href="https://github.com/acockburn">Andrew Cockburn</a> that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.</p>
|
||||
|
||||
<h3>{% linkable_title Videos %}</h3>
|
||||
<h3><a class='title-link' name='videos' href='#videos'></a> Videos </h3>
|
||||
|
||||
<p><a href="https://partofthething.com">Nick Touran</a> has been working on integrating IR remotes with Home Assistant. He made it into a component which should be available in the next release which should arrive in a couple of days. In the meanwhile, he wrote up <a href="https://partofthething.com/thoughts/?p=1010">a blog post</a> and has put out a video showing the new integration, very cool!</p>
|
||||
|
||||
|
|
@ -54,13 +54,13 @@
|
|||
<id>https://home-assistant.io/blog/2016/02/20/community-highlights</id>
|
||||
<content type="html"><![CDATA[<p>Home Assistant land has been busy and a lot of people have been creating awesome stuff. We’ve added <a href="/cookbook/">a cookbook section</a> to the website full of examples how you can automate different things. Make sure you take a look and share your own recipes too!</p>
|
||||
|
||||
<h3>{% linkable_title Home automation demo by Part of the Thing %}</h3>
|
||||
<h3><a class='title-link' name='home-automation-demo-by-part-of-the-thing' href='#home-automation-demo-by-part-of-the-thing'></a> Home automation demo by Part of the Thing </h3>
|
||||
|
||||
<div class="videoWrapper">
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/Mc_29EC3aZw" frameborder="0" allowfullscreen=""></iframe>
|
||||
</div>
|
||||
|
||||
<h3>{% linkable_title Haaska - Alexa Skill Adapter for Home Assistant %}</h3>
|
||||
<h3><a class='title-link' name='haaska---alexa-skill-adapter-for-home-assistant' href='#haaska---alexa-skill-adapter-for-home-assistant'></a> Haaska - Alexa Skill Adapter for Home Assistant </h3>
|
||||
|
||||
<p>Haaska allows you to control lights, switches, and scenes exposed by your Home Assistant instance using an Amazon Echo. This is different from our own <a href="/components/alexa/">Alexa</a> component because it will teach the Amazon Echo directly about the devices instead of teaching it to talk to Home Assistant. It will not allow you to use custom sentences but it will allow you to skip the ‘Ask Home Assistant’ part when giving commands:</p>
|
||||
|
||||
|
|
@ -72,7 +72,7 @@
|
|||
|
||||
<p><a href="https://github.com/auchter/haaska">Haaska on GitHub</a></p>
|
||||
|
||||
<h3>{% linkable_title Integrating Home Assistant with HomeKit %}</h3>
|
||||
<h3><a class='title-link' name='integrating-home-assistant-with-homekit' href='#integrating-home-assistant-with-homekit'></a> Integrating Home Assistant with HomeKit </h3>
|
||||
|
||||
<p>Contributor Maddox has created a plugin for HomeBridge, an open-source HomeKit bridge. This will allow you to control your home using Siri on your Apple devices. HomeBridge has recently restructured so you’ll have to install the plugin separately with the homebridge-homeassistant npm package.</p>
|
||||
|
||||
|
|
@ -95,7 +95,7 @@
|
|||
<p><a href="https://github.com/nfarina/homebridge">HomeBridge on GitHub</a><br />
|
||||
<a href="https://github.com/maddox/homebridge-homeassistant">HomeBridge Home Assistant Plugin</a></p>
|
||||
|
||||
<h3>{% linkable_title Custom alarm system with Home Assistant %}</h3>
|
||||
<h3><a class='title-link' name='custom-alarm-system-with-home-assistant' href='#custom-alarm-system-with-home-assistant'></a> Custom alarm system with Home Assistant </h3>
|
||||
|
||||
<p>User thaijames <a href="https://community.home-assistant.io/t/controlling-house-alarm-from-ha/67">describes in the Home Assistant forums</a> how he has created his own NFC-based alarm system using Home Assistant, DIY components and Garfield dolls.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Device-Tracking | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/device-tracking/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
|
||||
<p>In <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better">Part 1</a> 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.</p>
|
||||
|
||||
<h3>{% linkable_title Tracking things using iBeacons %}</h3>
|
||||
<h3><a class='title-link' name='tracking-things-using-ibeacons' href='#tracking-things-using-ibeacons'></a> Tracking things using iBeacons </h3>
|
||||
<p>In the first part I mentioned that iBeacons just send out <em>I’m here</em> packets, and we used this to trigger an update when your phone came close to a fixed beacon.</p>
|
||||
|
||||
<p>But beacons don’t have to be fixed.</p>
|
||||
|
|
@ -90,10 +90,10 @@
|
|||
- <span class="string"><span class="content">alias: 'Forgotten keys'</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}'</span></span>
|
||||
<span class="key">condition</span>:
|
||||
<span class="key">condition</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{ states.device_tracker.greg_gregphone.state != "home" }}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{ states.device_tracker.greg_gregphone.state != "home" }}'</span></span>
|
||||
<span class="key">action</span>:
|
||||
<span class="key">service</span>: <span class="string"><span class="content">script.turn_on</span></span>
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">script.send_key_alert</span></span>
|
||||
|
|
@ -101,7 +101,7 @@
|
|||
- <span class="string"><span class="content">alias: 'Forgotten keys - cancel'</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state}}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state}}'</span></span>
|
||||
<span class="key">condition</span>:
|
||||
- <span class="string"><span class="content">condition: state</span></span>
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">script.send_key_alert</span></span>
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
1. 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<br />
|
||||
2. 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)</p>
|
||||
|
||||
<h3>{% linkable_title Using both types of iBeacons at the same time %}</h3>
|
||||
<h3><a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time </h3>
|
||||
<p>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.</p>
|
||||
|
||||
<p class="img">
|
||||
|
|
@ -144,7 +144,7 @@
|
|||
</p>
|
||||
<p>Waterproof beacon</p>
|
||||
|
||||
<h3>{% linkable_title Buying Beacons %}</h3>
|
||||
<h3><a class='title-link' name='buying-beacons' href='#buying-beacons'></a> Buying Beacons </h3>
|
||||
<p>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.</p>
|
||||
|
||||
<p>I’ve bought quite a few iBeacons from a company called <a href="http://bluesensenetworks.com/">Blue Sense Networks</a>. 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.</p>
|
||||
|
|
@ -157,12 +157,12 @@
|
|||
|
||||
<p>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!</p>
|
||||
|
||||
<h3>{% linkable_title Conclusion %}</h3>
|
||||
<h3><a class='title-link' name='conclusion' href='#conclusion'></a> Conclusion </h3>
|
||||
<p>As I said in <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better">part 1</a>, 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.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<h3>{% linkable_title Notes %}</h3>
|
||||
<h3><a class='title-link' name='notes' href='#notes'></a> Notes </h3>
|
||||
|
||||
<p>Please see the <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/#tips">notes at the end of Part 1</a> for documentation information.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: ESP8266 | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/esp8266/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -35,7 +35,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Components %}</h3>
|
||||
<h3><a class='title-link' name='components' href='#components'></a> Components </h3>
|
||||
|
||||
<p>I’ve been using Adafruit for my shopping:</p>
|
||||
|
||||
|
|
@ -47,7 +47,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
|
||||
<p><em>Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires, soldering iron + wire, Serial USB cable.</em></p>
|
||||
|
||||
<h3>{% linkable_title Alternatives %}</h3>
|
||||
<h3><a class='title-link' name='alternatives' href='#alternatives'></a> Alternatives </h3>
|
||||
|
||||
<p>Since this article has been published the HDC1008 has been discontinued. Updated sketches are available for the following alternatives:</p>
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
<li><a href="https://www.adafruit.com/product/2652">BME280 sensor</a> and <a href="https://gist.github.com/mtl010957/9ee85fb404f65e15c440b08c659c0419">updated sketch</a>.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Connections %}</h3>
|
||||
<h3><a class='title-link' name='connections' href='#connections'></a> Connections </h3>
|
||||
|
||||
<p>On your breadboard, make the following connections from your ESP8266 to the HDC1008:</p>
|
||||
|
||||
|
|
@ -89,7 +89,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
|
||||
<p><em>I picked <code>#2</code> and <code>14</code> myself, you can configure them in the sketch.</em></p>
|
||||
|
||||
<h3>{% linkable_title Preparing your IDE %}</h3>
|
||||
<h3><a class='title-link' name='preparing-your-ide' href='#preparing-your-ide'></a> Preparing your IDE </h3>
|
||||
|
||||
<p>Follow <a href="https://github.com/esp8266/Arduino#installing-with-boards-manager">these instructions</a> on how to install and prepare the Arduino IDE for ESP8266 development.</p>
|
||||
|
||||
|
|
@ -100,7 +100,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
<li>Adafruit HDC1000</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Sketch %}</h3>
|
||||
<h3><a class='title-link' name='sketch' href='#sketch'></a> Sketch </h3>
|
||||
|
||||
<p>If you have followed the previous steps, you’re all set.</p>
|
||||
|
||||
|
|
@ -344,7 +344,7 @@ Adafruit_HDC1000 hdc = Adafruit_HDC1000();
|
|||
</tr></table>
|
||||
</div>
|
||||
|
||||
<h3>{% linkable_title Configuring Home Assistant %}</h3>
|
||||
<h3><a class='title-link' name='configuring-home-assistant' href='#configuring-home-assistant'></a> Configuring Home Assistant </h3>
|
||||
|
||||
<p>The last step is to integrate the sensor values into Home Assistant. This can be done by setting up Home Assistant to connect to the MQTT broker and subscribe to the sensor topics.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: How-To | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/how-to/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -39,7 +39,7 @@ One of the graphs created with this tutorial.
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Dependencies %}</h3>
|
||||
<h3><a class='title-link' name='dependencies' href='#dependencies'></a> Dependencies </h3>
|
||||
|
||||
<p>In order to run the provided Jupyter notebook, please make sure you have the following applications/libraries installed on your computer:</p>
|
||||
|
||||
|
|
@ -53,11 +53,11 @@ One of the graphs created with this tutorial.
|
|||
|
||||
<p>As a Windows user myself, I find the easiest, quickest and most hassle-free way of installing all of these dependencies is to use <a href="https://winpython.github.io/">WinPython</a>. This free open-source portable distribution includes all of the dependencies required for this notebook, as well as a few other essential Python libraries you may require for data exploration in the future.</p>
|
||||
|
||||
<h4>{% linkable_title Why Jupyter? %}</h4>
|
||||
<h4><a class='title-link' name='why-jupyter' href='#why-jupyter'></a> Why Jupyter? </h4>
|
||||
|
||||
<p>While all Home Assistant implementations can have varying setup, components and scripts, the underlying data structure is standardized and well-defined. This allows us to write Python code that is environmentally agnostic. Wrapping it in a Jupyter notebook ensures the code, visualizations and directions/explanations are kept digestible and neatly-packaged. One of the amazing features of Jupyter is the ability to change code as you go along, customizing all outputs and visualizations on the fly!</p>
|
||||
|
||||
<h4>{% linkable_title Where do I start? %}</h4>
|
||||
<h4><a class='title-link' name='where-do-i-start' href='#where-do-i-start'></a> Where do I start? </h4>
|
||||
|
||||
<p>This tutorial is based around a heavily commented Jupyter Notebook that we created. So to get started, you will have to open that:</p>
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ One of the graphs created with this tutorial.
|
|||
One of the graphs created with this tutorial.
|
||||
</p>
|
||||
|
||||
<h4>{% linkable_title What’s next? %}</h4>
|
||||
<h4><a class='title-link' name='whats-next' href='#whats-next'></a> What’s next? </h4>
|
||||
|
||||
<p>Thanks to the magic of Jupyter, all of the code is customizable: want to selectively display your data, only covering a specific entity? Sure thing! Want to change the properties of the plots? No problem!</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: iBeacons | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/ibeacons/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
|
||||
<p>In <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better">Part 1</a> 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.</p>
|
||||
|
||||
<h3>{% linkable_title Tracking things using iBeacons %}</h3>
|
||||
<h3><a class='title-link' name='tracking-things-using-ibeacons' href='#tracking-things-using-ibeacons'></a> Tracking things using iBeacons </h3>
|
||||
<p>In the first part I mentioned that iBeacons just send out <em>I’m here</em> packets, and we used this to trigger an update when your phone came close to a fixed beacon.</p>
|
||||
|
||||
<p>But beacons don’t have to be fixed.</p>
|
||||
|
|
@ -90,10 +90,10 @@
|
|||
- <span class="string"><span class="content">alias: 'Forgotten keys'</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}'</span></span>
|
||||
<span class="key">condition</span>:
|
||||
<span class="key">condition</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{ states.device_tracker.greg_gregphone.state != "home" }}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{ states.device_tracker.greg_gregphone.state != "home" }}'</span></span>
|
||||
<span class="key">action</span>:
|
||||
<span class="key">service</span>: <span class="string"><span class="content">script.turn_on</span></span>
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">script.send_key_alert</span></span>
|
||||
|
|
@ -101,7 +101,7 @@
|
|||
- <span class="string"><span class="content">alias: 'Forgotten keys - cancel'</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state}}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state}}'</span></span>
|
||||
<span class="key">condition</span>:
|
||||
- <span class="string"><span class="content">condition: state</span></span>
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">script.send_key_alert</span></span>
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
1. 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<br />
|
||||
2. 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)</p>
|
||||
|
||||
<h3>{% linkable_title Using both types of iBeacons at the same time %}</h3>
|
||||
<h3><a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time </h3>
|
||||
<p>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.</p>
|
||||
|
||||
<p class="img">
|
||||
|
|
@ -144,7 +144,7 @@
|
|||
</p>
|
||||
<p>Waterproof beacon</p>
|
||||
|
||||
<h3>{% linkable_title Buying Beacons %}</h3>
|
||||
<h3><a class='title-link' name='buying-beacons' href='#buying-beacons'></a> Buying Beacons </h3>
|
||||
<p>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.</p>
|
||||
|
||||
<p>I’ve bought quite a few iBeacons from a company called <a href="http://bluesensenetworks.com/">Blue Sense Networks</a>. 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.</p>
|
||||
|
|
@ -157,12 +157,12 @@
|
|||
|
||||
<p>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!</p>
|
||||
|
||||
<h3>{% linkable_title Conclusion %}</h3>
|
||||
<h3><a class='title-link' name='conclusion' href='#conclusion'></a> Conclusion </h3>
|
||||
<p>As I said in <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better">part 1</a>, 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.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<h3>{% linkable_title Notes %}</h3>
|
||||
<h3><a class='title-link' name='notes' href='#notes'></a> Notes </h3>
|
||||
|
||||
<p>Please see the <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/#tips">notes at the end of Part 1</a> for documentation information.</p>
|
||||
|
||||
|
|
@ -180,7 +180,7 @@
|
|||
|
||||
<p>The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in <em>part 1</em>. In <em>part 2</em> I’ll talk about using iBeacons to track devices that can’t track themselves.</p>
|
||||
|
||||
<h3>{% linkable_title Using beacons to improve OwnTracks location data %}</h3>
|
||||
<h3><a class='title-link' name='using-beacons-to-improve-owntracks-location-data' href='#using-beacons-to-improve-owntracks-location-data'></a> Using beacons to improve OwnTracks location data </h3>
|
||||
|
||||
<p>When you use OwnTracks in standard <em>major move</em> mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!</p>
|
||||
|
||||
|
|
@ -188,13 +188,13 @@
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Getting Started %}</h3>
|
||||
<h3><a class='title-link' name='getting-started' href='#getting-started'></a> Getting Started </h3>
|
||||
|
||||
<p>To do this you first need to set up <a href="/components/mqtt/#picking-a-broker">MQTT</a> and <a href="/components/device_tracker.owntracks/">OwnTracks</a> in Home assistant - and make sure that HA can track your phone.</p>
|
||||
|
||||
<p>You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.</p>
|
||||
|
||||
<h4>{% linkable_title A. Tell Home Assistant where your beacon is located %}</h4>
|
||||
<h4><a class='title-link' name='a-tell-home-assistant-where-your-beacon-is-located' href='#a-tell-home-assistant-where-your-beacon-is-located'></a> A. Tell Home Assistant where your beacon is located </h4>
|
||||
|
||||
<p>You tell HomeAssistant about fixed locations by creating a Zone with the longitude and latitude of your beacon. You should also give the zone a name which you will also use when you set up OwnTracks. An an example this zone specifies the location of my drive way.</p>
|
||||
|
||||
|
|
@ -215,7 +215,7 @@
|
|||
|
||||
<p>Once you’ve created the zone - you need to restart HA. The next step is:-</p>
|
||||
|
||||
<h4>{% linkable_title B. Tell OwnTracks to track your beacon %}</h4>
|
||||
<h4><a class='title-link' name='b-tell-owntracks-to-track--your-beacon' href='#b-tell-owntracks-to-track--your-beacon'></a> B. Tell OwnTracks to track your beacon </h4>
|
||||
|
||||
<ol>
|
||||
<li>Go to the OwnTracks app on your phone</li>
|
||||
|
|
@ -246,7 +246,7 @@
|
|||
|
||||
<p>I’m also pleased to say I no longer get an <em>arrive home</em> event at 2am that turns the lights on. I hope I’ve convinced you that iBeacons are worth trying!</p>
|
||||
|
||||
<h3>{% linkable_title Mixing Beacons and GPS locations %}</h3>
|
||||
<h3><a class='title-link' name='mixing-beacons-and-gps-locations' href='#mixing-beacons-and-gps-locations'></a> Mixing Beacons and GPS locations </h3>
|
||||
|
||||
<p>You will probably use beacons to make entry into your existing GPS zones more reliable. By default either a beacon or a GPS location can cause you to enter a zone - and HA has some logic that should make them two work well together (it ignores GPS updates when you’re in an iBeacon Zone).</p>
|
||||
|
||||
|
|
@ -279,17 +279,17 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
|
|||
|
||||
<p>To get this to work you’ll probably need to experiment with the beacon signal strength to try to match the beacon reception area to the location you want to track. Let me know if you get this to work (it doesn’t make sense in my open plan house)</p>
|
||||
|
||||
<h3>{% linkable_title Conclusion %}</h3>
|
||||
<h3><a class='title-link' name='conclusion' href='#conclusion'></a> Conclusion </h3>
|
||||
|
||||
<p>Presence tracking sounds easy - and it’s an important part of Home Automation. Trying it shows how difficult it is to get presence detection right. I’ve found that iBeacons have improved the reliability and timeliness of knowing where I am, and I hope I encouraged you to try them too.</p>
|
||||
|
||||
<h3>{% linkable_title Tips %}</h3>
|
||||
<h3><a class='title-link' name='tips' href='#tips'></a> Tips </h3>
|
||||
|
||||
<p>You can find out more about configuring the OwnTracks application and beacons <a href="http://owntracks.org/booklet/features/beacons/">here</a></p>
|
||||
|
||||
<p>There is information about configuring Homeassistant to use beacons <a href="https://home-assistant.io/components/device_tracker.owntracks/">here</a></p>
|
||||
|
||||
<h4>{% linkable_title Connections and disconnecting %}</h4>
|
||||
<h4><a class='title-link' name='connections-and-disconnecting' href='#connections-and-disconnecting'></a> Connections and disconnecting </h4>
|
||||
|
||||
<p>Owntracks treats a region name with a leading <code>-</code> as a hint that it shouldn’t disconnect after a single missed packet. This improves the ability to keep a connection to a beacon.</p>
|
||||
|
||||
|
|
@ -297,7 +297,7 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
|
|||
|
||||
<p>In automations you can use a <code>for:</code> to avoid triggering during a brief disconnect, or use a script with a delay. Stay tuned for <em>part 2</em> for an example of this.</p>
|
||||
|
||||
<h4>{% linkable_title Using Multiple beacons for the same Zone %}</h4>
|
||||
<h4><a class='title-link' name='using-multiple-beacons-for-the-same-zone' href='#using-multiple-beacons-for-the-same-zone'></a> Using Multiple beacons for the same Zone </h4>
|
||||
<p>iBeacons have a <code>UUID</code> (usually set to the same value for beacons from the same manufacturer), as well as a <code>minor</code> and <code>major</code> number. If you set two beacons to have exactly same details then OwnTracks will think multiple beacons are at the same location.</p>
|
||||
|
||||
<p>This means you can have more than one beacon around your home - and a connection to any of them will count as <code>home</code> to OwnTracks and HA. This reduces disconnections.</p>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Internet-of-Things | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/internet-of-things/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -100,11 +100,11 @@
|
|||
<p>The background to how we got to these classifiers can be read after the break.<br />
|
||||
<!--more--></p>
|
||||
|
||||
<h2>{% linkable_title State %}</h2>
|
||||
<h2><a class='title-link' name='state' href='#state'></a> State </h2>
|
||||
|
||||
<p>How state is communicated can be broken down into 5 categories. They are not mutually exclusive - a device state can be available both via the cloud and local connectivity.</p>
|
||||
|
||||
<h3>{% linkable_title No state available %}</h3>
|
||||
<h3><a class='title-link' name='no-state-available' href='#no-state-available'></a> No state available </h3>
|
||||
<p>These are devices that do not have the capabilities to make their state available. They only allow to be controlled. For example, devices with infrared remote controls like TVs and ACs. You can press the turn on button on the remote but can only assume that your command was received and executed successfully. The device might not be powered or something is blocking the infrared receiver.</p>
|
||||
|
||||
<p>Home automation will have to approach such devices based on the assumption that it’s commands are received correctly: using optimistic updates. This means that after sending a command it will update the state of the device as if the command was received successfully.</p>
|
||||
|
|
@ -121,7 +121,7 @@
|
|||
<li>Home automation will assume the wrong state if the the command is not received correctly or if the device is controlled in any other way outside of the home automation system.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Polling the cloud %}</h3>
|
||||
<h3><a class='title-link' name='polling-the-cloud' href='#polling-the-cloud'></a> Polling the cloud </h3>
|
||||
<p>These are devices that will only report their state to their own cloud backend. The cloud backend will allow reading the state but will not notify when a new state has arrived. This requires the home automation to check frequently if the state has been updated.</p>
|
||||
|
||||
<p>Advantages:</p>
|
||||
|
|
@ -138,7 +138,7 @@
|
|||
<li>You are no longer in control about who has access to your data.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Cloud pushing new state %}</h3>
|
||||
<h3><a class='title-link' name='cloud-pushing-new-state' href='#cloud-pushing-new-state'></a> Cloud pushing new state </h3>
|
||||
<p>All off the previous section applies to this one. On top of that the cloud will now notify the home automation when a new state has arrived. This means that as soon as the cloud knows, the home automation knows.</p>
|
||||
|
||||
<p>Advantages:</p>
|
||||
|
|
@ -147,7 +147,7 @@
|
|||
<li>New state known as soon as available in the cloud.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Polling the local device %}</h3>
|
||||
<h3><a class='title-link' name='polling-the-local-device' href='#polling-the-local-device'></a> Polling the local device </h3>
|
||||
<p>These devices will offer an API that is locally accessible. The home automation will have to frequently check if the state has been updated.</p>
|
||||
|
||||
<p>Advantages:</p>
|
||||
|
|
@ -162,7 +162,7 @@
|
|||
<li>To be pollable, a device needs to be always online which requires the device to be connected to a power source.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Local device pushing new state %}</h3>
|
||||
<h3><a class='title-link' name='local-device-pushing-new-state' href='#local-device-pushing-new-state'></a> Local device pushing new state </h3>
|
||||
<p>The best of the best. These devices will send out a notice when they get to a new state. These devices usually use a home automation protocol to pass it’s message to a hub that will do the heavy lifting of managing and notifying subscribers</p>
|
||||
|
||||
<p>Advantages:</p>
|
||||
|
|
@ -179,14 +179,14 @@
|
|||
<li>If using deep sleep and wifi, will suffer a delay when waking up because connecting to WiFi and receiving an IP takes time.</li>
|
||||
</ul>
|
||||
|
||||
<h2>{% linkable_title Control %}</h2>
|
||||
<h2><a class='title-link' name='control' href='#control'></a> Control </h2>
|
||||
|
||||
<p>Controlling a device can, just like state, be done through cloud and/or local connectivity. But the more important part of control is knowing if your command was a success and the new state of the device.</p>
|
||||
|
||||
<h3>{% linkable_title No control available %}</h3>
|
||||
<h3><a class='title-link' name='no-control-available' href='#no-control-available'></a> No control available </h3>
|
||||
<p>These devices are not able to be controlled. They will only offer state.</p>
|
||||
|
||||
<h3>{% linkable_title Poll State after sending command %}</h3>
|
||||
<h3><a class='title-link' name='poll-state-after-sending-command' href='#poll-state-after-sending-command'></a> Poll State after sending command </h3>
|
||||
<p>These devices will require the state to be polled after sending a command to see if a command was successfull.</p>
|
||||
|
||||
<p>Advantages:</p>
|
||||
|
|
@ -201,13 +201,13 @@
|
|||
<li>It can take time before the state gets updated. How often do we poll and how long do we wait till we consider the command failed? Also, a state may change because of other factors. Difficult to determine if the updated state is because of our command.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Device pushes state update %}</h3>
|
||||
<h3><a class='title-link' name='device-pushes-state-update' href='#device-pushes-state-update'></a> Device pushes state update </h3>
|
||||
<p>These devices will not return a new state as a result of the command but instead will push a new state right away. The downside of this approach is that we have to assume that a state update coming in within a certain period of time after a command is related to the command.</p>
|
||||
|
||||
<h3>{% linkable_title Command returns new state %}</h3>
|
||||
<h3><a class='title-link' name='command-returns-new-state' href='#command-returns-new-state'></a> Command returns new state </h3>
|
||||
<p>The very best. These devices will answer the command with the new state after executing the command.</p>
|
||||
|
||||
<h2>{% linkable_title Classifying Home Assistant %}</h2>
|
||||
<h2><a class='title-link' name='classifying-home-assistant' href='#classifying-home-assistant'></a> Classifying Home Assistant </h2>
|
||||
<p>Home Assistant tries to offer the best experience possible via its APIs. There are different ways of interacting with Home Assistant but all are local.</p>
|
||||
|
||||
<ul>
|
||||
|
|
@ -225,7 +225,7 @@
|
|||
<id>https://home-assistant.io/blog/2016/01/19/perfect-home-automation</id>
|
||||
<content type="html"><![CDATA[<p>People often ask me about my vision for Home Assistant. Before I can describe where I want to go with Home Assistant, I should first talk about how home automation would look in my ideal world. This will be the aim of this post. I’m not going to focus on protocols, networks or specific hubs. That’s all implementation details. Instead, this post will focus on what is most important: the interaction between the users and their home.</p>
|
||||
|
||||
<h3>{% linkable_title You should not have to adapt to technology. %}</h3>
|
||||
<h3><a class='title-link' name='you-should-not-have-to-adapt-to-technology' href='#you-should-not-have-to-adapt-to-technology'></a> You should not have to adapt to technology. </h3>
|
||||
|
||||
<p>When people start using home automation, they always experience home control first: being able to control devices in new ways using a phone or computer. They believe the future is now and their app will be their remote for their lives. They only focus on what they are getting, not on what they are losing. You install some light bulbs and all of a sudden you are no longer able to use the light switches. You’ll arrive at home at night and have to pull out your phone, open the app, let it connect and finally you’ll be able to turn on the light. All while turning the light on could have been a switch away.</p>
|
||||
|
||||
|
|
@ -234,17 +234,17 @@
|
|||
<p>If you find that using your new home devices is cumbersome, the promise of home automation technology has failed you. Your lights should work with both a switch (or button) at the entrance of your room and via presence detection. Honestly, there are hardly any valid use cases for being able to control lights from your phone except for showing off.<br />
|
||||
<!--more--></p>
|
||||
|
||||
<h3>{% linkable_title You are not the only user of your home automation. %}</h3>
|
||||
<h3><a class='title-link' name='you-are-not-the-only-user-of-your-home-automation' href='#you-are-not-the-only-user-of-your-home-automation'></a> You are not the only user of your home automation. </h3>
|
||||
|
||||
<p>People tend to forget that they are not the only ones in their home. As the developer of your house you’re enthusiastic about the possibilities and are willing to overlook flaws. Chances are very high that the other people in your household have different hobbies and just want to mind their own business.</p>
|
||||
|
||||
<p>This means that everything you automate has to work flawlessly. If you successfully manage to cause a response to some stimulus 90% of the time, you’re going to have a disproportionately poor experience 10% of the time. A common automation that fits this pattern is to fade the lights when you start watching a movie or series in the living room. It only works if everyone is watching.</p>
|
||||
|
||||
<h3>{% linkable_title Limit the impact of false positives and negatives. %}</h3>
|
||||
<h3><a class='title-link' name='limit-the-impact-of-false-positives-and-negatives' href='#limit-the-impact-of-false-positives-and-negatives'></a> Limit the impact of false positives and negatives. </h3>
|
||||
|
||||
<p>With every automation, you always have to think: what will be the impact if it doesn’t work? Home automation is composed of many different systems by many different vendors that speak many different protocols: things will go wrong. It’s up to you to make sure that they have a limited impact when they fail. Ideally, devices should fall back to a pre-smart home experience. A Philips Hue bulb will act like a standard white light if turned on/off using a normal switch or when not connected to a hub. If things get worse when your system is out of order, your users will revolt. Take for example the Nest thermostat that <a href="http://www.nytimes.com/2016/01/14/fashion/nest-thermostat-glitch-battery-dies-software-freeze.html">had a bug in the beginning of January</a> which caused it to stop heating the house, yikes!</p>
|
||||
|
||||
<h3>{% linkable_title The perfect app is no app. %}</h3>
|
||||
<h3><a class='title-link' name='the-perfect-app-is-no-app' href='#the-perfect-app-is-no-app'></a> The perfect app is no app. </h3>
|
||||
|
||||
<p>Home automation should blend with your current workflow, not replace it. For most devices, there is no faster way to control most devices than how you are already doing it today. Most of the time, the best app is no app. The only interface that can be more convenient, and is accessible for visitors of your home of all ages is a voice interface. The industry has realized this too and there are some major players focussing on voice interaction. Take Apple for example: the only way to control your HomeKit devices is with Siri. Amazon has taken it one step further with the Amazon Echo, providing an always-listening connected speaker/microphone for the living room. I expect a lot more companies to join this segment in 2016.</p>
|
||||
|
||||
|
|
@ -252,7 +252,7 @@
|
|||
|
||||
<p>This however doesn’t mean there isn’t a place for apps, there definitely is. They are perfectly well-suited for checking in while you’re away, browsing the state changes of your house or making the lights go all funky when there are kids visiting.</p>
|
||||
|
||||
<h3>{% linkable_title Your system should run at home, not in the cloud. %}</h3>
|
||||
<h3><a class='title-link' name='your-system-should-run-at-home-not-in-the-cloud' href='#your-system-should-run-at-home-not-in-the-cloud'></a> Your system should run at home, not in the cloud. </h3>
|
||||
|
||||
<p>The cloud is a magical thing. Somewhere in the world there are computers collecting the data that your house generates, testing them against your automation rules and sending commands back when needed. The cloud will receive updates and improve itself over time so it is able to serve you better. Until it’s not. There are many reasons why your home might lose its connection to the cloud. The internet can stop working, an update might have gone wrong or the servers running the cloud crash.</p>
|
||||
|
||||
|
|
@ -279,8 +279,8 @@ This article will try to explain how they all relate.</p>
|
|||
<p>As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers <strong>home control</strong>.</p>
|
||||
|
||||
<p class="img">
|
||||
<a href="{{site_root}}/images/screenshots/nexus_7_dashboard.png">
|
||||
<img alt="Hub dashboard example" src="{{site_root}}/images/screenshots/nexus_7_dashboard.png" />
|
||||
<a href="/images/screenshots/nexus_7_dashboard.png">
|
||||
<img alt="Hub dashboard example" src="/images/screenshots/nexus_7_dashboard.png" />
|
||||
</a>
|
||||
Example of a hub’s dashboard. Showing the state of 2 persons, 4 lights and the sun.
|
||||
</p>
|
||||
|
|
@ -298,8 +298,8 @@ This article will try to explain how they all relate.</p>
|
|||
<p>All this results in the following overview of Home Automation.</p>
|
||||
|
||||
<p class="img">
|
||||
<a href="{{site_root}}/images/architecture/home_automation_landscape.png">
|
||||
<img alt="Home Automation landscape" src="{{site_root}}/images/architecture/home_automation_landscape.png" />
|
||||
<a href="/images/architecture/home_automation_landscape.png">
|
||||
<img alt="Home Automation landscape" src="/images/architecture/home_automation_landscape.png" />
|
||||
</a>
|
||||
Overview of the home automation landscape.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: IoT-Data | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/iot-data/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -39,7 +39,7 @@ One of the graphs created with this tutorial.
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Dependencies %}</h3>
|
||||
<h3><a class='title-link' name='dependencies' href='#dependencies'></a> Dependencies </h3>
|
||||
|
||||
<p>In order to run the provided Jupyter notebook, please make sure you have the following applications/libraries installed on your computer:</p>
|
||||
|
||||
|
|
@ -53,11 +53,11 @@ One of the graphs created with this tutorial.
|
|||
|
||||
<p>As a Windows user myself, I find the easiest, quickest and most hassle-free way of installing all of these dependencies is to use <a href="https://winpython.github.io/">WinPython</a>. This free open-source portable distribution includes all of the dependencies required for this notebook, as well as a few other essential Python libraries you may require for data exploration in the future.</p>
|
||||
|
||||
<h4>{% linkable_title Why Jupyter? %}</h4>
|
||||
<h4><a class='title-link' name='why-jupyter' href='#why-jupyter'></a> Why Jupyter? </h4>
|
||||
|
||||
<p>While all Home Assistant implementations can have varying setup, components and scripts, the underlying data structure is standardized and well-defined. This allows us to write Python code that is environmentally agnostic. Wrapping it in a Jupyter notebook ensures the code, visualizations and directions/explanations are kept digestible and neatly-packaged. One of the amazing features of Jupyter is the ability to change code as you go along, customizing all outputs and visualizations on the fly!</p>
|
||||
|
||||
<h4>{% linkable_title Where do I start? %}</h4>
|
||||
<h4><a class='title-link' name='where-do-i-start' href='#where-do-i-start'></a> Where do I start? </h4>
|
||||
|
||||
<p>This tutorial is based around a heavily commented Jupyter Notebook that we created. So to get started, you will have to open that:</p>
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ One of the graphs created with this tutorial.
|
|||
One of the graphs created with this tutorial.
|
||||
</p>
|
||||
|
||||
<h4>{% linkable_title What’s next? %}</h4>
|
||||
<h4><a class='title-link' name='whats-next' href='#whats-next'></a> What’s next? </h4>
|
||||
|
||||
<p>Thanks to the magic of Jupyter, all of the code is customizable: want to selectively display your data, only covering a specific entity? Sure thing! Want to change the properties of the plots? No problem!</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: MQTT | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/mqtt/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -269,7 +269,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Components %}</h3>
|
||||
<h3><a class='title-link' name='components' href='#components'></a> Components </h3>
|
||||
|
||||
<p>I’ve been using Adafruit for my shopping:</p>
|
||||
|
||||
|
|
@ -281,7 +281,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
|
||||
<p><em>Besides this, you will need the usual hardware prototype equipment: a breadboard, some wires, soldering iron + wire, Serial USB cable.</em></p>
|
||||
|
||||
<h3>{% linkable_title Alternatives %}</h3>
|
||||
<h3><a class='title-link' name='alternatives' href='#alternatives'></a> Alternatives </h3>
|
||||
|
||||
<p>Since this article has been published the HDC1008 has been discontinued. Updated sketches are available for the following alternatives:</p>
|
||||
|
||||
|
|
@ -290,7 +290,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
<li><a href="https://www.adafruit.com/product/2652">BME280 sensor</a> and <a href="https://gist.github.com/mtl010957/9ee85fb404f65e15c440b08c659c0419">updated sketch</a>.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Connections %}</h3>
|
||||
<h3><a class='title-link' name='connections' href='#connections'></a> Connections </h3>
|
||||
|
||||
<p>On your breadboard, make the following connections from your ESP8266 to the HDC1008:</p>
|
||||
|
||||
|
|
@ -323,7 +323,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
|
||||
<p><em>I picked <code>#2</code> and <code>14</code> myself, you can configure them in the sketch.</em></p>
|
||||
|
||||
<h3>{% linkable_title Preparing your IDE %}</h3>
|
||||
<h3><a class='title-link' name='preparing-your-ide' href='#preparing-your-ide'></a> Preparing your IDE </h3>
|
||||
|
||||
<p>Follow <a href="https://github.com/esp8266/Arduino#installing-with-boards-manager">these instructions</a> on how to install and prepare the Arduino IDE for ESP8266 development.</p>
|
||||
|
||||
|
|
@ -334,7 +334,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
<li>Adafruit HDC1000</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Sketch %}</h3>
|
||||
<h3><a class='title-link' name='sketch' href='#sketch'></a> Sketch </h3>
|
||||
|
||||
<p>If you have followed the previous steps, you’re all set.</p>
|
||||
|
||||
|
|
@ -578,7 +578,7 @@ Adafruit_HDC1000 hdc = Adafruit_HDC1000();
|
|||
</tr></table>
|
||||
</div>
|
||||
|
||||
<h3>{% linkable_title Configuring Home Assistant %}</h3>
|
||||
<h3><a class='title-link' name='configuring-home-assistant' href='#configuring-home-assistant'></a> Configuring Home Assistant </h3>
|
||||
|
||||
<p>The last step is to integrate the sensor values into Home Assistant. This can be done by setting up Home Assistant to connect to the MQTT broker and subscribe to the sensor topics.</p>
|
||||
|
||||
|
|
@ -640,7 +640,7 @@ Adafruit_HDC1000 hdc = Adafruit_HDC1000();
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Manual usage %}</h3>
|
||||
<h3><a class='title-link' name='manual-usage' href='#manual-usage'></a> Manual usage </h3>
|
||||
|
||||
<p>The simplest but not the coolest way as a human to interact with a Home Assistant sensor is launching a command manually. Let’s create a “Mood” sensor. For simplicity Home Assistant and the MQTT broker are both running on the same host. The needed configuration snipplets to add to the <code>configuration.yaml</code> file consists of two parts: one for the broker and one for the sensor.</p>
|
||||
|
||||
|
|
@ -683,7 +683,7 @@ Adafruit_HDC1000 hdc = Adafruit_HDC1000();
|
|||
|
||||
<p>This is a really bad example. Don’t do this in the real world because you won’t be able to create diagrams of historical data. Better use a numerical value.</p>
|
||||
|
||||
<h3>{% linkable_title Python MQTT bindings %}</h3>
|
||||
<h3><a class='title-link' name='python-mqtt-bindings' href='#python-mqtt-bindings'></a> Python MQTT bindings </h3>
|
||||
|
||||
<p>The last section was pretty boring, I know. Nobody wants to send MQTT messages by hand if there is a computer on the desk. If you are playing the lottery this section is for you. If not, read it anyway because the lottery is just an example :-).</p>
|
||||
|
||||
|
|
@ -768,7 +768,7 @@ client.loop_start()
|
|||
|
||||
<p>With only a few lines of Python and an MQTT broker you can create your own “smartdevice” or send information to Home Assistant which you haven’t think of. Of course this is not limited to Python. If there is an MQTT library available, the device can be used with Home Assistant now.</p>
|
||||
|
||||
<h3>{% linkable_title Arduino %}</h3>
|
||||
<h3><a class='title-link' name='arduino' href='#arduino'></a> Arduino </h3>
|
||||
|
||||
<p>To get started with real hardware that is capable to send MQTT messages, the Arduino platform is an inexpensive way to do it. In this section an Arduino UNO with an Ethernet shield and a photo resistor is used. The photo resistor is connected to analog pin 0 (A0) and has an output from 0 to 1024.</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Organisation | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -58,7 +58,7 @@
|
|||
<p>The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).</p>
|
||||
|
||||
<p class="img">
|
||||
<img src="{{site_root}}/images/blog/ha-logo-history.png" />
|
||||
<img src="/images/blog/ha-logo-history.png" />
|
||||
The old logo, the new detailed logo and the new simple logo.
|
||||
</p>
|
||||
]]></content>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: OwnTracks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/owntracks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
|
||||
<p>In <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better">Part 1</a> 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.</p>
|
||||
|
||||
<h3>{% linkable_title Tracking things using iBeacons %}</h3>
|
||||
<h3><a class='title-link' name='tracking-things-using-ibeacons' href='#tracking-things-using-ibeacons'></a> Tracking things using iBeacons </h3>
|
||||
<p>In the first part I mentioned that iBeacons just send out <em>I’m here</em> packets, and we used this to trigger an update when your phone came close to a fixed beacon.</p>
|
||||
|
||||
<p>But beacons don’t have to be fixed.</p>
|
||||
|
|
@ -90,10 +90,10 @@
|
|||
- <span class="string"><span class="content">alias: 'Forgotten keys'</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{states.device_tracker.greg_gregphone.state != states.device_tracker.beacon_keys.state}}'</span></span>
|
||||
<span class="key">condition</span>:
|
||||
<span class="key">condition</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{ states.device_tracker.greg_gregphone.state != "home" }}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{ states.device_tracker.greg_gregphone.state != "home" }}'</span></span>
|
||||
<span class="key">action</span>:
|
||||
<span class="key">service</span>: <span class="string"><span class="content">script.turn_on</span></span>
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">script.send_key_alert</span></span>
|
||||
|
|
@ -101,7 +101,7 @@
|
|||
- <span class="string"><span class="content">alias: 'Forgotten keys - cancel'</span></span>
|
||||
<span class="key">trigger</span>:
|
||||
<span class="key">platform</span>: <span class="string"><span class="content">template</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">{% raw %}'{{states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state}}'{% endraw %}</span></span>
|
||||
<span class="key">value_template</span>: <span class="string"><span class="content">'{{states.device_tracker.greg_gregphone.state == states.device_tracker.beacon_keys.state}}'</span></span>
|
||||
<span class="key">condition</span>:
|
||||
- <span class="string"><span class="content">condition: state</span></span>
|
||||
<span class="key">entity_id</span>: <span class="string"><span class="content">script.send_key_alert</span></span>
|
||||
|
|
@ -131,7 +131,7 @@
|
|||
1. 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<br />
|
||||
2. 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)</p>
|
||||
|
||||
<h3>{% linkable_title Using both types of iBeacons at the same time %}</h3>
|
||||
<h3><a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time </h3>
|
||||
<p>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.</p>
|
||||
|
||||
<p class="img">
|
||||
|
|
@ -144,7 +144,7 @@
|
|||
</p>
|
||||
<p>Waterproof beacon</p>
|
||||
|
||||
<h3>{% linkable_title Buying Beacons %}</h3>
|
||||
<h3><a class='title-link' name='buying-beacons' href='#buying-beacons'></a> Buying Beacons </h3>
|
||||
<p>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.</p>
|
||||
|
||||
<p>I’ve bought quite a few iBeacons from a company called <a href="http://bluesensenetworks.com/">Blue Sense Networks</a>. 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.</p>
|
||||
|
|
@ -157,12 +157,12 @@
|
|||
|
||||
<p>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!</p>
|
||||
|
||||
<h3>{% linkable_title Conclusion %}</h3>
|
||||
<h3><a class='title-link' name='conclusion' href='#conclusion'></a> Conclusion </h3>
|
||||
<p>As I said in <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better">part 1</a>, 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.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<h3>{% linkable_title Notes %}</h3>
|
||||
<h3><a class='title-link' name='notes' href='#notes'></a> Notes </h3>
|
||||
|
||||
<p>Please see the <a href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/#tips">notes at the end of Part 1</a> for documentation information.</p>
|
||||
|
||||
|
|
@ -180,7 +180,7 @@
|
|||
|
||||
<p>The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in <em>part 1</em>. In <em>part 2</em> I’ll talk about using iBeacons to track devices that can’t track themselves.</p>
|
||||
|
||||
<h3>{% linkable_title Using beacons to improve OwnTracks location data %}</h3>
|
||||
<h3><a class='title-link' name='using-beacons-to-improve-owntracks-location-data' href='#using-beacons-to-improve-owntracks-location-data'></a> Using beacons to improve OwnTracks location data </h3>
|
||||
|
||||
<p>When you use OwnTracks in standard <em>major move</em> mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!</p>
|
||||
|
||||
|
|
@ -188,13 +188,13 @@
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Getting Started %}</h3>
|
||||
<h3><a class='title-link' name='getting-started' href='#getting-started'></a> Getting Started </h3>
|
||||
|
||||
<p>To do this you first need to set up <a href="/components/mqtt/#picking-a-broker">MQTT</a> and <a href="/components/device_tracker.owntracks/">OwnTracks</a> in Home assistant - and make sure that HA can track your phone.</p>
|
||||
|
||||
<p>You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.</p>
|
||||
|
||||
<h4>{% linkable_title A. Tell Home Assistant where your beacon is located %}</h4>
|
||||
<h4><a class='title-link' name='a-tell-home-assistant-where-your-beacon-is-located' href='#a-tell-home-assistant-where-your-beacon-is-located'></a> A. Tell Home Assistant where your beacon is located </h4>
|
||||
|
||||
<p>You tell HomeAssistant about fixed locations by creating a Zone with the longitude and latitude of your beacon. You should also give the zone a name which you will also use when you set up OwnTracks. An an example this zone specifies the location of my drive way.</p>
|
||||
|
||||
|
|
@ -215,7 +215,7 @@
|
|||
|
||||
<p>Once you’ve created the zone - you need to restart HA. The next step is:-</p>
|
||||
|
||||
<h4>{% linkable_title B. Tell OwnTracks to track your beacon %}</h4>
|
||||
<h4><a class='title-link' name='b-tell-owntracks-to-track--your-beacon' href='#b-tell-owntracks-to-track--your-beacon'></a> B. Tell OwnTracks to track your beacon </h4>
|
||||
|
||||
<ol>
|
||||
<li>Go to the OwnTracks app on your phone</li>
|
||||
|
|
@ -246,7 +246,7 @@
|
|||
|
||||
<p>I’m also pleased to say I no longer get an <em>arrive home</em> event at 2am that turns the lights on. I hope I’ve convinced you that iBeacons are worth trying!</p>
|
||||
|
||||
<h3>{% linkable_title Mixing Beacons and GPS locations %}</h3>
|
||||
<h3><a class='title-link' name='mixing-beacons-and-gps-locations' href='#mixing-beacons-and-gps-locations'></a> Mixing Beacons and GPS locations </h3>
|
||||
|
||||
<p>You will probably use beacons to make entry into your existing GPS zones more reliable. By default either a beacon or a GPS location can cause you to enter a zone - and HA has some logic that should make them two work well together (it ignores GPS updates when you’re in an iBeacon Zone).</p>
|
||||
|
||||
|
|
@ -279,17 +279,17 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
|
|||
|
||||
<p>To get this to work you’ll probably need to experiment with the beacon signal strength to try to match the beacon reception area to the location you want to track. Let me know if you get this to work (it doesn’t make sense in my open plan house)</p>
|
||||
|
||||
<h3>{% linkable_title Conclusion %}</h3>
|
||||
<h3><a class='title-link' name='conclusion' href='#conclusion'></a> Conclusion </h3>
|
||||
|
||||
<p>Presence tracking sounds easy - and it’s an important part of Home Automation. Trying it shows how difficult it is to get presence detection right. I’ve found that iBeacons have improved the reliability and timeliness of knowing where I am, and I hope I encouraged you to try them too.</p>
|
||||
|
||||
<h3>{% linkable_title Tips %}</h3>
|
||||
<h3><a class='title-link' name='tips' href='#tips'></a> Tips </h3>
|
||||
|
||||
<p>You can find out more about configuring the OwnTracks application and beacons <a href="http://owntracks.org/booklet/features/beacons/">here</a></p>
|
||||
|
||||
<p>There is information about configuring Homeassistant to use beacons <a href="https://home-assistant.io/components/device_tracker.owntracks/">here</a></p>
|
||||
|
||||
<h4>{% linkable_title Connections and disconnecting %}</h4>
|
||||
<h4><a class='title-link' name='connections-and-disconnecting' href='#connections-and-disconnecting'></a> Connections and disconnecting </h4>
|
||||
|
||||
<p>Owntracks treats a region name with a leading <code>-</code> as a hint that it shouldn’t disconnect after a single missed packet. This improves the ability to keep a connection to a beacon.</p>
|
||||
|
||||
|
|
@ -297,7 +297,7 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
|
|||
|
||||
<p>In automations you can use a <code>for:</code> to avoid triggering during a brief disconnect, or use a script with a delay. Stay tuned for <em>part 2</em> for an example of this.</p>
|
||||
|
||||
<h4>{% linkable_title Using Multiple beacons for the same Zone %}</h4>
|
||||
<h4><a class='title-link' name='using-multiple-beacons-for-the-same-zone' href='#using-multiple-beacons-for-the-same-zone'></a> Using Multiple beacons for the same Zone </h4>
|
||||
<p>iBeacons have a <code>UUID</code> (usually set to the same value for beacons from the same manufacturer), as well as a <code>minor</code> and <code>major</code> number. If you set two beacons to have exactly same details then OwnTracks will think multiple beacons are at the same location.</p>
|
||||
|
||||
<p>This means you can have more than one beacon around your home - and a connection to any of them will count as <code>home</code> to OwnTracks and HA. This reduces disconnections.</p>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Presence-Detection | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/presence-detection/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -24,7 +24,7 @@
|
|||
|
||||
<p>The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in <em>part 1</em>. In <em>part 2</em> I’ll talk about using iBeacons to track devices that can’t track themselves.</p>
|
||||
|
||||
<h3>{% linkable_title Using beacons to improve OwnTracks location data %}</h3>
|
||||
<h3><a class='title-link' name='using-beacons-to-improve-owntracks-location-data' href='#using-beacons-to-improve-owntracks-location-data'></a> Using beacons to improve OwnTracks location data </h3>
|
||||
|
||||
<p>When you use OwnTracks in standard <em>major move</em> mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!</p>
|
||||
|
||||
|
|
@ -32,13 +32,13 @@
|
|||
|
||||
<!--more-->
|
||||
|
||||
<h3>{% linkable_title Getting Started %}</h3>
|
||||
<h3><a class='title-link' name='getting-started' href='#getting-started'></a> Getting Started </h3>
|
||||
|
||||
<p>To do this you first need to set up <a href="/components/mqtt/#picking-a-broker">MQTT</a> and <a href="/components/device_tracker.owntracks/">OwnTracks</a> in Home assistant - and make sure that HA can track your phone.</p>
|
||||
|
||||
<p>You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.</p>
|
||||
|
||||
<h4>{% linkable_title A. Tell Home Assistant where your beacon is located %}</h4>
|
||||
<h4><a class='title-link' name='a-tell-home-assistant-where-your-beacon-is-located' href='#a-tell-home-assistant-where-your-beacon-is-located'></a> A. Tell Home Assistant where your beacon is located </h4>
|
||||
|
||||
<p>You tell HomeAssistant about fixed locations by creating a Zone with the longitude and latitude of your beacon. You should also give the zone a name which you will also use when you set up OwnTracks. An an example this zone specifies the location of my drive way.</p>
|
||||
|
||||
|
|
@ -59,7 +59,7 @@
|
|||
|
||||
<p>Once you’ve created the zone - you need to restart HA. The next step is:-</p>
|
||||
|
||||
<h4>{% linkable_title B. Tell OwnTracks to track your beacon %}</h4>
|
||||
<h4><a class='title-link' name='b-tell-owntracks-to-track--your-beacon' href='#b-tell-owntracks-to-track--your-beacon'></a> B. Tell OwnTracks to track your beacon </h4>
|
||||
|
||||
<ol>
|
||||
<li>Go to the OwnTracks app on your phone</li>
|
||||
|
|
@ -90,7 +90,7 @@
|
|||
|
||||
<p>I’m also pleased to say I no longer get an <em>arrive home</em> event at 2am that turns the lights on. I hope I’ve convinced you that iBeacons are worth trying!</p>
|
||||
|
||||
<h3>{% linkable_title Mixing Beacons and GPS locations %}</h3>
|
||||
<h3><a class='title-link' name='mixing-beacons-and-gps-locations' href='#mixing-beacons-and-gps-locations'></a> Mixing Beacons and GPS locations </h3>
|
||||
|
||||
<p>You will probably use beacons to make entry into your existing GPS zones more reliable. By default either a beacon or a GPS location can cause you to enter a zone - and HA has some logic that should make them two work well together (it ignores GPS updates when you’re in an iBeacon Zone).</p>
|
||||
|
||||
|
|
@ -123,17 +123,17 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
|
|||
|
||||
<p>To get this to work you’ll probably need to experiment with the beacon signal strength to try to match the beacon reception area to the location you want to track. Let me know if you get this to work (it doesn’t make sense in my open plan house)</p>
|
||||
|
||||
<h3>{% linkable_title Conclusion %}</h3>
|
||||
<h3><a class='title-link' name='conclusion' href='#conclusion'></a> Conclusion </h3>
|
||||
|
||||
<p>Presence tracking sounds easy - and it’s an important part of Home Automation. Trying it shows how difficult it is to get presence detection right. I’ve found that iBeacons have improved the reliability and timeliness of knowing where I am, and I hope I encouraged you to try them too.</p>
|
||||
|
||||
<h3>{% linkable_title Tips %}</h3>
|
||||
<h3><a class='title-link' name='tips' href='#tips'></a> Tips </h3>
|
||||
|
||||
<p>You can find out more about configuring the OwnTracks application and beacons <a href="http://owntracks.org/booklet/features/beacons/">here</a></p>
|
||||
|
||||
<p>There is information about configuring Homeassistant to use beacons <a href="https://home-assistant.io/components/device_tracker.owntracks/">here</a></p>
|
||||
|
||||
<h4>{% linkable_title Connections and disconnecting %}</h4>
|
||||
<h4><a class='title-link' name='connections-and-disconnecting' href='#connections-and-disconnecting'></a> Connections and disconnecting </h4>
|
||||
|
||||
<p>Owntracks treats a region name with a leading <code>-</code> as a hint that it shouldn’t disconnect after a single missed packet. This improves the ability to keep a connection to a beacon.</p>
|
||||
|
||||
|
|
@ -141,7 +141,7 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
|
|||
|
||||
<p>In automations you can use a <code>for:</code> to avoid triggering during a brief disconnect, or use a script with a delay. Stay tuned for <em>part 2</em> for an example of this.</p>
|
||||
|
||||
<h4>{% linkable_title Using Multiple beacons for the same Zone %}</h4>
|
||||
<h4><a class='title-link' name='using-multiple-beacons-for-the-same-zone' href='#using-multiple-beacons-for-the-same-zone'></a> Using Multiple beacons for the same Zone </h4>
|
||||
<p>iBeacons have a <code>UUID</code> (usually set to the same value for beacons from the same manufacturer), as well as a <code>minor</code> and <code>major</code> number. If you set two beacons to have exactly same details then OwnTracks will think multiple beacons are at the same location.</p>
|
||||
|
||||
<p>This means you can have more than one beacon around your home - and a connection to any of them will count as <code>home</code> to OwnTracks and HA. This reduces disconnections.</p>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/public-service-announcement/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Release-Notes | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/release-notes/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -59,11 +59,11 @@ $ hass --script db_migrator --config /path/to/config
|
|||
<li>Frontend: Wait up to two seconds for new state before resetting toggle after toggling state (<a href="https://github.com/balloob/">@balloob</a>)</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Hotfix 0.24.1 - July 21 %}</h3>
|
||||
<h3><a class='title-link' name='hotfix-0241---july-21' href='#hotfix-0241---july-21'></a> Hotfix 0.24.1 - July 21 </h3>
|
||||
|
||||
<p>Quick hot fix after we found a bug in the migrator where it wouldn’t work with a database in a non-standard location. Thanks to <a href="https://github.com/n8henrie/">@n8henrie</a> and <a href="https://github.com/AlucardZero/">@AlucardZero</a>.</p>
|
||||
|
||||
<h3>{% linkable_title Breaking changes %}</h3>
|
||||
<h3><a class='title-link' name='breaking-changes' href='#breaking-changes'></a> Breaking changes </h3>
|
||||
|
||||
<ul>
|
||||
<li>Migrating existing databases (see above).</li>
|
||||
|
|
@ -115,13 +115,13 @@ $ hass --script db_migrator --config /path/to/config
|
|||
<li>HTTP: Migrate to CherryPy WSGI server to fix install and runtime problems (<a href="https://github.com/balloob/">@balloob</a>)</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Breaking changes %}</h3>
|
||||
<h3><a class='title-link' name='breaking-changes' href='#breaking-changes'></a> Breaking changes </h3>
|
||||
|
||||
<ul>
|
||||
<li>Homematic thermostat configuration has changed and now depends on the new <a href="/components/homematic/">Homematic</a> component.</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Hotfix 0.23.1 - July 2 %}</h3>
|
||||
<h3><a class='title-link' name='hotfix-0231---july-2' href='#hotfix-0231---july-2'></a> Hotfix 0.23.1 - July 2 </h3>
|
||||
|
||||
<ul>
|
||||
<li>Bump PyVera to 0.2.13 to fix traceback and pyvera thread dying related to bug (<a href="https://github.com/rhooper/">@rhooper</a>)</li>
|
||||
|
|
@ -129,7 +129,7 @@ $ hass --script db_migrator --config /path/to/config
|
|||
<li>Wink: Downgraded pubnub to work around pycryptodome conflicts (<a href="https://github.com/w1ll1am23/">@w1ll1am23</a>)</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title FAQ %}</h3>
|
||||
<h3><a class='title-link' name='faq' href='#faq'></a> FAQ </h3>
|
||||
|
||||
<ul>
|
||||
<li><code>elevation: </code> was introduced to the configuration for weather/sunrise data. For existing <a href="https://home-assistant.io/getting-started/basic/">configurations</a> add the value shown in the warning <code>[homeassistant.config] Incomplete core config. Auto detected elevation: 665</code> to your <code>configuration.yaml</code> file.</li>
|
||||
|
|
@ -178,7 +178,7 @@ $ hass --script db_migrator --config /path/to/config
|
|||
<li>Sensor: Support for Swiss hydrological data (<a href="https://github.com/fabaff/">@fabaff</a>)</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Breaking change %}</h3>
|
||||
<h3><a class='title-link' name='breaking-change' href='#breaking-change'></a> Breaking change </h3>
|
||||
|
||||
<ul>
|
||||
<li>The new Netatmo support caused us to change how Netatmo are configured. It’s now done via it’s own component.</li>
|
||||
|
|
@ -194,7 +194,7 @@ $ hass --script db_migrator --config /path/to/config
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<h3>{% linkable_title Hotfix 0.22.1 - June 20 %}</h3>
|
||||
<h3><a class='title-link' name='hotfix-0221---june-20' href='#hotfix-0221---june-20'></a> Hotfix 0.22.1 - June 20 </h3>
|
||||
|
||||
<ul>
|
||||
<li>Insteon Hub lights will load again</li>
|
||||
|
|
@ -307,7 +307,7 @@ $ hass --script db_migrator --config /path/to/config
|
|||
<li>Group more info dialog allows control of group domain if available (<a href="https://github.com/fignuts">@fignuts</a>)</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% linkable_title Breaking changes %}</h3>
|
||||
<h3><a class='title-link' name='breaking-changes' href='#breaking-changes'></a> Breaking changes </h3>
|
||||
|
||||
<ul>
|
||||
<li>Asus WRT will now default to SSH with Telnet being an option</li>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Survey | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/survey/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Talks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/talks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Technology | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/technology/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: User-Stories | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/user-stories/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Video | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/video/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -61,11 +61,11 @@
|
|||
<id>https://home-assistant.io/blog/2016/06/01/community-highlights</id>
|
||||
<content type="html"><![CDATA[<p>Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our <a href="https://gitter.im/home-assistant/home-assistant">chat room</a> and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.</p>
|
||||
|
||||
<h3>{% linkable_title SceneGen - cli for making scenes %}</h3>
|
||||
<h3><a class='title-link' name='scenegen---cli-for-making-scenes' href='#scenegen---cli-for-making-scenes'></a> SceneGen - cli for making scenes </h3>
|
||||
|
||||
<p><a href="https://github.com/acockburn/scenegen">SceneGen</a> is a new command line utility developed by <a href="https://github.com/acockburn">Andrew Cockburn</a> that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.</p>
|
||||
|
||||
<h3>{% linkable_title Videos %}</h3>
|
||||
<h3><a class='title-link' name='videos' href='#videos'></a> Videos </h3>
|
||||
|
||||
<p><a href="https://partofthething.com">Nick Touran</a> has been working on integrating IR remotes with Home Assistant. He made it into a component which should be available in the next release which should arrive in a couple of days. In the meanwhile, he wrote up <a href="https://partofthething.com/thoughts/?p=1010">a blog post</a> and has put out a video showing the new integration, very cool!</p>
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Website | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/website/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2016-07-24T17:13:16+00:00</updated>
|
||||
<updated>2016-07-24T17:38:38+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue