jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2018-01-25 17:33:45 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-25 17:33:45 +00:00
parent 2a429df2b2
commit 94552b64db
144 changed files with 304 additions and 301 deletions
Download patch file Download diff file Expand all files Collapse all files

2
addons/dhcp_server/index.html
View file

@ -112,7 +112,7 @@
 - <strong>broadcast</strong> (<em>Required</em>): Network broadcast address.  - <strong>broadcast</strong> (<em>Required</em>): Network broadcast address.
 - <strong>gateway</strong> (<em>Required</em>): A List of gateways.  - <strong>gateway</strong> (<em>Required</em>): A List of gateways.
<ul> <ul>
<li><strong>interface</strong> (<em>Required</em>): Inteface on that will be listen. Normally is <code class="highlighter-rouge">eth0</code> for ethernet wired connection and <code class="highlighter-rouge">wlan0</code> for wireless connection.</li> <li><strong>interface</strong> (<em>Required</em>): Interface on that will be listen. Normally is <code class="highlighter-rouge">eth0</code> for ethernet wired connection and <code class="highlighter-rouge">wlan0</code> for wireless connection.</li>
</ul> </ul>
</li> </li>
<li><strong>hosts</strong> (<em>Optional</em>): A list of fixed IPs for devices. <li><strong>hosts</strong> (<em>Optional</em>): A list of fixed IPs for devices.

10
atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Home Assistant]]></title> <title><![CDATA[Home Assistant]]></title>
<link href="https://home-assistant.io/atom.xml" rel="self"/> <link href="https://home-assistant.io/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -754,14 +754,14 @@ Note however, that this feature was replaced by a new ignore_string config optio
</p> </p>
<h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2> <h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2>
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editting has been made easier.</p> <p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editing has been made easier.</p>
<h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2> <h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2>
<p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p> <p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p>
<p class="img"> <p class="img">
<img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." /> <img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." />
Screenshot of the of the Enitity Picker. Screenshot of the of the Entity Picker.
</p> </p>
<h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2> <h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2>
@ -1081,7 +1081,7 @@ The Hass.io release of 0.58 will be delayed by a couple of days because Pascal i
<h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2> <h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2>
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.</p> <p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.</p>
<p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p> <p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p>
@ -1298,7 +1298,7 @@ For Custom UI users: your custom UI will need to be updated before it can work w
<h2><a class="title-link" name="setting-up-tor" href="#setting-up-tor"></a> Setting up Tor</h2> <h2><a class="title-link" name="setting-up-tor" href="#setting-up-tor"></a> Setting up Tor</h2>
<p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailled guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p> <p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailed guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p>
<ol> <ol>
<li>Install Tor. On a Debian-based system: <code class="highlighter-rouge">$ sudo apt-get install tor</code>. On Fedora: <code class="highlighter-rouge">$ sudo dnf install tor</code></li> <li>Install Tor. On a Debian-based system: <code class="highlighter-rouge">$ sudo apt-get install tor</code>. On Fedora: <code class="highlighter-rouge">$ sudo dnf install tor</code></li>

2
blog/2015/02/08/looking-at-the-past/index.html
View file

@ -91,7 +91,7 @@
<li>Recorder component that will record every event to a SQLite database</li> <li>Recorder component that will record every event to a SQLite database</li>
<li>History component that will query and aggregate the recorded events</li> <li>History component that will query and aggregate the recorded events</li>
</ul> </ul>
<p>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p> <p>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of today’s release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p>
<p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p> <p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p>
<p>The history component will be enabled for new users by default. For current users, run <code class="highlighter-rouge">scripts/update</code> to upgrade to the latest version and add <code class="highlighter-rouge">[history]</code> to your <code class="highlighter-rouge">home-assistant.conf</code> file.</p> <p>The history component will be enabled for new users by default. For current users, run <code class="highlighter-rouge">scripts/update</code> to upgrade to the latest version and add <code class="highlighter-rouge">[history]</code> to your <code class="highlighter-rouge">home-assistant.conf</code> file.</p>
<p class="img"> <p class="img">

2
blog/2015/03/08/new-logo/index.html
View file

@ -78,7 +78,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'

2
blog/2015/09/11/different-ways-to-use-mqtt-with-home-assistant/index.html
View file

@ -178,7 +178,7 @@
</span><span class="kt">char</span><span class="o">*</span> <span class="n">stateTopic</span> <span class="o">=</span> <span class="s">"home-assistant/sensor01/brightness"</span><span class="p">;</span> <span class="c1">// MQTT topic where values are published </span><span class="kt">char</span><span class="o">*</span> <span class="n">stateTopic</span> <span class="o">=</span> <span class="s">"home-assistant/sensor01/brightness"</span><span class="p">;</span> <span class="c1">// MQTT topic where values are published
</span><span class="kt">int</span> <span class="n">sensorPin</span> <span class="o">=</span> <span class="n">A0</span><span class="p">;</span> <span class="c1">// Pin to which the sensor is connected to </span><span class="kt">int</span> <span class="n">sensorPin</span> <span class="o">=</span> <span class="n">A0</span><span class="p">;</span> <span class="c1">// Pin to which the sensor is connected to
</span><span class="kt">char</span> <span class="n">buf</span><span class="p">[</span><span class="mi">4</span><span class="p">];</span> <span class="c1">// Buffer to store the sensor value </span><span class="kt">char</span> <span class="n">buf</span><span class="p">[</span><span class="mi">4</span><span class="p">];</span> <span class="c1">// Buffer to store the sensor value
</span><span class="kt">int</span> <span class="n">updateInterval</span> <span class="o">=</span> <span class="mi">1000</span><span class="p">;</span> <span class="c1">// Interval in miliseconds </span><span class="kt">int</span> <span class="n">updateInterval</span> <span class="o">=</span> <span class="mi">1000</span><span class="p">;</span> <span class="c1">// Interval in milliseconds
</span> </span>
<span class="c1">// MQTT server settings <span class="c1">// MQTT server settings
</span><span class="n">IPAddress</span> <span class="n">mqttServer</span><span class="p">(</span><span class="mi">192</span><span class="p">,</span> <span class="mi">168</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">12</span><span class="p">);</span> </span><span class="n">IPAddress</span> <span class="n">mqttServer</span><span class="p">(</span><span class="mi">192</span><span class="p">,</span> <span class="mi">168</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">12</span><span class="p">);</span>

2
blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
View file

@ -86,7 +86,7 @@
</div> </div>
</header> </header>
<p><img src="/images/supported_brands/glances.png" style="border:none; box-shadow: none; float: right;" height="80" /> <p><img src="/images/supported_brands/glances.png" style="border:none; box-shadow: none; float: right;" height="80" />
Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p> Inspired by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p>
<a name="read-more"></a> <a name="read-more"></a>
<p>The basic problem is to get the data from the remote host. Starting with <a href="https://pypi.python.org/pypi/psutil">psutil</a> that is used by the systemmonitor sensor, a possible solution is only a click away and named <a href="https://github.com/nicolargo/glances">Glances</a>. Glances has a nice curses-based interface and a <a href="https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API">RESTful API</a>.</p> <p>The basic problem is to get the data from the remote host. Starting with <a href="https://pypi.python.org/pypi/psutil">psutil</a> that is used by the systemmonitor sensor, a possible solution is only a click away and named <a href="https://github.com/nicolargo/glances">Glances</a>. Glances has a nice curses-based interface and a <a href="https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API">RESTful API</a>.</p>
<p>The <a href="/components/sensor.glances/">Glances sensor</a> sensor uses that API to get all needed data.</p> <p>The <a href="/components/sensor.glances/">Glances sensor</a> sensor uses that API to get all needed data.</p>

8
blog/2016/04/17/updated-documentation/index.html
View file

@ -8,7 +8,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Updated documentation - Home Assistant</title> <title>Updated documentation - Home Assistant</title>
<meta name="author" content="Paulus Schoutsen"> <meta name="author" content="Paulus Schoutsen">
<meta name="description" content="We have reorganised our documentation which should make it easier to get started and develop for Home Assistant."> <meta name="description" content="We have reorganized our documentation which should make it easier to get started and develop for Home Assistant.">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/blog/2016/04/17/updated-documentation/"> <link rel="canonical" href="https://home-assistant.io/blog/2016/04/17/updated-documentation/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
@ -16,13 +16,13 @@
<meta property="og:site_name" content="Home Assistant"> <meta property="og:site_name" content="Home Assistant">
<meta property="og:url" content="https://home-assistant.io/blog/2016/04/17/updated-documentation/"> <meta property="og:url" content="https://home-assistant.io/blog/2016/04/17/updated-documentation/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="We have reorganised our documentation which should make it easier to get started and develop for Home Assistant."> <meta property="og:description" content="We have reorganized our documentation which should make it easier to get started and develop for Home Assistant.">
<meta property="og:image" content="https://home-assistant.io/images/default-social.png"> <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
<meta name="twitter:card" content="summary_large_image"> <meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@home_assistant"> <meta name="twitter:site" content="@home_assistant">
<meta name="twitter:creator" content="@balloob"> <meta name="twitter:creator" content="@balloob">
<meta name="twitter:title" content="Updated documentation"> <meta name="twitter:title" content="Updated documentation">
<meta name="twitter:description" content="We have reorganised our documentation which should make it easier to get started and develop for Home Assistant."> <meta name="twitter:description" content="We have reorganized our documentation which should make it easier to get started and develop for Home Assistant.">
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png"> <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet"> <link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml"> <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
@ -88,7 +88,7 @@
</header> </header>
<p>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 <a href="/getting-started/">getting started</a> and <a href="/developers/">developers</a> sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.</p> <p>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 <a href="/getting-started/">getting started</a> and <a href="/developers/">developers</a> sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.</p>
<p>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 <a href="/blog/2014/12/18/website-launched/">called it a website</a>. Back then we had a whopping <a href="https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown">11 components</a>.</p> <p>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 <a href="/blog/2014/12/18/website-launched/">called it a website</a>. Back then we had a whopping <a href="https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown">11 components</a>.</p>
<p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> 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 <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organisation.</p> <p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> 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 <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organization.</p>
<p>Today it has been almost 1.5 years since we started the website. We now have <a href="/components/">264 components and platforms</a> under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.</p> <p>Today it has been almost 1.5 years since we started the website. We now have <a href="/components/">264 components and platforms</a> under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.</p>
<p>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.</p> <p>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.</p>
</article> </article>

4
blog/2016/04/19/to-infinity-and-beyond/index.html
View file

@ -78,7 +78,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'
@ -86,7 +86,7 @@
>Comments</a> >Comments</a>
</div> </div>
</header> </header>
<p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organisation on GitHub</a>.</p> <p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organization on GitHub</a>.</p>
<p>On our journey we’ve reached many noteworthy milestones:</p> <p>On our journey we’ve reached many noteworthy milestones:</p>
<ul> <ul>
<li>#1 on HackerNews</li> <li>#1 on HackerNews</li>

4
blog/2016/04/20/bluetooth-lg-webos-tvs-and-roombas/index.html
View file

@ -86,8 +86,8 @@
>Comments</a> >Comments</a>
</div> </div>
</header> </header>
<p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.</p> <p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.</p>
<p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organisation on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p> <p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organization on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p>
<p><a href="/demo/"><img src="/images/blog/2016-04-release-18/media_player.png" style="box-shadow: none; border: 0;" /></a></p> <p><a href="/demo/"><img src="/images/blog/2016-04-release-18/media_player.png" style="box-shadow: none; border: 0;" /></a></p>
<p><img src="/images/supported_brands/bluetooth.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/webos.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/rss.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/eq3.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/thinkingcleaner.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p> <p><img src="/images/supported_brands/bluetooth.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/webos.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/rss.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/eq3.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/thinkingcleaner.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
<ul> <ul>

4
blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
View file

@ -93,11 +93,11 @@
<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> <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><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> <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> <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>
<p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p> <p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p>
<a name="read-more"></a> <a name="read-more"></a>
<h3><a class="title-link" name="getting-started" href="#getting-started"></a> 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>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> <p>You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.</p>
<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> <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> <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>
<p><strong>Example <code class="highlighter-rouge">configuration.yaml</code> entry</strong></p> <p><strong>Example <code class="highlighter-rouge">configuration.yaml</code> entry</strong></p>

2
blog/2016/06/23/usb-webcams-and-home-assistant/index.html
View file

@ -103,7 +103,7 @@ crw-rw----+ 1 root video 81, 0 Jun 23 08:05 /dev/video0
crw-rw----+ 1 root video 81, 1 Jun 23 08:36 /dev/video1 crw-rw----+ 1 root video 81, 1 Jun 23 08:36 /dev/video1
</code></pre> </code></pre>
</div> </div>
<p>We need an additional software part to handle the cameras. <a href="http://lavrsen.dk/foswiki/bin/view/Motion/WebHome">motion</a> is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the <a href="http://rpmfusion.org/">RPM Fusion respository</a> enabled.</p> <p>We need an additional software part to handle the cameras. <a href="http://lavrsen.dk/foswiki/bin/view/Motion/WebHome">motion</a> is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the <a href="http://rpmfusion.org/">RPM Fusion repository</a> enabled.</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo dnf -y install motion <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo dnf -y install motion
</code></pre> </code></pre>
</div> </div>

2
blog/2016/07/19/visualizing-your-iot-data/index.html
View file

@ -157,7 +157,7 @@ SQLite version 3.11.0 2016-02-15 17:29:24
<span class="n">plt</span><span class="o">.</span><span class="n">savefig</span><span class="p">(</span><span class="s">'sensor.png'</span><span class="p">)</span> <span class="n">plt</span><span class="o">.</span><span class="n">savefig</span><span class="p">(</span><span class="s">'sensor.png'</span><span class="p">)</span>
</code></pre> </code></pre>
</div> </div>
<p>Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are splitted into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.</p> <p>Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are split into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.</p>
<p class="img"> <p class="img">
<img src="/images/blog/2016-07-reporting/mpl-sensor.png" /> <img src="/images/blog/2016-07-reporting/mpl-sensor.png" />
Sensor graph generated by matplotlib Sensor graph generated by matplotlib

2
blog/2016/07/30/custom-frontend-panels-jupyter-notebooks-directv/index.html
View file

@ -87,7 +87,7 @@
</div> </div>
</header> </header>
<p>When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!</p> <p>When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!</p>
<p>Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p> <p>Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p>
<p>We have also seen an exciting trend of people starting to visualize their Internet of Things data using <a href="http://jupyter.org/">Jupyter</a> Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the <a href="/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/">blog</a> post by <a href="https://github.com/kireyeu">@kireyeu</a> shows an advanced usecase while our <a href="/cookbook/#jupyter-notebooks">Notebooks</a> in the <a href="https://github.com/home-assistant/home-assistant-notebooks">Home Assistant Notebooks repository</a> cover the basics.</p> <p>We have also seen an exciting trend of people starting to visualize their Internet of Things data using <a href="http://jupyter.org/">Jupyter</a> Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the <a href="/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/">blog</a> post by <a href="https://github.com/kireyeu">@kireyeu</a> shows an advanced usecase while our <a href="/cookbook/#jupyter-notebooks">Notebooks</a> in the <a href="https://github.com/home-assistant/home-assistant-notebooks">Home Assistant Notebooks repository</a> cover the basics.</p>
<p>This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!</p> <p>This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!</p>
<p>The brand-new <a href="/components/panel_iframe/">iFrame panel component</a> allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.</p> <p>The brand-new <a href="/components/panel_iframe/">iFrame panel component</a> allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.</p>

4
blog/2016/08/07/optimizing-the-home-assistant-mobile-web-app/index.html
View file

@ -91,11 +91,11 @@
<p>Do less and be lazy. It sounds so obvious and it took a while before it started to dawn on me. I think most of the code I write is pretty fast, but I don’t often stop to take a harder look at how and when it runs in practice. When do we need the result, can it be postponed?</p> <p>Do less and be lazy. It sounds so obvious and it took a while before it started to dawn on me. I think most of the code I write is pretty fast, but I don’t often stop to take a harder look at how and when it runs in practice. When do we need the result, can it be postponed?</p>
<p>And thus started my journey to take a critical look at how the Home Assistant app was working and how to make things faster. Below is the list of the different things that I did to make it fast.</p> <p>And thus started my journey to take a critical look at how the Home Assistant app was working and how to make things faster. Below is the list of the different things that I did to make it fast.</p>
<p>I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.</p> <p>I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.</p>
<p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 miliseconds and on my Nexus 5x in ~6500 miliseconds (~4.5 times slower!).</strong></p> <p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 milliseconds and on my Nexus 5x in ~6500 milliseconds (~4.5 times slower!).</strong></p>
<p class="img"> <p class="img">
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.18.2.png" alt="Timeline of loading the front end in Home Assistant 0.18.2" /> <img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.18.2.png" alt="Timeline of loading the front end in Home Assistant 0.18.2" />
</p> </p>
<p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 miliseconds (-35%) on my Mac and 2400 miliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p> <p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 milliseconds (-35%) on my Mac and 2400 milliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p>
<p class="img"> <p class="img">
<img src="/images/blog/2016-08-optimizing-web-app/performance-diagram.png" alt="diagram showing old and new loading times next to one another" /> <img src="/images/blog/2016-08-optimizing-web-app/performance-diagram.png" alt="diagram showing old and new loading times next to one another" />
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.26.png" alt="Timeline of loading the front end in Home Assistant 0.26" /> <img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.26.png" alt="Timeline of loading the front end in Home Assistant 0.26" />

4
blog/2016/09/10/notify-group-reload-api-pihole/index.html
View file

@ -97,9 +97,9 @@
<h3><a class="title-link" name="climate-and--cover" href="#climate-and--cover"></a> Climate and cover</h3> <h3><a class="title-link" name="climate-and--cover" href="#climate-and--cover"></a> Climate and cover</h3>
<p>There are countless bugfixes included in this release which will make your experience with the <code class="highlighter-rouge">climate</code> and the <code class="highlighter-rouge">cover</code> platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/djbanks">@djbanks</a>, <a href="https://github.com/danielperna84">@danielperna84</a>, and others the improvements on the code and the frontend side is continuing…</p> <p>There are countless bugfixes included in this release which will make your experience with the <code class="highlighter-rouge">climate</code> and the <code class="highlighter-rouge">cover</code> platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/djbanks">@djbanks</a>, <a href="https://github.com/danielperna84">@danielperna84</a>, and others the improvements on the code and the frontend side is continuing…</p>
<h3><a class="title-link" name="api-documentation" href="#api-documentation"></a> API documentation</h3> <h3><a class="title-link" name="api-documentation" href="#api-documentation"></a> API documentation</h3>
<p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p> <p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p>
<h3><a class="title-link" name="configuration-validation" href="#configuration-validation"></a> Configuration validation</h3> <h3><a class="title-link" name="configuration-validation" href="#configuration-validation"></a> Configuration validation</h3>
<p>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 <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p> <p>The validation of the configuration is still on-going. Approximately 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 <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p>
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3> <h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
<p><img src="/images/supported_brands/xbox-live.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/automatic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/pi_hole.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p> <p><img src="/images/supported_brands/xbox-live.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/automatic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/pi_hole.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
<ul> <ul>

6
blog/2016/10/01/we-have-raspberry-image-now/index.html
View file

@ -8,7 +8,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>We have a Raspberry Pi image now - Home Assistant</title> <title>We have a Raspberry Pi image now - Home Assistant</title>
<meta name="author" content="Fredrik Lindqvist"> <meta name="author" content="Fredrik Lindqvist">
<meta name="description" content="Release of the Rapsberry Pi Image for Home Assistant"> <meta name="description" content="Release of the Raspberry Pi Image for Home Assistant">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/blog/2016/10/01/we-have-raspberry-image-now/"> <link rel="canonical" href="https://home-assistant.io/blog/2016/10/01/we-have-raspberry-image-now/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
@ -16,12 +16,12 @@
<meta property="og:site_name" content="Home Assistant"> <meta property="og:site_name" content="Home Assistant">
<meta property="og:url" content="https://home-assistant.io/blog/2016/10/01/we-have-raspberry-image-now/"> <meta property="og:url" content="https://home-assistant.io/blog/2016/10/01/we-have-raspberry-image-now/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="Release of the Rapsberry Pi Image for Home Assistant"> <meta property="og:description" content="Release of the Raspberry Pi Image for Home Assistant">
<meta property="og:image" content="https://home-assistant.io/images/blog/2016-10-hassbian/social.png"> <meta property="og:image" content="https://home-assistant.io/images/blog/2016-10-hassbian/social.png">
<meta name="twitter:card" content="summary_large_image"> <meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@home_assistant"> <meta name="twitter:site" content="@home_assistant">
<meta name="twitter:title" content="We have a Raspberry Pi image now"> <meta name="twitter:title" content="We have a Raspberry Pi image now">
<meta name="twitter:description" content="Release of the Rapsberry Pi Image for Home Assistant"> <meta name="twitter:description" content="Release of the Raspberry Pi Image for Home Assistant">
<meta name="twitter:image" content="https://home-assistant.io/images/blog/2016-10-hassbian/social.png"> <meta name="twitter:image" content="https://home-assistant.io/images/blog/2016-10-hassbian/social.png">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet"> <link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml"> <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

2
blog/2016/10/02/hacktoberfest/index.html
View file

@ -86,7 +86,7 @@
>Comments</a> >Comments</a>
</div> </div>
</header> </header>
<p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p> <p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organized by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p>
<p>Why contribute to Home Assistant:</p> <p>Why contribute to Home Assistant:</p>
<ul> <ul>
<li>Written in Python3 with 94% test coverage</li> <li>Written in Python3 with 94% test coverage</li>

2
blog/2016/10/25/explaining-the-updater/index.html
View file

@ -78,7 +78,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'

2
blog/2017/01/21/home-assistant-governance/index.html
View file

@ -78,7 +78,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'

2
blog/2017/01/28/face-coffee-wink/index.html
View file

@ -182,7 +182,7 @@
<li>Switch - Pilight: Implement echo config option (<a href="https://github.com/janLo">@janLo</a>)</li> <li>Switch - Pilight: Implement echo config option (<a href="https://github.com/janLo">@janLo</a>)</li>
<li>Core: Support customize in packages (<a href="https://github.com/kellerza">@kellerza</a>)</li> <li>Core: Support customize in packages (<a href="https://github.com/kellerza">@kellerza</a>)</li>
<li>Switch - Flux: Allow disabling setting the brightness (<a href="https://github.com/rytilahti">@rytilahti</a>)</li> <li>Switch - Flux: Allow disabling setting the brightness (<a href="https://github.com/rytilahti">@rytilahti</a>)</li>
<li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no emtpy image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li> <li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no empty image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li>
<li>Climate: Hold mode (<a href="https://github.com/Duoxilian">@Duoxilian</a>)</li> <li>Climate: Hold mode (<a href="https://github.com/Duoxilian">@Duoxilian</a>)</li>
<li>Switch - TPlink: No longer doing I/O in event bus (<a href="https://github.com/balloob">@balloob</a>)</li> <li>Switch - TPlink: No longer doing I/O in event bus (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Light - Insteon local: Improve Insteon configuration (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li> <li>Light - Insteon local: Improve Insteon configuration (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li>

2
blog/2017/03/11/repurpose-any-android-phone-as-ip-camera/index.html
View file

@ -250,7 +250,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
<li>Add multi contracts support for Hydroquebec (<a href="https://github.com/titilambert">@titilambert</a>)</li> <li>Add multi contracts support for Hydroquebec (<a href="https://github.com/titilambert">@titilambert</a>)</li>
<li>Add Zwave refresh services (<a href="https://github.com/andrey-git">@andrey-git</a>)</li> <li>Add Zwave refresh services (<a href="https://github.com/andrey-git">@andrey-git</a>)</li>
<li>Add keep-alive feature to the generic thermostat (<a href="https://github.com/aronsky">@aronsky</a>)</li> <li>Add keep-alive feature to the generic thermostat (<a href="https://github.com/aronsky">@aronsky</a>)</li>
<li>Fix wake_on_lan for german version of Windows 10 (#6397) (<a href="https://github.com/siebert">@siebert</a>)</li> <li>Fix wake_on_lan for German version of Windows 10 (#6397) (<a href="https://github.com/siebert">@siebert</a>)</li>
<li>flux led lib (<a href="https://github.com/danielhiversen">@danielhiversen</a>)</li> <li>flux led lib (<a href="https://github.com/danielhiversen">@danielhiversen</a>)</li>
<li>Cleanup async handling (<a href="https://github.com/pvizeli">@pvizeli</a>)</li> <li>Cleanup async handling (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
<li>Restore for automation entities (<a href="https://github.com/kellerza">@kellerza</a>)</li> <li>Restore for automation entities (<a href="https://github.com/kellerza">@kellerza</a>)</li>

2
blog/2017/04/01/thomas-krenn-award/index.html
View file

@ -97,7 +97,7 @@
<li>Dead line: April, 23 2017 - 23.59 UTC</li> <li>Dead line: April, 23 2017 - 23.59 UTC</li>
<li>Voting period: April, 24th till April, 30 2017 - 23.59 UTC</li> <li>Voting period: April, 24th till April, 30 2017 - 23.59 UTC</li>
</ul> </ul>
<p>The decision of the jury will be final. If there will be a dispute then the Top-5 commiter of the Home Assistant organisation on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p> <p>The decision of the jury will be final. If there will be a dispute then the Top-5 committer of the Home Assistant organization on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p>
<p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p> <p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p>
</article> </article>
<section id="disqus"> <section id="disqus">

2
blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/index.html
View file

@ -103,7 +103,7 @@
<h2>Breaking changes</h2> <h2>Breaking changes</h2>
<ul> <ul>
<li>We were incorrectly treating groups named <code class="highlighter-rouge">default_view</code> as default views. Make sure you set <code class="highlighter-rouge">view: true</code> in the config for these groups. <a href="https://github.com/home-assistant/home-assistant-polymer/pull/251">#251 (frontend)</a></li> <li>We were incorrectly treating groups named <code class="highlighter-rouge">default_view</code> as default views. Make sure you set <code class="highlighter-rouge">view: true</code> in the config for these groups. <a href="https://github.com/home-assistant/home-assistant-polymer/pull/251">#251 (frontend)</a></li>
<li>The last release introduced a revamped LIFX platform. We only realised after deploy that this version does not work on Windows. We have added the old LIFX implementation back as <code class="highlighter-rouge">lifx_legacy</code>.</li> <li>The last release introduced a revamped LIFX platform. We only realized after deploy that this version does not work on Windows. We have added the old LIFX implementation back as <code class="highlighter-rouge">lifx_legacy</code>.</li>
<li>We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. <a href="https://github.com/home-assistant/home-assistant/pull/6688">#6688</a></li> <li>We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. <a href="https://github.com/home-assistant/home-assistant/pull/6688">#6688</a></li>
<li>Z-Wave cover workaround has been removed. Use device config instead. <a href="https://github.com/home-assistant/home-assistant/pull/6832">#6832</a></li> <li>Z-Wave cover workaround has been removed. Use device config instead. <a href="https://github.com/home-assistant/home-assistant/pull/6832">#6832</a></li>
</ul> </ul>

2
blog/2017/04/15/ios/index.html
View file

@ -93,7 +93,7 @@
<p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p> <p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p>
<p>I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.</p> <p>I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.</p>
<p>I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.</p> <p>I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.</p>
<p>It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p> <p>It may not look the way that I wanted it to initially, with beautiful native UI components, but that’s okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p>
<p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p> <p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p>
<p>The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.</p> <p>The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.</p>
<p>The app is <a href="https://github.com/home-assistant/home-assistant-iOS">open source</a>, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.</p> <p>The app is <a href="https://github.com/home-assistant/home-assistant-iOS">open source</a>, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.</p>

2
blog/2017/04/30/hassbian-1.21-its-about-time/index.html
View file

@ -93,7 +93,7 @@
<h3><a class="title-link" name="hassbian-config" href="#hassbian-config"></a> Hassbian-config</h3> <h3><a class="title-link" name="hassbian-config" href="#hassbian-config"></a> Hassbian-config</h3>
<p>To allow you to customize your installation further, we have included a tool called <code class="highlighter-rouge">hassbian-config</code>. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the <code class="highlighter-rouge">hassbian-scripts</code> functionality from 1.1.</p> <p>To allow you to customize your installation further, we have included a tool called <code class="highlighter-rouge">hassbian-config</code>. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the <code class="highlighter-rouge">hassbian-scripts</code> functionality from 1.1.</p>
<ul> <ul>
<li>Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.</li> <li>Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that’s used with Amazon Echo, Google Home and Mycroft.ai.</li>
<li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li> <li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li>
<li>Install Libcec. Adds local <a href="/components/hdmi_cec/">HDMI CEC support</a>.</li> <li>Install Libcec. Adds local <a href="/components/hdmi_cec/">HDMI CEC support</a>.</li>
<li>Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.</li> <li>Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.</li>

2
blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/index.html
View file

@ -90,7 +90,7 @@
<img src="/images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png" /> <img src="/images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png" />
</p> </p>
<p>Saw the <a href="/blog/2017/04/30/hassbian-1.21-its-about-time/">announcement</a> yesterday for HASSbian 1.21 and got super excited?</p> <p>Saw the <a href="/blog/2017/04/30/hassbian-1.21-its-about-time/">announcement</a> yesterday for HASSbian 1.21 and got super excited?</p>
<p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspbery Pi Zero W</a>. <p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspberry Pi Zero W</a>.
<strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p> <strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p>
<p>What you’ll need:</p> <p>What you’ll need:</p>
<ul> <ul>

2
blog/2017/09/09/release-53/index.html
View file

@ -110,7 +110,7 @@ Screenshot of the new customize editor.
<h2><a class="title-link" name="input-text" href="#input-text"></a> Input text</h2> <h2><a class="title-link" name="input-text" href="#input-text"></a> Input text</h2>
<p>This release introduces a new input component: <code class="highlighter-rouge">input_text</code> contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.</p> <p>This release introduces a new input component: <code class="highlighter-rouge">input_text</code> contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.</p>
<h2><a class="title-link" name="knx" href="#knx"></a> KNX</h2> <h2><a class="title-link" name="knx" href="#knx"></a> KNX</h2>
<p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p> <p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunneling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p>
<div class="videoWrapper"> <div class="videoWrapper">
<iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen=""></iframe> <iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen=""></iframe>
</div> </div>

2
blog/2017/11/12/tor/index.html
View file

@ -97,7 +97,7 @@
<p>The most amazing part? It is super easy to set up!</p> <p>The most amazing part? It is super easy to set up!</p>
<a name="read-more"></a> <a name="read-more"></a>
<h2><a class="title-link" name="setting-up-tor" href="#setting-up-tor"></a> Setting up Tor</h2> <h2><a class="title-link" name="setting-up-tor" href="#setting-up-tor"></a> Setting up Tor</h2>
<p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailled guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p> <p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailed guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p>
<ol> <ol>
<li>Install Tor. On a Debian-based system: <code class="highlighter-rouge">$ sudo apt-get install tor</code>. On Fedora: <code class="highlighter-rouge">$ sudo dnf install tor</code></li> <li>Install Tor. On a Debian-based system: <code class="highlighter-rouge">$ sudo apt-get install tor</code>. On Fedora: <code class="highlighter-rouge">$ sudo dnf install tor</code></li>
<li> <li>

2
blog/2017/11/18/release-58/index.html
View file

@ -91,7 +91,7 @@
The Hass.io release of 0.58 will be delayed by a couple of days because Pascal is moving this weekend. The Hass.io release of 0.58 will be delayed by a couple of days because Pascal is moving this weekend.
</p> </p>
<h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2> <h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2>
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.</p> <p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.</p>
<p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p> <p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p>
<p>And because more translations is more better, <a href="https://github.com/robbiet480">@robbiet480</a> has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.</p> <p>And because more translations is more better, <a href="https://github.com/robbiet480">@robbiet480</a> has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.</p>
<p><a href="https://home-assistant.io/blog/2017/11/05/frontend-translations/">Learn more about how to help with translations</a></p> <p><a href="https://home-assistant.io/blog/2017/11/05/frontend-translations/">Learn more about how to help with translations</a></p>

4
blog/2017/12/03/release-59/index.html
View file

@ -97,12 +97,12 @@
Screenshot of the color wheel. Screenshot of the color wheel.
</p> </p>
<h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2> <h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2>
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editting has been made easier.</p> <p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editing has been made easier.</p>
<h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2> <h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2>
<p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p> <p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p>
<p class="img"> <p class="img">
<img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." /> <img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." />
Screenshot of the of the Enitity Picker. Screenshot of the of the Entity Picker.
</p> </p>
<h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2> <h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2>
<p>If you follow our <a href="https://twitter.com/home_assistant">twitter feed</a> then you may already know that <a href="https://github.com/frenck">@frenck</a> spent some time to bring new stuff to the <a href="https://github.com/hassio-addons/repository">Community Hass.io Add-ons repository</a>.</p> <p>If you follow our <a href="https://twitter.com/home_assistant">twitter feed</a> then you may already know that <a href="https://github.com/frenck">@frenck</a> spent some time to bring new stuff to the <a href="https://github.com/hassio-addons/repository">Community Hass.io Add-ons repository</a>.</p>

8
blog/archives/index.html
View file

@ -280,7 +280,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -1212,7 +1212,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -1961,7 +1961,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -2151,7 +2151,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>

4
blog/categories/announcements/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Announcements | Home Assistant]]></title> <title><![CDATA[Category: Announcements | Home Assistant]]></title>
<link href="https://home-assistant.io/blog/categories/announcements/atom.xml" rel="self"/> <link href="https://home-assistant.io/blog/categories/announcements/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -227,7 +227,7 @@ I received emails and forum posts almost every day, even when the app would go w
I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink. I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant. It may not look the way that I wanted it to initially, with beautiful native UI components, but that's okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
Just because the app is released doesn't mean we are at the end of the road. It's only the beginning. There's plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that's pretty hard with how fast the project moves. Just because the app is released doesn't mean we are at the end of the road. It's only the beginning. There's plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that's pretty hard with how fast the project moves.

2
blog/categories/community/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Community | Home Assistant]]></title> <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/blog/categories/community/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

2
blog/categories/device-tracking/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Device-Tracking | Home Assistant]]></title> <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/blog/categories/device-tracking/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

2
blog/categories/esp8266/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: ESP8266 | Home Assistant]]></title> <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/blog/categories/esp8266/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

4
blog/categories/how-to/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: How-To | Home Assistant]]></title> <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/blog/categories/how-to/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -181,7 +181,7 @@ The most amazing part? It is super easy to set up!
## <a class='title-link' name='setting-up-tor' href='#setting-up-tor'></a> Setting up Tor ## <a class='title-link' name='setting-up-tor' href='#setting-up-tor'></a> Setting up Tor
Our [documentation](/docs/ecosystem/tor/) provides an detailled guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward: Our [documentation](/docs/ecosystem/tor/) provides an detailed guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor` 1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor`
2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines: 2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines:

6
blog/categories/ibeacons/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: iBeacons | Home Assistant]]></title> <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/blog/categories/ibeacons/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -183,7 +183,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
When you use OwnTracks in standard _major move_ 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! When you use OwnTracks in standard _major move_ 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!
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon. Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
<!--more--> <!--more-->
@ -194,7 +194,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
[MQTT]: /components/mqtt/#picking-a-broker [MQTT]: /components/mqtt/#picking-a-broker
[OwnTracks]: /components/device_tracker.owntracks/ [OwnTracks]: /components/device_tracker.owntracks/
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon. You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
#### <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 #### <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

2
blog/categories/internet-of-things/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Internet-of-Things | Home Assistant]]></title> <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/blog/categories/internet-of-things/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

4
blog/categories/iot-data/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: IoT-Data | Home Assistant]]></title> <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/blog/categories/iot-data/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -205,7 +205,7 @@ plt.xlabel('Time line')
plt.savefig('sensor.png') plt.savefig('sensor.png')
``` ```
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are splitted into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image. Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are split into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
<p class='img'> <p class='img'>
<img src='/images/blog/2016-07-reporting/mpl-sensor.png' /> <img src='/images/blog/2016-07-reporting/mpl-sensor.png' />

2
blog/categories/media/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Media | Home Assistant]]></title> <title><![CDATA[Category: Media | Home Assistant]]></title>
<link href="https://home-assistant.io/blog/categories/media/atom.xml" rel="self"/> <link href="https://home-assistant.io/blog/categories/media/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

2
blog/categories/merchandise/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Merchandise | Home Assistant]]></title> <title><![CDATA[Category: Merchandise | Home Assistant]]></title>
<link href="https://home-assistant.io/blog/categories/merchandise/atom.xml" rel="self"/> <link href="https://home-assistant.io/blog/categories/merchandise/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

2
blog/categories/micropython/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Micropython | Home Assistant]]></title> <title><![CDATA[Category: Micropython | Home Assistant]]></title>
<link href="https://home-assistant.io/blog/categories/micropython/atom.xml" rel="self"/> <link href="https://home-assistant.io/blog/categories/micropython/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

4
blog/categories/mqtt/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: MQTT | Home Assistant]]></title> <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/blog/categories/mqtt/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -673,7 +673,7 @@ char* deviceId = "sensor01"; // Name of the sensor
char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published
int sensorPin = A0; // Pin to which the sensor is connected to int sensorPin = A0; // Pin to which the sensor is connected to
char buf[4]; // Buffer to store the sensor value char buf[4]; // Buffer to store the sensor value
int updateInterval = 1000; // Interval in miliseconds int updateInterval = 1000; // Interval in milliseconds
// MQTT server settings // MQTT server settings
IPAddress mqttServer(192, 168, 0, 12); IPAddress mqttServer(192, 168, 0, 12);

8
blog/categories/organisation/atom.xml → blog/categories/organization/atom.xml
View file

@ -1,10 +1,10 @@
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"> <feed xmlns="http://www.w3.org/2005/Atom">
<title><![CDATA[Category: Organisation | Home Assistant]]></title> <title><![CDATA[Category: Organization | Home Assistant]]></title>
<link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/> <link href="https://home-assistant.io/blog/categories/organization/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -173,7 +173,7 @@ The source code of our updater AWS Lambda function is now available [here][sourc
<link href="https://home-assistant.io/blog/2016/04/19/to-infinity-and-beyond/"/> <link href="https://home-assistant.io/blog/2016/04/19/to-infinity-and-beyond/"/>
<updated>2016-04-19T22:44:00+00:00</updated> <updated>2016-04-19T22:44:00+00:00</updated>
<id>https://home-assistant.io/blog/2016/04/19/to-infinity-and-beyond</id> <id>https://home-assistant.io/blog/2016/04/19/to-infinity-and-beyond</id>
<content type="html"><![CDATA[After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organisation on GitHub][gh-ha]. <content type="html"><![CDATA[After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organization on GitHub][gh-ha].
On our journey we've reached many noteworthy milestones: On our journey we've reached many noteworthy milestones:

34
blog/categories/organisation/index.html → blog/categories/organization/index.html
View file

@ -6,22 +6,22 @@
<head> <head>
<meta charset="utf-8"> <meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Category: Organisation - Home Assistant</title> <title>Category: Organization - Home Assistant</title>
<meta name="author" content="Home Assistant"> <meta name="author" content="Home Assistant">
<meta name="description" content="Category: Organisation"> <meta name="description" content="Category: Organization">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/blog/categories/organisation/"> <link rel="canonical" href="https://home-assistant.io/blog/categories/organization/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
<meta property="og:title" content="Category: Organisation"> <meta property="og:title" content="Category: Organization">
<meta property="og:site_name" content="Home Assistant"> <meta property="og:site_name" content="Home Assistant">
<meta property="og:url" content="https://home-assistant.io/blog/categories/organisation/"> <meta property="og:url" content="https://home-assistant.io/blog/categories/organization/">
<meta property="og:type" content="website"> <meta property="og:type" content="website">
<meta property="og:description" content="Category: Organisation"> <meta property="og:description" content="Category: Organization">
<meta property="og:image" content="https://home-assistant.io/images/default-social.png"> <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
<meta name="twitter:card" content="summary_large_image"> <meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@home_assistant"> <meta name="twitter:site" content="@home_assistant">
<meta name="twitter:title" content="Category: Organisation"> <meta name="twitter:title" content="Category: Organization">
<meta name="twitter:description" content="Category: Organisation"> <meta name="twitter:description" content="Category: Organization">
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png"> <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet"> <link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml"> <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
@ -68,10 +68,10 @@
<div class="grid grid-center"> <div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole"> <div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="page"> <article class="page">
<div class='edit-github'><a href='https://github.com/home-assistant/home-assistant.github.io/tree/current/source/blog/categories/organisation/index.html'>Edit this page on GitHub</a></div> <div class='edit-github'><a href='https://github.com/home-assistant/home-assistant.github.io/tree/current/source/blog/categories/organization/index.html'>Edit this page on GitHub</a></div>
<header> <header>
<h1 class="title indent"> <h1 class="title indent">
Category: Organisation Category: Organization
</h1> </h1>
</header> </header>
<hr class="divider"> <hr class="divider">
@ -90,7 +90,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -112,7 +112,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -133,7 +133,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -155,7 +155,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
</footer> </footer>
@ -189,10 +189,10 @@
class="twitter-share-button" class="twitter-share-button"
data-via="home_assistant" data-via="home_assistant"
data-related="home_assistant" data-related="home_assistant"
data-url="https://home-assistant.io/blog/categories/organisation/" data-url="https://home-assistant.io/blog/categories/organization/"
data-counturl="https://home-assistant.io/blog/categories/organisation/" >Tweet</a> data-counturl="https://home-assistant.io/blog/categories/organization/" >Tweet</a>
<div class="fb-share-button" style='top: -6px;' <div class="fb-share-button" style='top: -6px;'
data-href="https://home-assistant.io/blog/categories/organisation/" data-href="https://home-assistant.io/blog/categories/organization/"
data-layout="button_count"> data-layout="button_count">
</div> </div>
<div class="g-plusone" data-size="standard"></div> <div class="g-plusone" data-size="standard"></div>

6
blog/categories/owntracks/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: OwnTracks | Home Assistant]]></title> <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/blog/categories/owntracks/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -183,7 +183,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
When you use OwnTracks in standard _major move_ 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! When you use OwnTracks in standard _major move_ 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!
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon. Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
<!--more--> <!--more-->
@ -194,7 +194,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
[MQTT]: /components/mqtt/#picking-a-broker [MQTT]: /components/mqtt/#picking-a-broker
[OwnTracks]: /components/device_tracker.owntracks/ [OwnTracks]: /components/device_tracker.owntracks/
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon. You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
#### <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 #### <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

6
blog/categories/presence-detection/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Presence-Detection | Home Assistant]]></title> <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/blog/categories/presence-detection/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -28,7 +28,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
When you use OwnTracks in standard _major move_ 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! When you use OwnTracks in standard _major move_ 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!
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon. Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
<!--more--> <!--more-->
@ -39,7 +39,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
[MQTT]: /components/mqtt/#picking-a-broker [MQTT]: /components/mqtt/#picking-a-broker
[OwnTracks]: /components/device_tracker.owntracks/ [OwnTracks]: /components/device_tracker.owntracks/
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon. You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
#### <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 #### <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

2
blog/categories/public-service-announcement/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title> <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/blog/categories/public-service-announcement/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

8
blog/categories/release-notes/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Release-Notes | Home Assistant]]></title> <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/blog/categories/release-notes/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -1229,14 +1229,14 @@ With the Dominos Pizza integration made by [@wardcraigj] your home is now taking
</p> </p>
## <a class='title-link' name='shopping-list-tweaks' href='#shopping-list-tweaks'></a> Shopping list tweaks ## <a class='title-link' name='shopping-list-tweaks' href='#shopping-list-tweaks'></a> Shopping list tweaks
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editting has been made easier. [@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editing has been made easier.
## <a class='title-link' name='entity-picker' href='#entity-picker'></a> Entity picker ## <a class='title-link' name='entity-picker' href='#entity-picker'></a> Entity picker
[@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities. [@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities.
<p class='img'> <p class='img'>
<img src='/images/blog/2017-12-0.59/picker.png' alt='Screenshot of the Entity Picker.'> <img src='/images/blog/2017-12-0.59/picker.png' alt='Screenshot of the Entity Picker.'>
Screenshot of the of the Enitity Picker. Screenshot of the of the Entity Picker.
</p> </p>
## <a class='title-link' name='hassio-add-ons' href='#hassio-add-ons'></a> Hass.io Add-ons ## <a class='title-link' name='hassio-add-ons' href='#hassio-add-ons'></a> Hass.io Add-ons
@ -1647,7 +1647,7 @@ The Hass.io release of 0.58 will be delayed by a couple of days because Pascal i
## <a class='title-link' name='translation-update' href='#translation-update'></a> Translation update ## <a class='title-link' name='translation-update' href='#translation-update'></a> Translation update
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated. Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.
Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks! Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!

2
blog/categories/survey/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Survey | Home Assistant]]></title> <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/blog/categories/survey/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

2
blog/categories/talks/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Talks | Home Assistant]]></title> <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/blog/categories/talks/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

4
blog/categories/technology/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Technology | Home Assistant]]></title> <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/blog/categories/technology/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -163,7 +163,7 @@ With the release of 1.21 a small problem with the OpenZWave build script wasn't
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the `hassbian-scripts` functionality from 1.1. To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the `hassbian-scripts` functionality from 1.1.
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai. - Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that's used with Amazon Echo, Google Home and Mycroft.ai.
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support. - Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
- Install Libcec. Adds local [HDMI CEC support][cec]. - Install Libcec. Adds local [HDMI CEC support][cec].
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed. - Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.

2
blog/categories/user-stories/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: User-Stories | Home Assistant]]></title> <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/blog/categories/user-stories/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

2
blog/categories/video/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Video | Home Assistant]]></title> <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/blog/categories/video/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>

4
blog/categories/website/atom.xml
View file

@ -4,7 +4,7 @@
<title><![CDATA[Category: Website | Home Assistant]]></title> <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/blog/categories/website/atom.xml" rel="self"/>
<link href="https://home-assistant.io/"/> <link href="https://home-assistant.io/"/>
<updated>2018-01-24T13:02:59+00:00</updated> <updated>2018-01-25T17:24:11+00:00</updated>
<id>https://home-assistant.io/</id> <id>https://home-assistant.io/</id>
<author> <author>
<name><![CDATA[Home Assistant]]></name> <name><![CDATA[Home Assistant]]></name>
@ -22,7 +22,7 @@
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](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown). 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](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown).
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) 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](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organisation. As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) 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](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
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. 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.

8
blog/index.html
View file

@ -393,12 +393,12 @@ broadlink.send_packet_192_168_0_107 -&gt; switch.broadlink_send_packet_192_168_0
Screenshot of the color wheel. Screenshot of the color wheel.
</p> </p>
<h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2> <h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2>
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editting has been made easier.</p> <p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editing has been made easier.</p>
<h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2> <h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2>
<p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p> <p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p>
<p class="img"> <p class="img">
<img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." /> <img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." />
Screenshot of the of the Enitity Picker. Screenshot of the of the Entity Picker.
</p> </p>
<h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2> <h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2>
<p>If you follow our <a href="https://twitter.com/home_assistant">twitter feed</a> then you may already know that <a href="https://github.com/frenck">@frenck</a> spent some time to bring new stuff to the <a href="https://github.com/hassio-addons/repository">Community Hass.io Add-ons repository</a>.</p> <p>If you follow our <a href="https://twitter.com/home_assistant">twitter feed</a> then you may already know that <a href="https://github.com/frenck">@frenck</a> spent some time to bring new stuff to the <a href="https://github.com/hassio-addons/repository">Community Hass.io Add-ons repository</a>.</p>
@ -492,7 +492,7 @@ broadlink.send_packet_192_168_0_107 -&gt; switch.broadlink_send_packet_192_168_0
The Hass.io release of 0.58 will be delayed by a couple of days because Pascal is moving this weekend. The Hass.io release of 0.58 will be delayed by a couple of days because Pascal is moving this weekend.
</p> </p>
<h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2> <h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2>
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.</p> <p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.</p>
<p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p> <p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p>
<p>And because more translations is more better, <a href="https://github.com/robbiet480">@robbiet480</a> has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.</p> <p>And because more translations is more better, <a href="https://github.com/robbiet480">@robbiet480</a> has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.</p>
<p><a href="https://home-assistant.io/blog/2017/11/05/frontend-translations/">Learn more about how to help with translations</a></p> <p><a href="https://home-assistant.io/blog/2017/11/05/frontend-translations/">Learn more about how to help with translations</a></p>
@ -635,7 +635,7 @@ For Custom UI users: your custom UI will need to be updated before it can work w
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

8
blog/posts/10/index.html
View file

@ -200,11 +200,11 @@
<p>Do less and be lazy. It sounds so obvious and it took a while before it started to dawn on me. I think most of the code I write is pretty fast, but I don’t often stop to take a harder look at how and when it runs in practice. When do we need the result, can it be postponed?</p> <p>Do less and be lazy. It sounds so obvious and it took a while before it started to dawn on me. I think most of the code I write is pretty fast, but I don’t often stop to take a harder look at how and when it runs in practice. When do we need the result, can it be postponed?</p>
<p>And thus started my journey to take a critical look at how the Home Assistant app was working and how to make things faster. Below is the list of the different things that I did to make it fast.</p> <p>And thus started my journey to take a critical look at how the Home Assistant app was working and how to make things faster. Below is the list of the different things that I did to make it fast.</p>
<p>I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.</p> <p>I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.</p>
<p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 miliseconds and on my Nexus 5x in ~6500 miliseconds (~4.5 times slower!).</strong></p> <p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 milliseconds and on my Nexus 5x in ~6500 milliseconds (~4.5 times slower!).</strong></p>
<p class="img"> <p class="img">
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.18.2.png" alt="Timeline of loading the front end in Home Assistant 0.18.2" /> <img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.18.2.png" alt="Timeline of loading the front end in Home Assistant 0.18.2" />
</p> </p>
<p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 miliseconds (-35%) on my Mac and 2400 miliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p> <p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 milliseconds (-35%) on my Mac and 2400 milliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p>
<p class="img"> <p class="img">
<img src="/images/blog/2016-08-optimizing-web-app/performance-diagram.png" alt="diagram showing old and new loading times next to one another" /> <img src="/images/blog/2016-08-optimizing-web-app/performance-diagram.png" alt="diagram showing old and new loading times next to one another" />
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.26.png" alt="Timeline of loading the front end in Home Assistant 0.26" /> <img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.26.png" alt="Timeline of loading the front end in Home Assistant 0.26" />
@ -267,7 +267,7 @@
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!</p> <p>When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!</p>
<p>Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p> <p>Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p>
<p>We have also seen an exciting trend of people starting to visualize their Internet of Things data using <a href="http://jupyter.org/">Jupyter</a> Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the <a href="/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/">blog</a> post by <a href="https://github.com/kireyeu">@kireyeu</a> shows an advanced usecase while our <a href="/cookbook/#jupyter-notebooks">Notebooks</a> in the <a href="https://github.com/home-assistant/home-assistant-notebooks">Home Assistant Notebooks repository</a> cover the basics.</p> <p>We have also seen an exciting trend of people starting to visualize their Internet of Things data using <a href="http://jupyter.org/">Jupyter</a> Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the <a href="/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/">blog</a> post by <a href="https://github.com/kireyeu">@kireyeu</a> shows an advanced usecase while our <a href="/cookbook/#jupyter-notebooks">Notebooks</a> in the <a href="https://github.com/home-assistant/home-assistant-notebooks">Home Assistant Notebooks repository</a> cover the basics.</p>
<p>This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!</p> <p>This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!</p>
<p>The brand-new <a href="/components/panel_iframe/">iFrame panel component</a> allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.</p> <p>The brand-new <a href="/components/panel_iframe/">iFrame panel component</a> allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.</p>
@ -550,7 +550,7 @@ Over a year ago I participated in the <a href="https://www.kickstarter.com/proje
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/11/index.html
View file

@ -574,7 +574,7 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

14
blog/posts/12/index.html
View file

@ -256,7 +256,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> <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><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> <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> <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>
<p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p> <p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p>
<a class="btn pull-right" href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/#read-more">Read on &rarr;</a> <a class="btn pull-right" href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/#read-more">Read on &rarr;</a>
</div> </div>
</article> </article>
@ -282,8 +282,8 @@
</div> </div>
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.</p> <p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.</p>
<p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organisation on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p> <p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organization on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p>
<p><a href="/demo/"><img src="/images/blog/2016-04-release-18/media_player.png" style="box-shadow: none; border: 0;" /></a></p> <p><a href="/demo/"><img src="/images/blog/2016-04-release-18/media_player.png" style="box-shadow: none; border: 0;" /></a></p>
<p><img src="/images/supported_brands/bluetooth.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/webos.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/rss.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/eq3.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/thinkingcleaner.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p> <p><img src="/images/supported_brands/bluetooth.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/webos.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/rss.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/eq3.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/thinkingcleaner.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
<ul> <ul>
@ -336,7 +336,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'
@ -345,7 +345,7 @@
</div> </div>
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organisation on GitHub</a>.</p> <p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organization on GitHub</a>.</p>
<p>On our journey we’ve reached many noteworthy milestones:</p> <p>On our journey we’ve reached many noteworthy milestones:</p>
<ul> <ul>
<li>#1 on HackerNews</li> <li>#1 on HackerNews</li>
@ -388,7 +388,7 @@
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>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 <a href="/getting-started/">getting started</a> and <a href="/developers/">developers</a> sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.</p> <p>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 <a href="/getting-started/">getting started</a> and <a href="/developers/">developers</a> sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.</p>
<p>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 <a href="/blog/2014/12/18/website-launched/">called it a website</a>. Back then we had a whopping <a href="https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown">11 components</a>.</p> <p>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 <a href="/blog/2014/12/18/website-launched/">called it a website</a>. Back then we had a whopping <a href="https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown">11 components</a>.</p>
<p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> 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 <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organisation.</p> <p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> 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 <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organization.</p>
<p>Today it has been almost 1.5 years since we started the website. We now have <a href="/components/">264 components and platforms</a> under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.</p> <p>Today it has been almost 1.5 years since we started the website. We now have <a href="/components/">264 components and platforms</a> under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.</p>
<p>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.</p> <p>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.</p>
</div> </div>
@ -534,7 +534,7 @@
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/13/index.html
View file

@ -650,7 +650,7 @@ Example of the new views in the frontend. <a href="/components/group/">Learn mor
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/14/index.html
View file

@ -475,7 +475,7 @@ The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time se
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

4
blog/posts/15/index.html
View file

@ -300,7 +300,7 @@ Map in Home Assistant showing two people and three zones (home, school, work)
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p><img src="/images/supported_brands/glances.png" style="border:none; box-shadow: none; float: right;" height="80" /> <p><img src="/images/supported_brands/glances.png" style="border:none; box-shadow: none; float: right;" height="80" />
Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p> Inspired by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p>
<a class="btn pull-right" href="/blog/2015/09/18/monitoring-with-glances-and-home-assistant/#read-more">Read on &rarr;</a> <a class="btn pull-right" href="/blog/2015/09/18/monitoring-with-glances-and-home-assistant/#read-more">Read on &rarr;</a>
</div> </div>
</article> </article>
@ -478,7 +478,7 @@ Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/3
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

4
blog/posts/16/index.html
View file

@ -458,7 +458,7 @@ An initial version of voice control for Home Assistant has landed. The current i
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'
@ -512,7 +512,7 @@ The old logo, the new detailed logo and the new simple logo.
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

4
blog/posts/17/index.html
View file

@ -149,7 +149,7 @@
<li>Recorder component that will record every event to a SQLite database</li> <li>Recorder component that will record every event to a SQLite database</li>
<li>History component that will query and aggregate the recorded events</li> <li>History component that will query and aggregate the recorded events</li>
</ul> </ul>
<p>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p> <p>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of today’s release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p>
<p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p> <p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p>
<p>The history component will be enabled for new users by default. For current users, run <code class="highlighter-rouge">scripts/update</code> to upgrade to the latest version and add <code class="highlighter-rouge">[history]</code> to your <code class="highlighter-rouge">home-assistant.conf</code> file.</p> <p>The history component will be enabled for new users by default. For current users, run <code class="highlighter-rouge">scripts/update</code> to upgrade to the latest version and add <code class="highlighter-rouge">[history]</code> to your <code class="highlighter-rouge">home-assistant.conf</code> file.</p>
<p class="img"> <p class="img">
@ -402,7 +402,7 @@ This article will try to explain how they all relate.</p>
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/2/index.html
View file

@ -549,7 +549,7 @@ The Home Assistant sidebar in 12 different languages.
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

4
blog/posts/3/index.html
View file

@ -361,7 +361,7 @@ Screenshot of the new customize editor.
<h2><a class="title-link" name="input-text" href="#input-text"></a> Input text</h2> <h2><a class="title-link" name="input-text" href="#input-text"></a> Input text</h2>
<p>This release introduces a new input component: <code class="highlighter-rouge">input_text</code> contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.</p> <p>This release introduces a new input component: <code class="highlighter-rouge">input_text</code> contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.</p>
<h2><a class="title-link" name="knx" href="#knx"></a> KNX</h2> <h2><a class="title-link" name="knx" href="#knx"></a> KNX</h2>
<p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p> <p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunneling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p>
<div class="videoWrapper"> <div class="videoWrapper">
<iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen=""></iframe> <iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen=""></iframe>
</div> </div>
@ -607,7 +607,7 @@ Screenshot of the new customize editor.
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/4/index.html
View file

@ -601,7 +601,7 @@ Screenshot of a green dashboard
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/5/index.html
View file

@ -522,7 +522,7 @@ If you have a security key set in your Open Z-Wave <code class="highlighter-roug
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

10
blog/posts/6/index.html
View file

@ -92,7 +92,7 @@
<img src="/images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png" /> <img src="/images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png" />
</p> </p>
<p>Saw the <a href="/blog/2017/04/30/hassbian-1.21-its-about-time/">announcement</a> yesterday for HASSbian 1.21 and got super excited?</p> <p>Saw the <a href="/blog/2017/04/30/hassbian-1.21-its-about-time/">announcement</a> yesterday for HASSbian 1.21 and got super excited?</p>
<p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspbery Pi Zero W</a>. <p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspberry Pi Zero W</a>.
<strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p> <strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p>
<p>What you’ll need:</p> <p>What you’ll need:</p>
<ul> <ul>
@ -160,7 +160,7 @@ $ sudo systemctl start install_homeassistant.service
<h3><a class="title-link" name="hassbian-config" href="#hassbian-config"></a> Hassbian-config</h3> <h3><a class="title-link" name="hassbian-config" href="#hassbian-config"></a> Hassbian-config</h3>
<p>To allow you to customize your installation further, we have included a tool called <code class="highlighter-rouge">hassbian-config</code>. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the <code class="highlighter-rouge">hassbian-scripts</code> functionality from 1.1.</p> <p>To allow you to customize your installation further, we have included a tool called <code class="highlighter-rouge">hassbian-config</code>. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the <code class="highlighter-rouge">hassbian-scripts</code> functionality from 1.1.</p>
<ul> <ul>
<li>Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.</li> <li>Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that’s used with Amazon Echo, Google Home and Mycroft.ai.</li>
<li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li> <li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li>
<li>Install Libcec. Adds local <a href="/components/hdmi_cec/">HDMI CEC support</a>.</li> <li>Install Libcec. Adds local <a href="/components/hdmi_cec/">HDMI CEC support</a>.</li>
<li>Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.</li> <li>Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.</li>
@ -406,7 +406,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
<p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p> <p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p>
<p>I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.</p> <p>I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.</p>
<p>I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.</p> <p>I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.</p>
<p>It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p> <p>It may not look the way that I wanted it to initially, with beautiful native UI components, but that’s okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p>
<p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p> <p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p>
<p>The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.</p> <p>The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.</p>
<p>The app is <a href="https://github.com/home-assistant/home-assistant-iOS">open source</a>, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.</p> <p>The app is <a href="https://github.com/home-assistant/home-assistant-iOS">open source</a>, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.</p>
@ -489,7 +489,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
<li>Dead line: April, 23 2017 - 23.59 UTC</li> <li>Dead line: April, 23 2017 - 23.59 UTC</li>
<li>Voting period: April, 24th till April, 30 2017 - 23.59 UTC</li> <li>Voting period: April, 24th till April, 30 2017 - 23.59 UTC</li>
</ul> </ul>
<p>The decision of the jury will be final. If there will be a dispute then the Top-5 commiter of the Home Assistant organisation on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p> <p>The decision of the jury will be final. If there will be a dispute then the Top-5 committer of the Home Assistant organization on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p>
<p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p> <p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p>
</div> </div>
</article> </article>
@ -557,7 +557,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
blog/posts/7/index.html
View file

@ -721,7 +721,7 @@ On the close horizon from <a href="https://github.com/Landrash">@Landrash</a> th
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

6
blog/posts/8/index.html
View file

@ -184,7 +184,7 @@
<li>Switch - Pilight: Implement echo config option (<a href="https://github.com/janLo">@janLo</a>)</li> <li>Switch - Pilight: Implement echo config option (<a href="https://github.com/janLo">@janLo</a>)</li>
<li>Core: Support customize in packages (<a href="https://github.com/kellerza">@kellerza</a>)</li> <li>Core: Support customize in packages (<a href="https://github.com/kellerza">@kellerza</a>)</li>
<li>Switch - Flux: Allow disabling setting the brightness (<a href="https://github.com/rytilahti">@rytilahti</a>)</li> <li>Switch - Flux: Allow disabling setting the brightness (<a href="https://github.com/rytilahti">@rytilahti</a>)</li>
<li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no emtpy image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li> <li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no empty image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li>
<li>Climate: Hold mode (<a href="https://github.com/Duoxilian">@Duoxilian</a>)</li> <li>Climate: Hold mode (<a href="https://github.com/Duoxilian">@Duoxilian</a>)</li>
<li>Switch - TPlink: No longer doing I/O in event bus (<a href="https://github.com/balloob">@balloob</a>)</li> <li>Switch - TPlink: No longer doing I/O in event bus (<a href="https://github.com/balloob">@balloob</a>)</li>
<li>Light - Insteon local: Improve Insteon configuration (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li> <li>Light - Insteon local: Improve Insteon configuration (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li>
@ -237,7 +237,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'
@ -943,7 +943,7 @@ You have to note:
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

10
blog/posts/9/index.html
View file

@ -79,7 +79,7 @@
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>
<ul class="tags unstyled"> <ul class="tags unstyled">
<li>Organisation</li> <li>Organization</li>
</ul> </ul>
</span> </span>
<a class='comments' <a class='comments'
@ -534,7 +534,7 @@
</div> </div>
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p> <p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organized by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p>
<p>Why contribute to Home Assistant:</p> <p>Why contribute to Home Assistant:</p>
<ul> <ul>
<li>Written in Python3 with 94% test coverage</li> <li>Written in Python3 with 94% test coverage</li>
@ -735,9 +735,9 @@
<h3><a class="title-link" name="climate-and--cover" href="#climate-and--cover"></a> Climate and cover</h3> <h3><a class="title-link" name="climate-and--cover" href="#climate-and--cover"></a> Climate and cover</h3>
<p>There are countless bugfixes included in this release which will make your experience with the <code class="highlighter-rouge">climate</code> and the <code class="highlighter-rouge">cover</code> platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/djbanks">@djbanks</a>, <a href="https://github.com/danielperna84">@danielperna84</a>, and others the improvements on the code and the frontend side is continuing…</p> <p>There are countless bugfixes included in this release which will make your experience with the <code class="highlighter-rouge">climate</code> and the <code class="highlighter-rouge">cover</code> platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/djbanks">@djbanks</a>, <a href="https://github.com/danielperna84">@danielperna84</a>, and others the improvements on the code and the frontend side is continuing…</p>
<h3><a class="title-link" name="api-documentation" href="#api-documentation"></a> API documentation</h3> <h3><a class="title-link" name="api-documentation" href="#api-documentation"></a> API documentation</h3>
<p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p> <p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p>
<h3><a class="title-link" name="configuration-validation" href="#configuration-validation"></a> Configuration validation</h3> <h3><a class="title-link" name="configuration-validation" href="#configuration-validation"></a> Configuration validation</h3>
<p>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 <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p> <p>The validation of the configuration is still on-going. Approximately 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 <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p>
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3> <h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
<p><img src="/images/supported_brands/xbox-live.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/automatic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/pi_hole.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p> <p><img src="/images/supported_brands/xbox-live.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/automatic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/pi_hole.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
<ul> <ul>
@ -1086,7 +1086,7 @@ Heatmap
<li><a href="/blog/categories/media/">Media</a></li> <li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li> <li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li> <li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li> <li><a href="/blog/categories/organization/">Organization</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li> <li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li> <li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li> <li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>

2
components/binary_sensor.bbb_gpio/index.html
View file

@ -93,7 +93,7 @@
<li><strong>pin_name</strong> (<em>Required</em>): Pin numbers and corresponding names. <li><strong>pin_name</strong> (<em>Required</em>): Pin numbers and corresponding names.
<ul> <ul>
<li><strong>name</strong> (<em>Required</em>): Friendly name to use for the frontend.</li> <li><strong>name</strong> (<em>Required</em>): Friendly name to use for the frontend.</li>
<li><strong>bouncetime</strong> (<em>Optional</em>): Debounce time for reading input pin defined in miliseconds [ms]. Defaults to <code class="highlighter-rouge">50 ms</code>.</li> <li><strong>bouncetime</strong> (<em>Optional</em>): Debounce time for reading input pin defined in milliseconds [ms]. Defaults to <code class="highlighter-rouge">50 ms</code>.</li>
<li><strong>invert_logic</strong> (<em>Optional</em>): If <code class="highlighter-rouge">true</code>, inverts the input logic to ACTIVE LOW. Default is <code class="highlighter-rouge">false</code> (ACTIVE HIGH).</li> <li><strong>invert_logic</strong> (<em>Optional</em>): If <code class="highlighter-rouge">true</code>, inverts the input logic to ACTIVE LOW. Default is <code class="highlighter-rouge">false</code> (ACTIVE HIGH).</li>
<li><strong>pull_mode</strong> (<em>Optional</em>): Type of internal pull resistor connected to input. Options are <code class="highlighter-rouge">UP</code> - pull-up resistor and <code class="highlighter-rouge">DOWN</code> - pull-down resistor. Defaults to <code class="highlighter-rouge">UP</code>.</li> <li><strong>pull_mode</strong> (<em>Optional</em>): Type of internal pull resistor connected to input. Options are <code class="highlighter-rouge">UP</code> - pull-up resistor and <code class="highlighter-rouge">DOWN</code> - pull-down resistor. Defaults to <code class="highlighter-rouge">UP</code>.</li>
</ul> </ul>

2
components/binary_sensor.xiaomi_aqara/index.html
View file

@ -157,7 +157,7 @@
<td>Button (1st gen)</td> <td>Button (1st gen)</td>
<td>switch</td> <td>switch</td>
<td>WXKG01LM</td> <td>WXKG01LM</td>
<td>on (thru long_click_press), off</td> <td>on (through long_click_press), off</td>
<td><code class="highlighter-rouge">click</code></td> <td><code class="highlighter-rouge">click</code></td>
<td><code class="highlighter-rouge">click_type</code></td> <td><code class="highlighter-rouge">click_type</code></td>
<td><code class="highlighter-rouge">long_click_press</code>, <code class="highlighter-rouge">long_click_release</code>, <code class="highlighter-rouge">hold</code>, <code class="highlighter-rouge">single</code>, <code class="highlighter-rouge">double</code></td> <td><code class="highlighter-rouge">long_click_press</code>, <code class="highlighter-rouge">long_click_release</code>, <code class="highlighter-rouge">hold</code>, <code class="highlighter-rouge">single</code>, <code class="highlighter-rouge">double</code></td>

2
components/binary_sensor.zigbee/index.html
View file

@ -74,7 +74,7 @@
</h1> </h1>
</header> </header>
<hr class="divider"> <hr class="divider">
<p>A <code class="highlighter-rouge">zigbee</code> binary sensor in this context is a device connected to one of the digital input pins on a <a href="http://www.zigbee.org/">ZigBee</a> module. The states reported by such a device are limited to <code class="highlighter-rouge">on</code> or <code class="highlighter-rouge">off</code>. By default, a binary sensor is considered <code class="highlighter-rouge">on</code> when the ZigBee device’s digital input pin is held ‘high’ and considered <code class="highlighter-rouge">off</code> when it is held <code class="highlighter-rouge">low</code>. This behaviour can be inverted by setting the <code class="highlighter-rouge">on_state</code> configuration variable to <code class="highlighter-rouge">low</code>.</p> <p>A <code class="highlighter-rouge">zigbee</code> binary sensor in this context is a device connected to one of the digital input pins on a <a href="http://www.zigbee.org/">ZigBee</a> module. The states reported by such a device are limited to <code class="highlighter-rouge">on</code> or <code class="highlighter-rouge">off</code>. By default, a binary sensor is considered <code class="highlighter-rouge">on</code> when the ZigBee device’s digital input pin is held ‘high’ and considered <code class="highlighter-rouge">off</code> when it is held <code class="highlighter-rouge">low</code>. This behavior can be inverted by setting the <code class="highlighter-rouge">on_state</code> configuration variable to <code class="highlighter-rouge">low</code>.</p>
<p>To enable a digital input pin as binary sensor in your installation, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p> <p>To enable a digital input pin as binary sensor in your installation, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code>:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
<span class="s">binary_sensor</span><span class="pi">:</span> <span class="s">binary_sensor</span><span class="pi">:</span>

2
components/climate.ecobee/index.html
View file

@ -419,7 +419,7 @@ For ‘temp’, the current temperature is taken as the target temperature.
When None is provided as parameter, the hold_mode is turned off. When None is provided as parameter, the hold_mode is turned off.
It is not possible to set a vacation hold; such hold has to be It is not possible to set a vacation hold; such hold has to be
defined on the thermostat directly. However, a vacation hold can be defined on the thermostat directly. However, a vacation hold can be
cancelled.</p> canceled.</p>
<table> <table>
<thead> <thead>
<tr> <tr>

4
components/device_tracker.bluetooth_le_tracker/index.html
View file

@ -86,7 +86,7 @@ We have received <a href="https://github.com/home-assistant/home-assistant/issue
<p>Before you get started with this platform, please note that:</p> <p>Before you get started with this platform, please note that:</p>
<ul> <ul>
<li>This platform is incompatible with Windows</li> <li>This platform is incompatible with Windows</li>
<li>This platform requires access to the bluetooth stack, see <a href="#rootless-setup">Rootless Setup section</a> for further infomation</li> <li>This platform requires access to the bluetooth stack, see <a href="#rootless-setup">Rootless Setup section</a> for further information</li>
</ul> </ul>
<p>To use the Bluetooth tracker in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p> <p>To use the Bluetooth tracker in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
@ -104,7 +104,7 @@ We have received <a href="https://github.com/home-assistant/home-assistant/issue
<p>As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times. <p>As some BT LE devices change their MAC address regularly, a new device is only discovered when it has been seen 5 times.
Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won’t see this device.</p> Some BTLE devices (e.g. fitness trackers) are only visible to the devices that they are paired with. In this case, the BTLE tracker won’t see this device.</p>
<h2><a class="title-link" name="rootless-setup" href="#rootless-setup"></a> Rootless Setup</h2> <h2><a class="title-link" name="rootless-setup" href="#rootless-setup"></a> Rootless Setup</h2>
<p>Normaly accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see <a href="http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root">Stack Exchange</a> for more information).</p> <p>Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see <a href="http://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root">Stack Exchange</a> for more information).</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo apt-get install libcap2-bin <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo apt-get install libcap2-bin
<span class="gp">$ </span>sudo setcap <span class="s1">'cap_net_raw,cap_net_admin+eip'</span> <span class="sb">`</span>readlink -f <span class="se">\`</span>which python3<span class="se">\`</span><span class="sb">`</span> <span class="gp">$ </span>sudo setcap <span class="s1">'cap_net_raw,cap_net_admin+eip'</span> <span class="sb">`</span>readlink -f <span class="se">\`</span>which python3<span class="se">\`</span><span class="sb">`</span>
</code></pre> </code></pre>

6
components/device_tracker.gpslogger/index.html
View file

@ -121,15 +121,15 @@
<li>Use the domain that Home Assistant is available on the internet or the public IP address. Can be a local IP address if you are using a VPN setup.</li> <li>Use the domain that Home Assistant is available on the internet or the public IP address. Can be a local IP address if you are using a VPN setup.</li>
<li>Only remove <code class="highlighter-rouge">[Port]</code> if your Home Assistant instance is using port 80. Otherwise set it to 8123.</li> <li>Only remove <code class="highlighter-rouge">[Port]</code> if your Home Assistant instance is using port 80. Otherwise set it to 8123.</li>
<li>For Home Assistant only the above URL, as written, will work - do not add or remove any parameters.</li> <li>For Home Assistant only the above URL, as written, will work - do not add or remove any parameters.</li>
<li>Make sure to include your <a href="/components/http/">API password</a> if you have configured a password. Add <code class="highlighter-rouge">&amp;api_password=[Your pasword]</code> to the end of the URL.</li> <li>Make sure to include your <a href="/components/http/">API password</a> if you have configured a password. Add <code class="highlighter-rouge">&amp;api_password=[Your password]</code> to the end of the URL.</li>
<li>You can change the name of your device name by replacing <code class="highlighter-rouge">&amp;device=%SER</code> with <code class="highlighter-rouge">&amp;device=[Devicename]</code>.</li> <li>You can change the name of your device name by replacing <code class="highlighter-rouge">&amp;device=%SER</code> with <code class="highlighter-rouge">&amp;device=[Devicename]</code>.</li>
</ul> </ul>
<p>If your battery drains fast then you can tune the performence of GPSLogger under <strong>Performance</strong> -&gt; <strong>Location providers</strong></p> <p>If your battery drains fast then you can tune the performance of GPSLogger under <strong>Performance</strong> -&gt; <strong>Location providers</strong></p>
<p class="img"> <p class="img">
<img width="300" src="/images/components/gpslogger/performance.png" /> <img width="300" src="/images/components/gpslogger/performance.png" />
Performance Performance
</p> </p>
<p>A request can be forced from the app to test if everything is working fine. A succesful request will update the <code class="highlighter-rouge">known_devices.yaml</code> file with the device’s serial number.</p> <p>A request can be forced from the app to test if everything is working fine. A successful request will update the <code class="highlighter-rouge">known_devices.yaml</code> file with the device’s serial number.</p>
</article> </article>
</div> </div>
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole"> <aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

2
components/fan.xiaomi_miio/index.html
View file

@ -74,7 +74,7 @@
</h1> </h1>
</header> </header>
<hr class="divider"> <hr class="divider">
<p>The <code class="highlighter-rouge">xiaomi_miio</code> fan platform allows you to control the Xiaomi Air Purifier 2, Air Purifier 2S andd Air Purifier Pro.</p> <p>The <code class="highlighter-rouge">xiaomi_miio</code> fan platform allows you to control the Xiaomi Air Purifier 2, Air Purifier 2S and Air Purifier Pro.</p>
<p>Currently, the supported features are</p> <p>Currently, the supported features are</p>
<ul> <ul>
<li>On, Off</li> <li>On, Off</li>

4
components/frontend/index.html
View file

@ -109,11 +109,11 @@
</dd> </dd>
<dt><a class="title-link" name="extra_html_url" href="#extra_html_url"></a> extra_html_url</dt> <dt><a class="title-link" name="extra_html_url" href="#extra_html_url"></a> extra_html_url</dt>
<dd> <dd>
<p class="desc"><span class="type">(<span class="list">list</span>)</span><span class="required">(Optional)</span><span class="description">List of addtional <a href="/developers/frontend_creating_custom_ui/">resources</a> to load in <code class="highlighter-rouge">latest</code> javascript mode.</span></p> <p class="desc"><span class="type">(<span class="list">list</span>)</span><span class="required">(Optional)</span><span class="description">List of additional <a href="/developers/frontend_creating_custom_ui/">resources</a> to load in <code class="highlighter-rouge">latest</code> javascript mode.</span></p>
</dd> </dd>
<dt><a class="title-link" name="extra_html_url_es5" href="#extra_html_url_es5"></a> extra_html_url_es5</dt> <dt><a class="title-link" name="extra_html_url_es5" href="#extra_html_url_es5"></a> extra_html_url_es5</dt>
<dd> <dd>
<p class="desc"><span class="type">(<span class="list">list</span>)</span><span class="required">(Optional)</span><span class="description">List of addtional <a href="/developers/frontend_creating_custom_ui/">resources</a> to load in <code class="highlighter-rouge">es5</code> javascript mode.</span></p> <p class="desc"><span class="type">(<span class="list">list</span>)</span><span class="required">(Optional)</span><span class="description">List of additional <a href="/developers/frontend_creating_custom_ui/">resources</a> to load in <code class="highlighter-rouge">es5</code> javascript mode.</span></p>
</dd> </dd>
<dt><a class="title-link" name="development_repo" href="#development_repo"></a> development_repo</dt> <dt><a class="title-link" name="development_repo" href="#development_repo"></a> development_repo</dt>
<dd> <dd>

2
components/group/index.html
View file

@ -169,7 +169,7 @@ Notice in the example below that in order to refer to the group “Living Room
<span class="pi">-</span> <span class="s">group.all_scripts</span> <span class="pi">-</span> <span class="s">group.all_scripts</span>
</code></pre> </code></pre>
</div> </div>
<h2><a class="title-link" name="group-behaviour" href="#group-behaviour"></a> Group behaviour</h2> <h2><a class="title-link" name="group-behavior" href="#group-behavior"></a> Group behavior</h2>
<p>When any member of a group is <code class="highlighter-rouge">on</code> then the group will also be <code class="highlighter-rouge">on</code>. Similarly with a device tracker, when any member of the group is <code class="highlighter-rouge">home</code> then the group is <code class="highlighter-rouge">home</code>.</p> <p>When any member of a group is <code class="highlighter-rouge">on</code> then the group will also be <code class="highlighter-rouge">on</code>. Similarly with a device tracker, when any member of the group is <code class="highlighter-rouge">home</code> then the group is <code class="highlighter-rouge">home</code>.</p>
<h2><a class="title-link" name="customize-group-order" href="#customize-group-order"></a> Customize group order</h2> <h2><a class="title-link" name="customize-group-order" href="#customize-group-order"></a> Customize group order</h2>
<p>You can also order your groups using <a href="/docs/configuration/customizing-devices/">customize</a> with <code class="highlighter-rouge">order: </code> if they don’t show up in the order you want them in.</p> <p>You can also order your groups using <a href="/docs/configuration/customizing-devices/">customize</a> with <code class="highlighter-rouge">order: </code> if they don’t show up in the order you want them in.</p>

2
components/hive/index.html
View file

@ -106,7 +106,7 @@
<li>Hive Active Heating (including hot water and Hive Multizone)</li> <li>Hive Active Heating (including hot water and Hive Multizone)</li>
<li>Hive Active Light Dimmable</li> <li>Hive Active Light Dimmable</li>
<li>Hive Active Light Cool to Warm White</li> <li>Hive Active Light Cool to Warm White</li>
<li>Hive Active Light Colour Changing</li> <li>Hive Active Light Color Changing</li>
<li>Hive Active Plug</li> <li>Hive Active Plug</li>
<li>Hive Window or Door Sensor</li> <li>Hive Window or Door Sensor</li>
<li>Hive Motion Sensor</li> <li>Hive Motion Sensor</li>

2
components/image_processing/index.html
View file

@ -81,7 +81,7 @@ If you are running Home Assistant over SSL or from within a container, you will
</p> </p>
<h2><a class="title-link" name="alpr" href="#alpr"></a> ALPR</h2> <h2><a class="title-link" name="alpr" href="#alpr"></a> ALPR</h2>
<p>Alpr entities attribute have a vehicle counter <code class="highlighter-rouge">vehicles</code> and all found plates as <code class="highlighter-rouge">plates</code>.</p> <p>Alpr entities attribute have a vehicle counter <code class="highlighter-rouge">vehicles</code> and all found plates as <code class="highlighter-rouge">plates</code>.</p>
<p>This event is trigger after OpenALPR found a new licence plate.</p> <p>This event is trigger after OpenALPR found a new license plate.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml automation entry</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml automation entry</span>
<span class="s">automation</span><span class="pi">:</span> <span class="s">automation</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s">Open garage door</span> <span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s">Open garage door</span>

2
components/input_datetime/index.html
View file

@ -144,7 +144,7 @@
</tr> </tr>
<tr> <tr>
<td><code class="highlighter-rouge">year</code><br /><code class="highlighter-rouge">month</code><br /><code class="highlighter-rouge">day</code></td> <td><code class="highlighter-rouge">year</code><br /><code class="highlighter-rouge">month</code><br /><code class="highlighter-rouge">day</code></td>
<td>The year, month and day of the date.<br />(only availabel if <code class="highlighter-rouge">has_date: true</code>)</td> <td>The year, month and day of the date.<br />(only available if <code class="highlighter-rouge">has_date: true</code>)</td>
</tr> </tr>
<tr> <tr>
<td><code class="highlighter-rouge">hour</code><br /><code class="highlighter-rouge">minute</code><br /><code class="highlighter-rouge">second</code></td> <td><code class="highlighter-rouge">hour</code><br /><code class="highlighter-rouge">minute</code><br /><code class="highlighter-rouge">second</code></td>

2
components/input_number/index.html
View file

@ -111,7 +111,7 @@ Before version 0.55 this component was known as <code class="highlighter-rouge">
</dd> </dd>
<dt><a class="title-link" name="max" href="#max"></a> max</dt> <dt><a class="title-link" name="max" href="#max"></a> max</dt>
<dd> <dd>
<p class="desc"><span class="type">(<span class="float">float</span>)</span><span class="required">(Required)</span><span class="description">Maxium value.</span></p> <p class="desc"><span class="type">(<span class="float">float</span>)</span><span class="required">(Required)</span><span class="description">Maximum value.</span></p>
</dd> </dd>
<dt><a class="title-link" name="name" href="#name"></a> name</dt> <dt><a class="title-link" name="name" href="#name"></a> name</dt>
<dd> <dd>

2
components/knx/index.html
View file

@ -133,7 +133,7 @@
<ul> <ul>
<li><strong>fire_event</strong> (<em>Optional</em>): If set to True, platform will write all received KNX messages to event bus</li> <li><strong>fire_event</strong> (<em>Optional</em>): If set to True, platform will write all received KNX messages to event bus</li>
<li><strong>fire_event_filter</strong> (<em>Optional</em>): If <code class="highlighter-rouge">fire_event</code> is set <code class="highlighter-rouge">fire_event_filter</code> has to be specified. <code class="highlighter-rouge">fire_event_filter</code> defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme Assistant event bus.</li> <li><strong>fire_event_filter</strong> (<em>Optional</em>): If <code class="highlighter-rouge">fire_event</code> is set <code class="highlighter-rouge">fire_event_filter</code> has to be specified. <code class="highlighter-rouge">fire_event_filter</code> defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HOme Assistant event bus.</li>
<li><strong>state_updater</strong> (<em>Optional</em>): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behaviour.</li> <li><strong>state_updater</strong> (<em>Optional</em>): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behavior.</li>
<li><strong>time_address</strong> (<em>Optional</em>): Broadcast current local time to KNX bus with configured group address.</li> <li><strong>time_address</strong> (<em>Optional</em>): Broadcast current local time to KNX bus with configured group address.</li>
</ul> </ul>
<h3><a class="title-link" name="services" href="#services"></a> Services</h3> <h3><a class="title-link" name="services" href="#services"></a> Services</h3>

2
components/light.hive/index.html
View file

@ -79,7 +79,7 @@
<ul> <ul>
<li><strong>Hive Active Light Dimmable</strong></li> <li><strong>Hive Active Light Dimmable</strong></li>
<li><strong>Hive Active Light Cool to Warm White</strong></li> <li><strong>Hive Active Light Cool to Warm White</strong></li>
<li><strong>Hive Active Light Colour Changing</strong></li> <li><strong>Hive Active Light Color Changing</strong></li>
</ul> </ul>
<p class="note"> <p class="note">
Full configuration details can be found on the main <a href="/components/hive/">Hive component</a> page. Full configuration details can be found on the main <a href="/components/hive/">Hive component</a> page.

1
components/light.yeelight/index.html
View file

@ -116,6 +116,7 @@ This component is tested to work with the following models. If you have a differ
<li><strong>YLDP03YL</strong>: LED Bulb (Color) - E26</li> <li><strong>YLDP03YL</strong>: LED Bulb (Color) - E26</li>
<li><strong>YLDD01YL</strong>: Lightstrip (Color)</li> <li><strong>YLDD01YL</strong>: Lightstrip (Color)</li>
<li><strong>YLDD02YL</strong>: Lightstrip (Color)</li> <li><strong>YLDD02YL</strong>: Lightstrip (Color)</li>
<li><strong>MJCTD01YL</strong>: Xiaomi Mijia Bedside Lamp - WIFI Version!</li>
</ul> </ul>
</article> </article>
</div> </div>

2
components/light.zigbee/index.html
View file

@ -74,7 +74,7 @@
</h1> </h1>
</header> </header>
<hr class="divider"> <hr class="divider">
<p>A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered <code class="highlighter-rouge">on</code> when the ZigBee device’s digital output is held <code class="highlighter-rouge">high</code> and considered <code class="highlighter-rouge">off</code> when it is held <code class="highlighter-rouge">low</code>. This behaviour can be inverted by setting the <code class="highlighter-rouge">on_state</code> configuration variable to <code class="highlighter-rouge">low</code>.</p> <p>A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered <code class="highlighter-rouge">on</code> when the ZigBee device’s digital output is held <code class="highlighter-rouge">high</code> and considered <code class="highlighter-rouge">off</code> when it is held <code class="highlighter-rouge">low</code>. This behavior can be inverted by setting the <code class="highlighter-rouge">on_state</code> configuration variable to <code class="highlighter-rouge">low</code>.</p>
<p>To configure a digital output pin as light, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p> <p>To configure a digital output pin as light, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">light</span><span class="pi">:</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">light</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Desk Lamp</span> <span class="pi">-</span> <span class="s">name</span><span class="pi">:</span> <span class="s">Desk Lamp</span>

2
components/lirc/index.html
View file

@ -88,7 +88,7 @@ The configuration is slightly different :
- The former single <code class="highlighter-rouge">lirc</code> service is replaced with the three systemd services <code class="highlighter-rouge">lircd.service</code>, <code class="highlighter-rouge">lircmd.service</code> and <code class="highlighter-rouge">irexec.service</code>. There is no counterpart to the 0.9.0 <code class="highlighter-rouge">lirc</code> service which covered all of these. Using a separate transmitter device requires yet another service. - The former single <code class="highlighter-rouge">lirc</code> service is replaced with the three systemd services <code class="highlighter-rouge">lircd.service</code>, <code class="highlighter-rouge">lircmd.service</code> and <code class="highlighter-rouge">irexec.service</code>. There is no counterpart to the 0.9.0 <code class="highlighter-rouge">lirc</code> service which covered all of these. Using a separate transmitter device requires yet another service.
- 0.9.4 defaults to using systemd for controlling the services. This is not just start/stop functionality, systemd is used to implement new features and to address shortcomings in 0.9.0. However, traditional systemV scripts are also installed and could be used although this is less tested and not really documented.<br /> - 0.9.4 defaults to using systemd for controlling the services. This is not just start/stop functionality, systemd is used to implement new features and to address shortcomings in 0.9.0. However, traditional systemV scripts are also installed and could be used although this is less tested and not really documented.<br />
<br /> <br />
For more infomation have a look at <code class="highlighter-rouge">/usr/share/doc/lirc/README.Debian.gz</code> where the update process is explained when you have updated from jessie to stretch. For more information have a look at <code class="highlighter-rouge">/usr/share/doc/lirc/README.Debian.gz</code> where the update process is explained when you have updated from jessie to stretch.
</p> </p>
<h3><a class="title-link" name="configuring-lirc" href="#configuring-lirc"></a> Configuring LIRC</h3> <h3><a class="title-link" name="configuring-lirc" href="#configuring-lirc"></a> Configuring LIRC</h3>
<p>Now teach LIRC about your particular remote control by preparing a lircd configuration file (<code class="highlighter-rouge">/etc/lirc/lircd.conf</code>). Search the <a href="http://lirc.sourceforge.net/remotes/">LIRC remote database</a> for your model. If you can’t find it, then you can always use the <code class="highlighter-rouge">irrecord</code> program to learn your remote. This will create a valid configuration file. Add as many remotes as you want by pasting them into the file. If <code class="highlighter-rouge">irrecord</code> doesn’t work (e.g. for some air conditioner remotes), then the <code class="highlighter-rouge">mode2</code> program is capable of reading the codes in raw mode, followed by <code class="highlighter-rouge">irrecord -a</code> to extract hex codes.</p> <p>Now teach LIRC about your particular remote control by preparing a lircd configuration file (<code class="highlighter-rouge">/etc/lirc/lircd.conf</code>). Search the <a href="http://lirc.sourceforge.net/remotes/">LIRC remote database</a> for your model. If you can’t find it, then you can always use the <code class="highlighter-rouge">irrecord</code> program to learn your remote. This will create a valid configuration file. Add as many remotes as you want by pasting them into the file. If <code class="highlighter-rouge">irrecord</code> doesn’t work (e.g. for some air conditioner remotes), then the <code class="highlighter-rouge">mode2</code> program is capable of reading the codes in raw mode, followed by <code class="highlighter-rouge">irrecord -a</code> to extract hex codes.</p>

2
components/media_player.denonavr/index.html
View file

@ -125,7 +125,7 @@ If you have something else using the IP controller for your Denon AVR 3808CI, su
<ul> <ul>
<li>Additional option the control Denon AVR receivers with a builtin web server is using the HTTP interface with denonavr platform.</li> <li>Additional option the control Denon AVR receivers with a builtin web server is using the HTTP interface with denonavr platform.</li>
<li>denonavr platform supports some additional functionalities like album covers, custom input source names and auto discovery.</li> <li>denonavr platform supports some additional functionalities like album covers, custom input source names and auto discovery.</li>
<li>Marantz receivers seem to a have quite simliar interface. Thus if you own one, give it a try.</li> <li>Marantz receivers seem to a have quite similar interface. Thus if you own one, give it a try.</li>
</ul> </ul>
</article> </article>
</div> </div>

2
components/media_player.yamaha/index.html
View file

@ -121,7 +121,7 @@ your DNS) then.</li>
volume control and source selection. Playback controls, for instance volume control and source selection. Playback controls, for instance
play and stop are available for sources that supports it.</li> play and stop are available for sources that supports it.</li>
<li>The <code class="highlighter-rouge">play_media</code> service is implemented for <code class="highlighter-rouge">NET RADIO</code> source <li>The <code class="highlighter-rouge">play_media</code> service is implemented for <code class="highlighter-rouge">NET RADIO</code> source
only. The <code class="highlighter-rouge">media_id</code> is a <code class="highlighter-rouge">&gt;</code> separted string of the menu path on only. The <code class="highlighter-rouge">media_id</code> is a <code class="highlighter-rouge">&gt;</code> separated string of the menu path on
the vtuner service. For instance <code class="highlighter-rouge">Bookmarks&gt;Internet&gt;WAMC 90.3 FM</code>.</li> the vtuner service. For instance <code class="highlighter-rouge">Bookmarks&gt;Internet&gt;WAMC 90.3 FM</code>.</li>
</ul> </ul>
<h3><a class="title-link" name="example-configuration" href="#example-configuration"></a> Example configuration</h3> <h3><a class="title-link" name="example-configuration" href="#example-configuration"></a> Example configuration</h3>

2
components/namecheapdns/index.html
View file

@ -76,7 +76,7 @@
<hr class="divider"> <hr class="divider">
<p>With the <code class="highlighter-rouge">namecheapdns</code> component you can automatically update your dynamic DNS entry at <a href="https://www.namecheap.com/store/domains/freedns/">namecheapdns</a>.</p> <p>With the <code class="highlighter-rouge">namecheapdns</code> component you can automatically update your dynamic DNS entry at <a href="https://www.namecheap.com/store/domains/freedns/">namecheapdns</a>.</p>
<p class="note warning"> <p class="note warning">
Namecheap only supports IPv4 adresses to update. Namecheap only supports IPv4 addresses to update.
</p> </p>
<p>To use the component in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p> <p>To use the component in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>

2
components/notify.facebook/index.html
View file

@ -106,7 +106,7 @@ The phone number used in <strong>target</strong> should be registered with Faceb
<span class="pi">-</span> <span class="s1">'</span><span class="s">+919784516314'</span> <span class="pi">-</span> <span class="s1">'</span><span class="s">+919784516314'</span>
</code></pre> </code></pre>
</div> </div>
<p>You can also send messages to users that do not have stored their phone number with Facebook, but this requires a bit more work. The Messenger platform uses page specific user IDs instead of a global user ID. You will need to enable a webhook for the “messages” event in Facebook’s developer console. Once a user writes a message to a page, that webhook will then receive the user’s page specifc ID as part of the webhook’s payload. Below is a simple PHP script that reacts to the message “get my id” and sends a reply containing the user’s ID:</p> <p>You can also send messages to users that do not have stored their phone number with Facebook, but this requires a bit more work. The Messenger platform uses page specific user IDs instead of a global user ID. You will need to enable a webhook for the “messages” event in Facebook’s developer console. Once a user writes a message to a page, that webhook will then receive the user’s page specific ID as part of the webhook’s payload. Below is a simple PHP script that reacts to the message “get my id” and sends a reply containing the user’s ID:</p>
<div class="language-php highlighter-rouge"><pre class="highlight"><code><span class="cp">&lt;?php</span> <div class="language-php highlighter-rouge"><pre class="highlight"><code><span class="cp">&lt;?php</span>
<span class="nv">$access_token</span> <span class="o">=</span> <span class="s2">""</span><span class="p">;</span> <span class="nv">$access_token</span> <span class="o">=</span> <span class="s2">""</span><span class="p">;</span>

6
components/notify.pushsafer/index.html
View file

@ -90,7 +90,7 @@
<li><strong>private_key</strong> (<em>Required</em>): Your private or alias key. Private key = send the notification to all devices with standard params, alias key send the notification to the devices stored in the alias with predefined params.</li> <li><strong>private_key</strong> (<em>Required</em>): Your private or alias key. Private key = send the notification to all devices with standard params, alias key send the notification to the devices stored in the alias with predefined params.</li>
</ul> </ul>
<h3><a class="title-link" name="examples" href="#examples"></a> Examples</h3> <h3><a class="title-link" name="examples" href="#examples"></a> Examples</h3>
<p>Message to two devices with formated text.</p> <p>Message to two devices with formatted text.</p>
<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w"> <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
</span><span class="nt">"title"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Test to 2 devices"</span><span class="p">,</span><span class="w"> </span><span class="nt">"title"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Test to 2 devices"</span><span class="p">,</span><span class="w">
</span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Attention [b]bold[/b] text[br][url=https://www.pushsafer.com]Link to Pushsafer[/url]"</span><span class="p">,</span><span class="w"> </span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Attention [b]bold[/b] text[br][url=https://www.pushsafer.com]Link to Pushsafer[/url]"</span><span class="p">,</span><span class="w">
@ -107,7 +107,7 @@
</span><span class="p">}</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></code></pre> </span></code></pre>
</div> </div>
<p>Message to one device with formated text and image from an external URL.</p> <p>Message to one device with formatted text and image from an external URL.</p>
<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w"> <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
</span><span class="nt">"title"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Test to 1 device with image from an url"</span><span class="p">,</span><span class="w"> </span><span class="nt">"title"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Test to 1 device with image from an url"</span><span class="p">,</span><span class="w">
</span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Attention [i]italic[/i] Text[br][url=https://home-assistant.io/]Testlink[/url]"</span><span class="p">,</span><span class="w"> </span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Attention [i]italic[/i] Text[br][url=https://home-assistant.io/]Testlink[/url]"</span><span class="p">,</span><span class="w">
@ -127,7 +127,7 @@
</span><span class="p">}</span><span class="w"> </span><span class="p">}</span><span class="w">
</span></code></pre> </span></code></pre>
</div> </div>
<p>Message to two devices and one device group with formated text and local image.</p> <p>Message to two devices and one device group with formatted text and local image.</p>
<div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w"> <div class="language-json highlighter-rouge"><pre class="highlight"><code><span class="p">{</span><span class="w">
</span><span class="nt">"title"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Test to 3 devices with local image"</span><span class="p">,</span><span class="w"> </span><span class="nt">"title"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Test to 3 devices with local image"</span><span class="p">,</span><span class="w">
</span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Attention [i]italic[/i] Text[br][url=https://home-assistant.io/]Testlink[/url]"</span><span class="p">,</span><span class="w"> </span><span class="nt">"message"</span><span class="p">:</span><span class="w"> </span><span class="s2">"Attention [i]italic[/i] Text[br][url=https://home-assistant.io/]Testlink[/url]"</span><span class="p">,</span><span class="w">

2
components/pilight/index.html
View file

@ -89,7 +89,7 @@
<li><strong>host</strong> (<em>Required</em>): The IP address of the computer running the pilight-daemon, e.g. 192.168.1.32.</li> <li><strong>host</strong> (<em>Required</em>): The IP address of the computer running the pilight-daemon, e.g. 192.168.1.32.</li>
<li><strong>port</strong> (<em>Required</em>): The network port to connect to. The usual port is <a href="https://manual.pilight.org/development/api.html">5000</a>.</li> <li><strong>port</strong> (<em>Required</em>): The network port to connect to. The usual port is <a href="https://manual.pilight.org/development/api.html">5000</a>.</li>
<li><strong>send_delay</strong> (<em>Optional</em>): You can define a send delay as a fraction of seconds if you experience transmission problems when you try to switch multiple switches at once. This can happen when you use a <a href="https://github.com/pilight/pilight-usb-nano">pilight USB Nano</a> as hardware and switches a whole group of multiple switches on or off. Tested values are between 0.3 and 0.8 seconds depending on the hardware.</li> <li><strong>send_delay</strong> (<em>Optional</em>): You can define a send delay as a fraction of seconds if you experience transmission problems when you try to switch multiple switches at once. This can happen when you use a <a href="https://github.com/pilight/pilight-usb-nano">pilight USB Nano</a> as hardware and switches a whole group of multiple switches on or off. Tested values are between 0.3 and 0.8 seconds depending on the hardware.</li>
<li><strong>whitelist</strong> (<em>Optional</em>): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbours weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.</li> <li><strong>whitelist</strong> (<em>Optional</em>): You can define a whitelist to prevent that too many unwanted RF codes (e.g. the neighbors weather station) are put on your HA event bus. All defined subsections have to be matched. A subsection is matched if one of the items are true.</li>
</ul> </ul>
<p>In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight <a href="https://manual.pilight.org/development/api.html">API</a>.</p> <p>In this example only received RF codes using a daycom or Intertechno protocol are put on the event bus and only when the device id is 42. For more possible settings please look at the receiver section of the pilight <a href="https://manual.pilight.org/development/api.html">API</a>.</p>
<p>A full configuration sample could look like the sample below:</p> <p>A full configuration sample could look like the sample below:</p>

2
components/remember_the_milk/index.html
View file

@ -94,7 +94,7 @@
<dl class=""> <dl class="">
<dt><a class="title-link" name="name" href="#name"></a> name</dt> <dt><a class="title-link" name="name" href="#name"></a> name</dt>
<dd> <dd>
<p class="desc"><span class="type">(<span class="string">string</span>)</span><span class="required">(Required)</span><span class="description">Name of the RTM account, as you can have serveral accounts in RTM. The name must be unique.</span></p> <p class="desc"><span class="type">(<span class="string">string</span>)</span><span class="required">(Required)</span><span class="description">Name of the RTM account, as you can have several accounts in RTM. The name must be unique.</span></p>
</dd> </dd>
<dt><a class="title-link" name="api_key" href="#api_key"></a> api_key</dt> <dt><a class="title-link" name="api_key" href="#api_key"></a> api_key</dt>
<dd> <dd>

2
components/sensor.buienradar/index.html
View file

@ -117,7 +117,7 @@
<li><strong>groundtemperature</strong>: The current ground temperature (in <a href="https://en.wikipedia.org/wiki/Celsius">C</a>).</li> <li><strong>groundtemperature</strong>: The current ground temperature (in <a href="https://en.wikipedia.org/wiki/Celsius">C</a>).</li>
<li><strong>windspeed</strong>: The wind speed in <a href="https://en.wikipedia.org/wiki/M/s">m/s</a>.</li> <li><strong>windspeed</strong>: The wind speed in <a href="https://en.wikipedia.org/wiki/M/s">m/s</a>.</li>
<li><strong>windforce</strong>: The wind speed/force in <a href="https://en.wikipedia.org/wiki/Beaufort_scale">Bft</a>.</li> <li><strong>windforce</strong>: The wind speed/force in <a href="https://en.wikipedia.org/wiki/Beaufort_scale">Bft</a>.</li>
<li><strong>winddirection</strong>: Where the wind is coming from: N (North),Z (south), NO (Noth-East), etc.</li> <li><strong>winddirection</strong>: Where the wind is coming from: N (North),Z (south), NO (North-East), etc.</li>
<li><strong>windazimuth</strong>: Where the wind is coming from in degrees, with true north at 0° and progressing clockwise.</li> <li><strong>windazimuth</strong>: Where the wind is coming from in degrees, with true north at 0° and progressing clockwise.</li>
<li><strong>pressure</strong>: The sea-level air pressure in <a href="https://en.wikipedia.org/wiki/Hectopascal">hPa</a>.</li> <li><strong>pressure</strong>: The sea-level air pressure in <a href="https://en.wikipedia.org/wiki/Hectopascal">hPa</a>.</li>
<li><strong>visibility</strong>: Visibility in meters (<a href="https://en.wikipedia.org/wiki/Metre">m</a>).</li> <li><strong>visibility</strong>: Visibility in meters (<a href="https://en.wikipedia.org/wiki/Metre">m</a>).</li>

6
components/sensor.deutsche_bahn/index.html
View file

@ -8,7 +8,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Deutsche Bahn - Home Assistant</title> <title>Deutsche Bahn - Home Assistant</title>
<meta name="author" content="Home Assistant"> <meta name="author" content="Home Assistant">
<meta name="description" content="Instructions how to integrate timetable data for travelling in Germany within Home Assistant."> <meta name="description" content="Instructions how to integrate timetable data for traveling in Germany within Home Assistant.">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/components/sensor.deutsche_bahn/"> <link rel="canonical" href="https://home-assistant.io/components/sensor.deutsche_bahn/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
@ -16,12 +16,12 @@
<meta property="og:site_name" content="Home Assistant"> <meta property="og:site_name" content="Home Assistant">
<meta property="og:url" content="https://home-assistant.io/components/sensor.deutsche_bahn/"> <meta property="og:url" content="https://home-assistant.io/components/sensor.deutsche_bahn/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="Instructions how to integrate timetable data for travelling in Germany within Home Assistant."> <meta property="og:description" content="Instructions how to integrate timetable data for traveling in Germany within Home Assistant.">
<meta property="og:image" content="https://home-assistant.io/images/default-social.png"> <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
<meta name="twitter:card" content="summary_large_image"> <meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@home_assistant"> <meta name="twitter:site" content="@home_assistant">
<meta name="twitter:title" content="Deutsche Bahn"> <meta name="twitter:title" content="Deutsche Bahn">
<meta name="twitter:description" content="Instructions how to integrate timetable data for travelling in Germany within Home Assistant."> <meta name="twitter:description" content="Instructions how to integrate timetable data for traveling in Germany within Home Assistant.">
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png"> <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet"> <link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml"> <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

6
components/sensor.dublin_bus_transport/index.html
View file

@ -8,7 +8,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Dublin Bus Transport - Home Assistant</title> <title>Dublin Bus Transport - Home Assistant</title>
<meta name="author" content="Home Assistant"> <meta name="author" content="Home Assistant">
<meta name="description" content="Instructions how to integrate timetable data for travelling on Dublin Bus within Home Assistant."> <meta name="description" content="Instructions how to integrate timetable data for traveling on Dublin Bus within Home Assistant.">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/components/sensor.dublin_bus_transport/"> <link rel="canonical" href="https://home-assistant.io/components/sensor.dublin_bus_transport/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
@ -16,12 +16,12 @@
<meta property="og:site_name" content="Home Assistant"> <meta property="og:site_name" content="Home Assistant">
<meta property="og:url" content="https://home-assistant.io/components/sensor.dublin_bus_transport/"> <meta property="og:url" content="https://home-assistant.io/components/sensor.dublin_bus_transport/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="Instructions how to integrate timetable data for travelling on Dublin Bus within Home Assistant."> <meta property="og:description" content="Instructions how to integrate timetable data for traveling on Dublin Bus within Home Assistant.">
<meta property="og:image" content="https://home-assistant.io/images/default-social.png"> <meta property="og:image" content="https://home-assistant.io/images/default-social.png">
<meta name="twitter:card" content="summary_large_image"> <meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@home_assistant"> <meta name="twitter:site" content="@home_assistant">
<meta name="twitter:title" content="Dublin Bus Transport"> <meta name="twitter:title" content="Dublin Bus Transport">
<meta name="twitter:description" content="Instructions how to integrate timetable data for travelling on Dublin Bus within Home Assistant."> <meta name="twitter:description" content="Instructions how to integrate timetable data for traveling on Dublin Bus within Home Assistant.">
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png"> <meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet"> <link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml"> <link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">

Some files were not shown because too many files have changed in this diff Show more