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

Site updated at 2018-01-28 22:02:31 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-28 22:02:31 +00:00
parent 57a21e9eb0
commit 01b474f87c
268 changed files with 412 additions and 412 deletions
Download patch file Download diff file Expand all files Collapse all files

8
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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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>
@ -1477,7 +1477,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 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> <p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides a detailed guide about setting 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>
@ -1750,7 +1750,7 @@ INFO: -----------------------------------------------------------
</code></pre> </code></pre>
</div> </div>
<p>This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to <code class="highlighter-rouge">mqtt_ttn</code> sensor which allows you to select the device.</p> <p>This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to <code class="highlighter-rouge">mqtt_ttn</code> sensor which allows you to select the device.</p>
]]></content> ]]></content>
</entry> </entry>
@ -2686,7 +2686,7 @@ Demo is running... -&gt; CTRL + C to shutdown
<h2><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking Changes</h2> <h2><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking Changes</h2>
<ul> <ul>
<li>history_graph component: If your component used <code class="highlighter-rouge">history.get_significant_states</code> function then you need to adjust the string <code class="highlighter-rouge">entitity_id</code> parameter has been changed to a list of strings <code class="highlighter-rouge">entity_ids</code> parameter. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9472">#9472</a>) (<a href="https://home-assistant.io/components/history_graph/">history_graph docs</a>) (breaking change)</li> <li>history_graph component: If your component used <code class="highlighter-rouge">history.get_significant_states</code> function then you need to adjust the string <code class="highlighter-rouge">entity_id</code> parameter has been changed to a list of strings <code class="highlighter-rouge">entity_ids</code> parameter. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9472">#9472</a>) (<a href="https://home-assistant.io/components/history_graph/">history_graph docs</a>) (breaking change)</li>
<li>UPNP component: The <code class="highlighter-rouge">external_port</code> configuration option was removed. (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9560">#9560</a>) (<a href="https://home-assistant.io/components/upnp/">upnp docs</a>) (breaking change)</li> <li>UPNP component: The <code class="highlighter-rouge">external_port</code> configuration option was removed. (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9560">#9560</a>) (<a href="https://home-assistant.io/components/upnp/">upnp docs</a>) (breaking change)</li>
<li>New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by “_” and no longer “ “. (<a href="https://github.com/w1ll1am23">@w1ll1am23</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9303">#9303</a>) (<a href="https://home-assistant.io/components/wink/">wink docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.wink/">binary_sensor.wink docs</a>) (<a href="https://home-assistant.io/components/lock.wink/">lock.wink docs</a>) (breaking change)</li> <li>New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by “_” and no longer “ “. (<a href="https://github.com/w1ll1am23">@w1ll1am23</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9303">#9303</a>) (<a href="https://home-assistant.io/components/wink/">wink docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.wink/">binary_sensor.wink docs</a>) (<a href="https://home-assistant.io/components/lock.wink/">lock.wink docs</a>) (breaking change)</li>
<li>TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. (<a href="https://github.com/djchen">@djchen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9607">#9607</a>) (<a href="https://home-assistant.io/components/switch.tplink/">switch.tplink docs</a>) (breaking change)</li> <li>TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. (<a href="https://github.com/djchen">@djchen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9607">#9607</a>) (<a href="https://home-assistant.io/components/switch.tplink/">switch.tplink docs</a>) (breaking change)</li>

20
blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
View file

@ -6,23 +6,23 @@
<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>MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported - Home Assistant</title> <title>MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported - Home Assistant</title>
<meta name="author" content="Paulus Schoutsen"> <meta name="author" content="Paulus Schoutsen">
<meta name="description" content="New support for MQTT, Rasperry PI GPIO, Logitech Squeezebox and ASUSWRT routers"> <meta name="description" content="New support for MQTT, Rasperry Pi GPIO, Logitech Squeezebox and ASUSWRT routers">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/"> <link rel="canonical" href="https://home-assistant.io/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
<meta property="og:title" content="MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported"> <meta property="og:title" content="MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported">
<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/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/"> <meta property="og:url" content="https://home-assistant.io/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="New support for MQTT, Rasperry PI GPIO, Logitech Squeezebox and ASUSWRT routers"> <meta property="og:description" content="New support for MQTT, Rasperry Pi GPIO, Logitech Squeezebox and ASUSWRT routers">
<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="MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported"> <meta name="twitter:title" content="MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported">
<meta name="twitter:description" content="New support for MQTT, Rasperry PI GPIO, Logitech Squeezebox and ASUSWRT routers"> <meta name="twitter:description" content="New support for MQTT, Rasperry Pi GPIO, Logitech Squeezebox and ASUSWRT routers">
<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">
@ -70,7 +70,7 @@
<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="post"> <article class="post">
<header> <header>
<h1 class="title indent">MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported</h1> <h1 class="title indent">MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported</h1>
<div class="meta clearfix"> <div class="meta clearfix">
<time datetime="2015-08-09T18:01:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 9, 2015</time> <time datetime="2015-08-09T18:01:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 9, 2015</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span> <span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
@ -86,7 +86,7 @@
>Comments</a> >Comments</a>
</div> </div>
</header> </header>
<p>It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to <a href="https://github.com/balloob">@balloob</a>. If you’re a developer, make sure you read up on <a href="https://github.com/home-assistant/home-assistant/pull/251">the deprecation notices</a>. <a href="https://github.com/fabaff">@fabaff</a> did another great round of documentating all the various components.</p> <p>It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to <a href="https://github.com/balloob">@balloob</a>. If you’re a developer, make sure you read up on <a href="https://github.com/home-assistant/home-assistant/pull/251">the deprecation notices</a>. <a href="https://github.com/fabaff">@fabaff</a> did another great round of documenting all the various components.</p>
<p><strong>MQTT Support</strong> <p><strong>MQTT Support</strong>
<img src="/images/supported_brands/mqtt.png" style="border:none; box-shadow: none; float: right;" height="50" /> The big new addition in this release is the support for the MQTT protocol by <a href="https://github.com/fabaff">@fabaff</a> with some help from <a href="https://github.com/balloob">@balloob</a>. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (<a href="https://github.com/home-assistant/home-assistant/blob/dev/config/custom_components/mqtt_example.py">see the example</a>) and also support for the automation component <a href="/getting-started/automation-trigger/#mqtt-trigger">has been added</a>. For more information, see <a href="/components/mqtt/">the MQTT component page</a>.</p> <img src="/images/supported_brands/mqtt.png" style="border:none; box-shadow: none; float: right;" height="50" /> The big new addition in this release is the support for the MQTT protocol by <a href="https://github.com/fabaff">@fabaff</a> with some help from <a href="https://github.com/balloob">@balloob</a>. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (<a href="https://github.com/home-assistant/home-assistant/blob/dev/config/custom_components/mqtt_example.py">see the example</a>) and also support for the automation component <a href="/getting-started/automation-trigger/#mqtt-trigger">has been added</a>. For more information, see <a href="/components/mqtt/">the MQTT component page</a>.</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>
@ -101,8 +101,8 @@
</code></pre> </code></pre>
</div> </div>
<a name="read-more"></a> <a name="read-more"></a>
<p><strong>Raspberry PI GPIO Support</strong> <p><strong>Raspberry Pi GPIO Support</strong>
<img src="/images/supported_brands/raspberry-pi.png" style="border:none; box-shadow: none; float: right;" height="50" /> <a href="https://github.com/gbarba">@gbarba</a> has contributed support to use the general purpose input and output pins on a Raspberry PI as switches inside Home Assistant.</p> <img src="/images/supported_brands/raspberry-pi.png" style="border:none; box-shadow: none; float: right;" height="50" /> <a href="https://github.com/gbarba">@gbarba</a> has contributed support to use the general purpose input and output pins on a Raspberry Pi as switches inside Home Assistant.</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">switch</span><span class="pi">:</span> <span class="s">switch</span><span class="pi">:</span>
<span class="s">platform</span><span class="pi">:</span> <span class="s">rpi_gpio</span> <span class="s">platform</span><span class="pi">:</span> <span class="s">rpi_gpio</span>

2
blog/2016/02/09/Smarter-Smart-Things-with-MQTT-and-Home-Assistant/index.html
View file

@ -236,7 +236,7 @@ Z-Wave light bulb |
<p>There are a lot of stops along the way for these events, but each piece is a simple translation layer to shuttle the events between systems.</p> <p>There are a lot of stops along the way for these events, but each piece is a simple translation layer to shuttle the events between systems.</p>
<h3>Future Improvements</h3> <h3>Future Improvements</h3>
<ul> <ul>
<li><strong>Raspberry pi</strong>: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point.</li> <li><strong>Raspberry Pi</strong>: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point.</li>
<li><strong>Authentication for MQTT</strong>: At the moment, the MQTT bridge doesn’t understand how to authenticate to MQTT, so only unauthenticated MQTT is supported. This is mitigated to some degree if you use our Docker Compose config, because MQTT’s port is not actually shared publicly.</li> <li><strong>Authentication for MQTT</strong>: At the moment, the MQTT bridge doesn’t understand how to authenticate to MQTT, so only unauthenticated MQTT is supported. This is mitigated to some degree if you use our Docker Compose config, because MQTT’s port is not actually shared publicly.</li>
<li><strong>Authentication for MQTT Bridge</strong>: Right now the bridge expects that anyone subscribing is the SmartThings hub. This could use proper authentication.</li> <li><strong>Authentication for MQTT Bridge</strong>: Right now the bridge expects that anyone subscribing is the SmartThings hub. This could use proper authentication.</li>
</ul> </ul>

2
blog/2016/04/07/static-website/index.html
View file

@ -94,7 +94,7 @@
<a name="read-more"></a> <a name="read-more"></a>
<p>In the past the buzz word “Smart mirror” was used a couple of times in our <a href="https://discord.gg/c5DvZ4e">chatroom</a> and even made it into the <a href="https://github.com/home-assistant/home-assistant/issues/1392">issue tracker</a>. The existing solutions (<a href="http://docs.smart-mirror.io/">Smart mirror</a>, <a href="http://michaelteeuw.nl/tagged/magicmirror">MagicMirror</a>, and <a href="https://github.com/HannahMitt/HomeMirror">HomeMirror</a>) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.</p> <p>In the past the buzz word “Smart mirror” was used a couple of times in our <a href="https://discord.gg/c5DvZ4e">chatroom</a> and even made it into the <a href="https://github.com/home-assistant/home-assistant/issues/1392">issue tracker</a>. The existing solutions (<a href="http://docs.smart-mirror.io/">Smart mirror</a>, <a href="http://michaelteeuw.nl/tagged/magicmirror">MagicMirror</a>, and <a href="https://github.com/HannahMitt/HomeMirror">HomeMirror</a>) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.</p>
<p>There are plenty of ways to achieve this…<a href="/developers/rest_api/">RESTful API</a>, <a href="/developers/python_api/">Python API</a>, or one of the <a href="/components/#history">history components</a>. If it is to be a web page I’m using the <a href="/components/mqtt_eventstream/">MQTT Eventstream component</a> and <a href="http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src">mqttws31.js</a>.</p> <p>There are plenty of ways to achieve this…<a href="/developers/rest_api/">RESTful API</a>, <a href="/developers/python_api/">Python API</a>, or one of the <a href="/components/#history">history components</a>. If it is to be a web page I’m using the <a href="/components/mqtt_eventstream/">MQTT Eventstream component</a> and <a href="http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.javascript.git/tree/src">mqttws31.js</a>.</p>
<p>The <a href="https://pypi.python.org/pypi/hbmqtt">HBMQTT</a> broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It’s a matter of minutes. OK, it took a little longer because I’m not a Javascript guy to create the software part that will show details about your environment. The source is available at <a href="https://github.com/fabaff/home-assistant-display">https://github.com/fabaff/home-assistant-display</a> and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it’s a only prototype and showcase to include an image in this blog post.</p> <p>The <a href="https://pypi.python.org/pypi/hbmqtt">HBMQTT</a> broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It’s a matter of minutes. OK, it took a little longer because I’m not a Javascript guy to create the software part that will show details about your environment. The source is available at <a href="https://github.com/fabaff/home-assistant-display">https://github.com/fabaff/home-assistant-display</a> and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it’s only a prototype and showcase to include an image in this blog post.</p>
<p>I hope that this little article could give you an idea of extending Home Assistant in an unconventional way.</p> <p>I hope that this little article could give you an idea of extending Home Assistant in an unconventional way.</p>
</article> </article>
<div id='post-comments'></div> <div id='post-comments'></div>

2
blog/2016/04/09/onkyo-panasonic-gtfs-and-config-validation/index.html
View file

@ -86,7 +86,7 @@
>Comments</a> >Comments</a>
</div> </div>
</header> </header>
<p>Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to <a href="https://github.com/jaharkes/">@jaharkes</a> for his hard work on this. Config validation is still in it’s early stages. More common platforms and components have been added but we didn’t do everything yet.</p> <p>Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to <a href="https://github.com/jaharkes/">@jaharkes</a> for his hard work on this. Config validation is still in its early stages. More common platforms and components have been added but we didn’t do everything yet.</p>
<p>When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.</p> <p>When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.</p>
<p>Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.</p> <p>Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.</p>
<p><img src="/images/supported_brands/onkyo.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/loop.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/panasonic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /></p> <p><img src="/images/supported_brands/onkyo.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/loop.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/panasonic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /></p>

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

@ -87,7 +87,7 @@
</div> </div>
</header> </header>
<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>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">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>Since the last release we have moved all Home Assistant source code etc into its 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>

2
blog/2016/05/26/ibeacons-how-to-track-things-that-cant-track-themselves-part-ii/index.html
View file

@ -174,7 +174,7 @@
<li>I’ve found that beacons (especially the low power Estimote Nearables) can get disconnected for a few seconds so it’s best to wait a minute or so before deciding that you’ve left your keys behind)</li> <li>I’ve found that beacons (especially the low power Estimote Nearables) can get disconnected for a few seconds so it’s best to wait a minute or so before deciding that you’ve left your keys behind)</li>
</ol> </ol>
<h3><a class="title-link" name="using-both-types-of-ibeacons-at-the-same-time" href="#using-both-types-of-ibeacons-at-the-same-time"></a> Using both types of iBeacons at the same time</h3> <h3><a class="title-link" name="using-both-types-of-ibeacons-at-the-same-time" href="#using-both-types-of-ibeacons-at-the-same-time"></a> Using both types of iBeacons at the same time</h3>
<p>Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I’ve been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.</p> <p>Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I’ve been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.</p>
<p class="img"> <p class="img">
<img width="300" src="http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg" /> <img width="300" src="http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg" />
</p> </p>

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 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>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 its 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/16/we-have-apps-now/index.html
View file

@ -98,13 +98,13 @@
<li>Is it open and expandable?</li> <li>Is it open and expandable?</li>
<li>Does it run locally without any reliance on the cloud?</li> <li>Does it run locally without any reliance on the cloud?</li>
</ul> </ul>
<p>In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and it’s Restful API.</p> <p>In my opinion, Home Assistant accomplishes the majority of these very well with a combination of Automations, Scripts and Templates, and its Restful API.</p>
<p>So why <code class="highlighter-rouge">AppDaemon</code>? <code class="highlighter-rouge">AppDaemon</code> is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table:</p> <p>So why <code class="highlighter-rouge">AppDaemon</code>? <code class="highlighter-rouge">AppDaemon</code> is not meant to replace Home Assistant Automations and Scripts, rather complement them. For a lot of things, automations work well and can be very succinct. However, there is a class of more complex automations for which they become harder to use, and appdeamon then comes into its own. It brings quite a few things to the table:</p>
<ul> <ul>
<li>New paradigm - some problems require a procedural and/or iterative approach, and <code class="highlighter-rouge">AppDaemon</code> Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can’t</li> <li>New paradigm - some problems require a procedural and/or iterative approach, and <code class="highlighter-rouge">AppDaemon</code> Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can’t</li>
<li>Ease of use - <code class="highlighter-rouge">AppDaemon</code>’s API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as “Pythonic” as possible, experienced Python programmers should feel right at home.</li> <li>Ease of use - <code class="highlighter-rouge">AppDaemon</code>’s API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as “Pythonic” as possible, experienced Python programmers should feel right at home.</li>
<li>Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file</li> <li>Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file</li>
<li>Dynamic - <code class="highlighter-rouge">AppDaemon</code> has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to it’s loose coupling. However, it is better than that - the user can make changes to code and <code class="highlighter-rouge">AppDaemon</code> will automatically reload the code, figure out which Apps were using it and restart them to use the new code without the need to restart <code class="highlighter-rouge">AppDaemon</code> itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result.</li> <li>Dynamic - <code class="highlighter-rouge">AppDaemon</code> has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to its loose coupling. However, it is better than that - the user can make changes to code and <code class="highlighter-rouge">AppDaemon</code> will automatically reload the code, figure out which Apps were using it and restart them to use the new code without the need to restart <code class="highlighter-rouge">AppDaemon</code> itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result.</li>
<li>Complex logic - Python’s If/Else constructs are clearer and easier to code for arbitrarily complex nested logic</li> <li>Complex logic - Python’s If/Else constructs are clearer and easier to code for arbitrarily complex nested logic</li>
<li>Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened</li> <li>Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened</li>
<li>All the power of Python - use any of Python’s libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!</li> <li>All the power of Python - use any of Python’s libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!</li>

2
blog/2016/10/08/hassbian-rest-digital-ocean/index.html
View file

@ -101,7 +101,7 @@
<p class="img"> <p class="img">
<img src="/images/screenshots/stats-sensor.png" /> <img src="/images/screenshots/stats-sensor.png" />
</p> </p>
<p>As the results are processed on-the-fly you still need to use the data from your database for a in-depth analysis of your stored information. Check the latest <a href="http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb">notebook</a> for doing statistics with your Home Assistant database.</p> <p>As the results are processed on-the-fly you still need to use the data from your database for an in-depth analysis of your stored information. Check the latest <a href="http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb">notebook</a> for doing statistics with your Home Assistant database.</p>
<h3><a class="title-link" name="rest-we-dont" href="#rest-we-dont"></a> REST! We don’t…</h3> <h3><a class="title-link" name="rest-we-dont" href="#rest-we-dont"></a> REST! We don’t…</h3>
<p>There was a lot of work done on our implementation which are working with RESTful APIs. <a href="https://github.com/w1ll1am23">@w1ll1am23</a> extended the <a href="https://arest.io/">aREST</a> platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.</p> <p>There was a lot of work done on our implementation which are working with RESTful APIs. <a href="https://github.com/w1ll1am23">@w1ll1am23</a> extended the <a href="https://arest.io/">aREST</a> platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.</p>
<p>The <a href="/components/sensor.rest/">REST sensor</a> supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.</p> <p>The <a href="/components/sensor.rest/">REST sensor</a> supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.</p>

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

@ -214,7 +214,7 @@
<li>Due to massive improvements of the <a href="https://home-assistant.io/components/wink/">Wink</a> integration, the names of your binary sensors will change and new devices can show up.</li> <li>Due to massive improvements of the <a href="https://home-assistant.io/components/wink/">Wink</a> integration, the names of your binary sensors will change and new devices can show up.</li>
<li>The <a href="https://home-assistant.io/components/mysensors/">MySensors</a> component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.</li> <li>The <a href="https://home-assistant.io/components/mysensors/">MySensors</a> component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.</li>
<li>The <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> service <code class="highlighter-rouge">sonos_group_players</code> was removed. Use now <code class="highlighter-rouge">sonos_join</code> for this function.</li> <li>The <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> service <code class="highlighter-rouge">sonos_group_players</code> was removed. Use now <code class="highlighter-rouge">sonos_join</code> for this function.</li>
<li>TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. <code class="highlighter-rouge">HASH_LANG_PLATFORM.xxx</code> -&gt; <code class="highlighter-rouge">HASH_LANG_OPTIONS_PLATFORM.xxx</code>, replace <em>OPTIONS</em> with <code class="highlighter-rouge">-</code> on exiting platforms.</li> <li>TTS cache have change for the last time. Files use now also an option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. <code class="highlighter-rouge">HASH_LANG_PLATFORM.xxx</code> -&gt; <code class="highlighter-rouge">HASH_LANG_OPTIONS_PLATFORM.xxx</code>, replace <em>OPTIONS</em> with <code class="highlighter-rouge">-</code> on exiting platforms.</li>
</ul> </ul>
<h3><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h3> <h3><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h3>
<p>…don’t hesitate to use our <a href="https://community.home-assistant.io/">Forum</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.</p> <p>…don’t hesitate to use our <a href="https://community.home-assistant.io/">Forum</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.</p>

6
blog/2017/02/03/babyphone/index.html
View file

@ -94,14 +94,14 @@
<p class="note"> <p class="note">
We change the platform name for binary sensor in 0.38 from <code class="highlighter-rouge">ffmpeg</code> to <code class="highlighter-rouge">ffmpeg_noise</code>. Also all service going to component and was rename from <code class="highlighter-rouge">binary_sensor.ffmpeg_xy</code> to <code class="highlighter-rouge">ffmpeg.xy</code>. We change the platform name for binary sensor in 0.38 from <code class="highlighter-rouge">ffmpeg</code> to <code class="highlighter-rouge">ffmpeg_noise</code>. Also all service going to component and was rename from <code class="highlighter-rouge">binary_sensor.ffmpeg_xy</code> to <code class="highlighter-rouge">ffmpeg.xy</code>.
</p> </p>
<p>On Raspbian Jessie, you can setup <a href="/components/ffmpeg">FFmpeg</a> and install a <a href="http://icecast.org/">icecast2</a> server using:</p> <p>On Raspbian Jessie, you can setup <a href="/components/ffmpeg">FFmpeg</a> and install an <a href="http://icecast.org/">icecast2</a> server using:</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo <span class="nb">echo</span> <span class="s2">"deb http://ftp.debian.org/debian jessie-backports main"</span> &gt;&gt; /etc/apt/sources.list <div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo <span class="nb">echo</span> <span class="s2">"deb http://ftp.debian.org/debian jessie-backports main"</span> &gt;&gt; /etc/apt/sources.list
<span class="gp">$ </span>sudo apt-get update <span class="gp">$ </span>sudo apt-get update
<span class="gp">$ </span>sudo apt-get -t jessie-backports install ffmpeg <span class="gp">$ </span>sudo apt-get -t jessie-backports install ffmpeg
<span class="gp">$ </span>sudo apt-get install icecast2 <span class="gp">$ </span>sudo apt-get install icecast2
</code></pre> </code></pre>
</div> </div>
<p>We setup a icecast mount point for our babyphone and update <code class="highlighter-rouge">/etc/icecast2/icecast.xml</code>:</p> <p>We setup an icecast mount point for our babyphone and update <code class="highlighter-rouge">/etc/icecast2/icecast.xml</code>:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>&lt;mount&gt; <div class="highlighter-rouge"><pre class="highlight"><code>&lt;mount&gt;
&lt;mount-name&gt;/babyphone.mp3&lt;/mount-name&gt; &lt;mount-name&gt;/babyphone.mp3&lt;/mount-name&gt;
&lt;stream-name&gt;Babyphone&lt;/stream-name&gt; &lt;stream-name&gt;Babyphone&lt;/stream-name&gt;
@ -152,7 +152,7 @@ We change the platform name for binary sensor in 0.38 from <code class="highligh
<span class="s">entity_id</span><span class="pi">:</span> <span class="s">binary_sensor.ffmpeg_noise</span> <span class="s">entity_id</span><span class="pi">:</span> <span class="s">binary_sensor.ffmpeg_noise</span>
</code></pre> </code></pre>
</div> </div>
<h3><a class="title-link" name="trigger-a-alarm" href="#trigger-a-alarm"></a> Trigger a alarm</h3> <h3><a class="title-link" name="trigger-an-alarm" href="#trigger-an-alarm"></a> Trigger an alarm</h3>
<p>Now we can make a lot stuff. Here is a simple example of an automation what should be possible with Sonos speakers.</p> <p>Now we can make a lot stuff. Here is a simple example of an automation what should be possible with Sonos speakers.</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">automation</span><span class="pi">:</span>
<span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Babyphone</span><span class="nv"> </span><span class="s">alarm</span><span class="nv"> </span><span class="s">on'</span> <span class="pi">-</span> <span class="s">alias</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Babyphone</span><span class="nv"> </span><span class="s">alarm</span><span class="nv"> </span><span class="s">on'</span>

4
blog/2017/02/25/config-panel-and-state-restoration/index.html
View file

@ -124,8 +124,8 @@
<p>We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?</p> <p>We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?</p>
<p>So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.</p> <p>So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.</p>
<p><a href="https://jsfiddle.net/balloob/d2e56q6f/74/"><strong>Update: the online tool can be found here.</strong></a></p> <p><a href="https://jsfiddle.net/balloob/d2e56q6f/74/"><strong>Update: the online tool can be found here.</strong></a></p>
<h4>Customize has been reverted to it’s original config</h4> <h4>Customize has been reverted to its original config</h4>
<p>The old customize is back. The options to match by domain or using glob have been moved to it’s own options. It will now look like this:</p> <p>The old customize is back. The options to match by domain or using glob have been moved to its own options. It will now look like this:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">homeassistant</span><span class="pi">:</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">homeassistant</span><span class="pi">:</span>
<span class="s">customize</span><span class="pi">:</span> <span class="s">customize</span><span class="pi">:</span>
<span class="s">light.kitchen</span><span class="pi">:</span> <span class="s">light.kitchen</span><span class="pi">:</span>

2
blog/2017/10/07/release-55/index.html
View file

@ -128,7 +128,7 @@
<a name="read-more"></a> <a name="read-more"></a>
<h2><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking Changes</h2> <h2><a class="title-link" name="breaking-changes" href="#breaking-changes"></a> Breaking Changes</h2>
<ul> <ul>
<li>history_graph component: If your component used <code class="highlighter-rouge">history.get_significant_states</code> function then you need to adjust the string <code class="highlighter-rouge">entitity_id</code> parameter has been changed to a list of strings <code class="highlighter-rouge">entity_ids</code> parameter. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9472">#9472</a>) (<a href="https://home-assistant.io/components/history_graph/">history_graph docs</a>) (breaking change)</li> <li>history_graph component: If your component used <code class="highlighter-rouge">history.get_significant_states</code> function then you need to adjust the string <code class="highlighter-rouge">entity_id</code> parameter has been changed to a list of strings <code class="highlighter-rouge">entity_ids</code> parameter. (<a href="https://github.com/andrey-git">@andrey-git</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9472">#9472</a>) (<a href="https://home-assistant.io/components/history_graph/">history_graph docs</a>) (breaking change)</li>
<li>UPNP component: The <code class="highlighter-rouge">external_port</code> configuration option was removed. (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9560">#9560</a>) (<a href="https://home-assistant.io/components/upnp/">upnp docs</a>) (breaking change)</li> <li>UPNP component: The <code class="highlighter-rouge">external_port</code> configuration option was removed. (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9560">#9560</a>) (<a href="https://home-assistant.io/components/upnp/">upnp docs</a>) (breaking change)</li>
<li>New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by “_” and no longer “ “. (<a href="https://github.com/w1ll1am23">@w1ll1am23</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9303">#9303</a>) (<a href="https://home-assistant.io/components/wink/">wink docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.wink/">binary_sensor.wink docs</a>) (<a href="https://home-assistant.io/components/lock.wink/">lock.wink docs</a>) (breaking change)</li> <li>New Wink services: pair new device, rename, delete and add new lock key code. All device attributes that are multi-words are now separated by “_” and no longer “ “. (<a href="https://github.com/w1ll1am23">@w1ll1am23</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9303">#9303</a>) (<a href="https://home-assistant.io/components/wink/">wink docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.wink/">binary_sensor.wink docs</a>) (<a href="https://home-assistant.io/components/lock.wink/">lock.wink docs</a>) (breaking change)</li>
<li>TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. (<a href="https://github.com/djchen">@djchen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9607">#9607</a>) (<a href="https://home-assistant.io/components/switch.tplink/">switch.tplink docs</a>) (breaking change)</li> <li>TP-Link Switch: Attribute names now uses underscores and unnecessary capitalization was removed. (<a href="https://github.com/djchen">@djchen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9607">#9607</a>) (<a href="https://home-assistant.io/components/switch.tplink/">switch.tplink docs</a>) (breaking change)</li>

2
blog/2017/11/10/ttn-with-mqtt/index.html
View file

@ -251,7 +251,7 @@
state_topic: "home/ttn/garden_temp" state_topic: "home/ttn/garden_temp"
</code></pre> </code></pre>
</div> </div>
<p>This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to <code class="highlighter-rouge">mqtt_ttn</code> sensor which allows you to select the device.</p> <p>This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to <code class="highlighter-rouge">mqtt_ttn</code> sensor which allows you to select the device.</p>
</article> </article>
<div id='post-comments'></div> <div id='post-comments'></div>
<section id="disqus"> <section id="disqus">

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 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> <p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides a detailed guide about setting 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/archives/index.html
View file

@ -443,7 +443,7 @@
</time> </time>
</div> </div>
<div class="grid__item four-fifths palm-one-whole"> <div class="grid__item four-fifths palm-one-whole">
<h1 class="gamma"><a href="/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported</a></h1> <h1 class="gamma"><a href="/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported</a></h1>
<footer class="meta"> <footer class="meta">
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>

2
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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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>
@ -129,7 +129,7 @@ script:
### <a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time ### <a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time
Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.
<p class='img'> <p class='img'>
<img width='300' src='http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg'> <img width='300' src='http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg'>

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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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>

6
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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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 detailed 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 a detailed guide about setting 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:
@ -446,7 +446,7 @@ sensor:
state_topic: "home/ttn/garden_temp" state_topic: "home/ttn/garden_temp"
``` ```
This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add an configuration variable to `mqtt_ttn` sensor which allows you to select the device. This solution is not production-ready, scalable or stable but it could fill the gape till Home Assistant is able to connect to multiple MQTT brokers. If you have multiple devices relay all messages to your local broker and add a configuration variable to `mqtt_ttn` sensor which allows you to select the device.
]]></content> ]]></content>
</entry> </entry>

4
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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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>
@ -129,7 +129,7 @@ script:
### <a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time ### <a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time
Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.
<p class='img'> <p class='img'>
<img width='300' src='http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg'> <img width='300' src='http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg'>

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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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>
@ -307,7 +307,7 @@ Here is the final sequence of events:
There are a lot of stops along the way for these events, but each piece is a simple translation layer to shuttle the events between systems. There are a lot of stops along the way for these events, but each piece is a simple translation layer to shuttle the events between systems.
### Future Improvements ### Future Improvements
- **Raspberry pi**: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point. - **Raspberry Pi**: There is a lot of interest in getting this running on the Raspberry Pi. It only requires binaries compiled for ARM, so we plan to get ARM-compatible versions of the containers going at some point.
- **Authentication for MQTT**: At the moment, the MQTT bridge doesn't understand how to authenticate to MQTT, so only unauthenticated MQTT is supported. This is mitigated to some degree if you use our Docker Compose config, because MQTT's port is not actually shared publicly. - **Authentication for MQTT**: At the moment, the MQTT bridge doesn't understand how to authenticate to MQTT, so only unauthenticated MQTT is supported. This is mitigated to some degree if you use our Docker Compose config, because MQTT's port is not actually shared publicly.
- **Authentication for MQTT Bridge**: Right now the bridge expects that anyone subscribing is the SmartThings hub. This could use proper authentication. - **Authentication for MQTT Bridge**: Right now the bridge expects that anyone subscribing is the SmartThings hub. This could use proper authentication.

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

@ -4,7 +4,7 @@
<title><![CDATA[Category: Organization | Home Assistant]]></title> <title><![CDATA[Category: Organization | Home Assistant]]></title>
<link href="https://home-assistant.io/blog/categories/organization/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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>
@ -129,7 +129,7 @@ script:
### <a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time ### <a class='title-link' name='using-both-types-of-ibeacons-at-the-same-time' href='#using-both-types-of-ibeacons-at-the-same-time'></a> Using both types of iBeacons at the same time
Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and a iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home. Of course you can use both fixed and mobile beacons at the same time. I want my gates to open when I arrive home in the car - so I use an iBeacon in the car so that I can track the car, and an iBeacon on my drive so that a location update is triggered when I arrive. I've been experimenting with a high power beacon in a waterproof box on my drive which seems to work well to notice when I get home.
<p class='img'> <p class='img'>
<img width='300' src='http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg'> <img width='300' src='http://bluesensenetworks.com/wp-content/uploads/2015/02/BlueBar-Beacon-Long-Range.jpg'>

2
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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/release-notes/index.html
View file

@ -1412,7 +1412,7 @@
</time> </time>
</div> </div>
<div class="grid__item four-fifths palm-one-whole"> <div class="grid__item four-fifths palm-one-whole">
<h1 class="gamma"><a href="/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported</a></h1> <h1 class="gamma"><a href="/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported</a></h1>
<footer class="meta"> <footer class="meta">
<span> <span>
<i class="icon-tags"></i> <i class="icon-tags"></i>

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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/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-28T17:56:25+00:00</updated> <updated>2018-01-28T21:52:35+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/posts/10/index.html
View file

@ -297,7 +297,7 @@ Heatmap
</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 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>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 its 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/posts/12/index.html
View file

@ -312,7 +312,7 @@
</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 traveling 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">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>Since the last release we have moved all Home Assistant source code etc into its 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>
@ -444,7 +444,7 @@
</div> </div>
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to <a href="https://github.com/jaharkes/">@jaharkes</a> for his hard work on this. Config validation is still in it’s early stages. More common platforms and components have been added but we didn’t do everything yet.</p> <p>Another awesome release ready to hit your homes. YAML can be hard for beginners and more experienced automators. So to help catch those pesky errors that sneak into your files we’ve been hard at work to introduce config validation! Especially huge thanks to <a href="https://github.com/jaharkes/">@jaharkes</a> for his hard work on this. Config validation is still in its early stages. More common platforms and components have been added but we didn’t do everything yet.</p>
<p>When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.</p> <p>When we encounter an invalid config we will now write a warning to your logs. You can see those in the frontend by clicking on the last developer tool. We’re looking into options to make it more clear - it is a work in progress.</p>
<p>Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.</p> <p>Another big thing is the addition of GTFS support. You probably don’t know it, but GTFS is the standard that public transit companies all over the world use to distribute their schedule. This means that you can now have the time of the next bus/train/etc right in your frontend.</p>
<p><img src="/images/supported_brands/onkyo.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/loop.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/panasonic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /></p> <p><img src="/images/supported_brands/onkyo.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/loop.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/panasonic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /></p>

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

@ -148,7 +148,7 @@
<article class="listing"> <article class="listing">
<header> <header>
<h1 class="beta"> <h1 class="beta">
<a href="/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">MQTT, Rasperry PI, Logitech Squeezebox and ASUSWRT routers now supported</a> <a href="/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/">MQTT, Rasperry Pi, Logitech Squeezebox and ASUSWRT routers now supported</a>
</h1> </h1>
<div class="meta clearfix"> <div class="meta clearfix">
<time datetime="2015-08-09T18:01:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 9, 2015</time> <time datetime="2015-08-09T18:01:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 9, 2015</time>
@ -166,7 +166,7 @@
</div> </div>
</header> </header>
<div class="entry-content clearfix"> <div class="entry-content clearfix">
<p>It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to <a href="https://github.com/balloob">@balloob</a>. If you’re a developer, make sure you read up on <a href="https://github.com/home-assistant/home-assistant/pull/251">the deprecation notices</a>. <a href="https://github.com/fabaff">@fabaff</a> did another great round of documentating all the various components.</p> <p>It’s time for the August release and there is some serious good stuff this time. The core of Home Assistant has gone some serious clean up and a bump in test coverage thanks to <a href="https://github.com/balloob">@balloob</a>. If you’re a developer, make sure you read up on <a href="https://github.com/home-assistant/home-assistant/pull/251">the deprecation notices</a>. <a href="https://github.com/fabaff">@fabaff</a> did another great round of documenting all the various components.</p>
<p><strong>MQTT Support</strong> <p><strong>MQTT Support</strong>
<img src="/images/supported_brands/mqtt.png" style="border:none; box-shadow: none; float: right;" height="50" /> The big new addition in this release is the support for the MQTT protocol by <a href="https://github.com/fabaff">@fabaff</a> with some help from <a href="https://github.com/balloob">@balloob</a>. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (<a href="https://github.com/home-assistant/home-assistant/blob/dev/config/custom_components/mqtt_example.py">see the example</a>) and also support for the automation component <a href="/getting-started/automation-trigger/#mqtt-trigger">has been added</a>. For more information, see <a href="/components/mqtt/">the MQTT component page</a>.</p> <img src="/images/supported_brands/mqtt.png" style="border:none; box-shadow: none; float: right;" height="50" /> The big new addition in this release is the support for the MQTT protocol by <a href="https://github.com/fabaff">@fabaff</a> with some help from <a href="https://github.com/balloob">@balloob</a>. It will now be possible to integrate any IoT device that talks via MQTT. For the initial release we support connecting Home Assistant to a broker (no TLS yet). Components can now subscribe and publish to MQTT topics (<a href="https://github.com/home-assistant/home-assistant/blob/dev/config/custom_components/mqtt_example.py">see the example</a>) and also support for the automation component <a href="/getting-started/automation-trigger/#mqtt-trigger">has been added</a>. For more information, see <a href="/components/mqtt/">the MQTT component page</a>.</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>

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

@ -357,8 +357,8 @@ Screenshot of all the different functionality the IP webcam integration offers.
<p>We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?</p> <p>We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?</p>
<p>So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.</p> <p>So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.</p>
<p><a href="https://jsfiddle.net/balloob/d2e56q6f/74/"><strong>Update: the online tool can be found here.</strong></a></p> <p><a href="https://jsfiddle.net/balloob/d2e56q6f/74/"><strong>Update: the online tool can be found here.</strong></a></p>
<h4>Customize has been reverted to it’s original config</h4> <h4>Customize has been reverted to its original config</h4>
<p>The old customize is back. The options to match by domain or using glob have been moved to it’s own options. It will now look like this:</p> <p>The old customize is back. The options to match by domain or using glob have been moved to its own options. It will now look like this:</p>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">homeassistant</span><span class="pi">:</span> <div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">homeassistant</span><span class="pi">:</span>
<span class="s">customize</span><span class="pi">:</span> <span class="s">customize</span><span class="pi">:</span>
<span class="s">light.kitchen</span><span class="pi">:</span> <span class="s">light.kitchen</span><span class="pi">:</span>

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

@ -243,7 +243,7 @@
<li>Due to massive improvements of the <a href="https://home-assistant.io/components/wink/">Wink</a> integration, the names of your binary sensors will change and new devices can show up.</li> <li>Due to massive improvements of the <a href="https://home-assistant.io/components/wink/">Wink</a> integration, the names of your binary sensors will change and new devices can show up.</li>
<li>The <a href="https://home-assistant.io/components/mysensors/">MySensors</a> component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.</li> <li>The <a href="https://home-assistant.io/components/mysensors/">MySensors</a> component now requires all persistence file paths to be set if any is set by the user. This is to avoid name conflicts for the paths. If no path is set Home Assistant will set all paths for you.</li>
<li>The <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> service <code class="highlighter-rouge">sonos_group_players</code> was removed. Use now <code class="highlighter-rouge">sonos_join</code> for this function.</li> <li>The <a href="https://home-assistant.io/components/media_player.sonos/">Sonos</a> service <code class="highlighter-rouge">sonos_group_players</code> was removed. Use now <code class="highlighter-rouge">sonos_join</code> for this function.</li>
<li>TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. <code class="highlighter-rouge">HASH_LANG_PLATFORM.xxx</code> -&gt; <code class="highlighter-rouge">HASH_LANG_OPTIONS_PLATFORM.xxx</code>, replace <em>OPTIONS</em> with <code class="highlighter-rouge">-</code> on exiting platforms.</li> <li>TTS cache have change for the last time. Files use now also an option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. <code class="highlighter-rouge">HASH_LANG_PLATFORM.xxx</code> -&gt; <code class="highlighter-rouge">HASH_LANG_OPTIONS_PLATFORM.xxx</code>, replace <em>OPTIONS</em> with <code class="highlighter-rouge">-</code> on exiting platforms.</li>
</ul> </ul>
<h3><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h3> <h3><a class="title-link" name="if-you-need-help" href="#if-you-need-help"></a> If you need help…</h3>
<p>…don’t hesitate to use our <a href="https://community.home-assistant.io/">Forum</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.</p> <p>…don’t hesitate to use our <a href="https://community.home-assistant.io/">Forum</a> or join us for a little <a href="https://discord.gg/c5DvZ4e">chat</a>. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.</p>

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

@ -545,7 +545,7 @@
<p class="img"> <p class="img">
<img src="/images/screenshots/stats-sensor.png" /> <img src="/images/screenshots/stats-sensor.png" />
</p> </p>
<p>As the results are processed on-the-fly you still need to use the data from your database for a in-depth analysis of your stored information. Check the latest <a href="http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb">notebook</a> for doing statistics with your Home Assistant database.</p> <p>As the results are processed on-the-fly you still need to use the data from your database for an in-depth analysis of your stored information. Check the latest <a href="http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb">notebook</a> for doing statistics with your Home Assistant database.</p>
<h3><a class="title-link" name="rest-we-dont" href="#rest-we-dont"></a> REST! We don’t…</h3> <h3><a class="title-link" name="rest-we-dont" href="#rest-we-dont"></a> REST! We don’t…</h3>
<p>There was a lot of work done on our implementation which are working with RESTful APIs. <a href="https://github.com/w1ll1am23">@w1ll1am23</a> extended the <a href="https://arest.io/">aREST</a> platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.</p> <p>There was a lot of work done on our implementation which are working with RESTful APIs. <a href="https://github.com/w1ll1am23">@w1ll1am23</a> extended the <a href="https://arest.io/">aREST</a> platforms to display if an aREST unit is available or not. The aREST implementations are now covered by the configuration check as well. Please check the Breaking changes section for more details.</p>
<p>The <a href="/components/sensor.rest/">REST sensor</a> supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.</p> <p>The <a href="/components/sensor.rest/">REST sensor</a> supports now HTTP authentication (basic and digest) and custom headers. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.</p>

2
components/alarmdecoder/index.html
View file

@ -79,7 +79,7 @@
<p>There is currently support for the following device types within Home Assistant:</p> <p>There is currently support for the following device types within Home Assistant:</p>
<ul> <ul>
<li><a href="/components/binary_sensor.alarmdecoder/">Binary Sensor</a>: Reports on zone status</li> <li><a href="/components/binary_sensor.alarmdecoder/">Binary Sensor</a>: Reports on zone status</li>
<li><a href="/components/sensor.alarmdecoder/">Sensor</a>: Emulates an keypad display</li> <li><a href="/components/sensor.alarmdecoder/">Sensor</a>: Emulates a keypad display</li>
<li><a href="/components/alarm_control_panel.alarmdecoder/">Alarm Control Panel</a>: Reports on alarm status, and can be used to arm/disarm the system</li> <li><a href="/components/alarm_control_panel.alarmdecoder/">Alarm Control Panel</a>: Reports on alarm status, and can be used to arm/disarm the system</li>
</ul> </ul>
<p>This is a fully event-based component. Any event sent by the AlarmDecoder device will be immediately reflected within Home Assistant.</p> <p>This is a fully event-based component. Any event sent by the AlarmDecoder device will be immediately reflected within Home Assistant.</p>

2
components/arduino/index.html
View file

@ -165,7 +165,7 @@ A word of caution: The Arduino boards are not storing states. This means that wi
<a href='/components/rpi_pfio/'>PiFace Digital I/O</a> <a href='/components/rpi_pfio/'>PiFace Digital I/O</a>
</li> </li>
<li> <li>
<a href='/components/rpi_gpio/'>Raspberry PI GPIO</a> <a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a>
</li> </li>
<li> <li>
<a href='/components/raspihats/'>Raspihats</a> <a href='/components/raspihats/'>Raspihats</a>

2
components/bbb_gpio/index.html
View file

@ -135,7 +135,7 @@
<a href='/components/rpi_pfio/'>PiFace Digital I/O</a> <a href='/components/rpi_pfio/'>PiFace Digital I/O</a>
</li> </li>
<li> <li>
<a href='/components/rpi_gpio/'>Raspberry PI GPIO</a> <a href='/components/rpi_gpio/'>Raspberry Pi GPIO</a>
</li> </li>
<li> <li>
<a href='/components/raspihats/'>Raspihats</a> <a href='/components/raspihats/'>Raspihats</a>

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

@ -260,7 +260,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -270,7 +270,7 @@ file:</p>
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -244,7 +244,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -256,7 +256,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

4
components/binary_sensor.arest/index.html
View file

@ -74,7 +74,7 @@
</h1> </h1>
</header> </header>
<hr class="divider"> <hr class="divider">
<p>The <code class="highlighter-rouge">arest</code> binary sensor platform allows you to get all data from your devices (like Arduinos with a ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the <a href="http://arest.io/">aREST</a> RESTful framework.</p> <p>The <code class="highlighter-rouge">arest</code> binary sensor platform allows you to get all data from your devices (like Arduinos with an ethernet/wifi connection, the ESP8266, and the Raspberry Pi) running the <a href="http://arest.io/">aREST</a> RESTful framework.</p>
<p>To use your aREST binary sensor in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p> <p>To use your aREST binary sensor 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>
<span class="s">binary_sensor</span><span class="pi">:</span> <span class="s">binary_sensor</span><span class="pi">:</span>
@ -270,7 +270,7 @@ This sensor is not suitable for fast state changes because there is a high possi
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -243,7 +243,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -249,7 +249,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -298,7 +298,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -266,7 +266,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -241,7 +241,7 @@ To get your Blink binary sensors working with Home Assistant, follow the instruc
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -261,7 +261,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -298,7 +298,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -244,7 +244,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -267,7 +267,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -248,7 +248,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -240,7 +240,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -281,7 +281,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -244,7 +244,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -260,7 +260,7 @@ If the <code class="highlighter-rouge">ffmpeg</code> process is broken, the sens
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -251,7 +251,7 @@ If the <code class="highlighter-rouge">ffmpeg</code> process is broken, the sens
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -272,7 +272,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

8
components/binary_sensor.gc100/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>gc100 Binary Sensor - Home Assistant</title> <title>gc100 Binary Sensor - Home Assistant</title>
<meta name="author" content="Home Assistant"> <meta name="author" content="Home Assistant">
<meta name="description" content="Instructions on how to set up an gc100 binary sensor within Home Assistant."> <meta name="description" content="Instructions on how to set up a gc100 binary sensor 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/binary_sensor.gc100/"> <link rel="canonical" href="https://home-assistant.io/components/binary_sensor.gc100/">
<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/binary_sensor.gc100/"> <meta property="og:url" content="https://home-assistant.io/components/binary_sensor.gc100/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="Instructions on how to set up an gc100 binary sensor within Home Assistant."> <meta property="og:description" content="Instructions on how to set up a gc100 binary sensor 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="gc100 Binary Sensor"> <meta name="twitter:title" content="gc100 Binary Sensor">
<meta name="twitter:description" content="Instructions on how to set up an gc100 binary sensor within Home Assistant."> <meta name="twitter:description" content="Instructions on how to set up a gc100 binary sensor 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">
@ -250,7 +250,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -321,7 +321,7 @@ binary_sensor.home_line_crossing_2
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -256,7 +256,7 @@ Full configuration details can be found on the main <a href="/components/hive/">
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -252,7 +252,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -288,7 +288,7 @@ You should choose a unique device name (DEVICE_NAME) to avoid clashes with other
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -299,7 +299,7 @@ For more information about IHC resource ids see <a href="/components/ihc/#manual
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -242,7 +242,7 @@ component.</p>
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -255,7 +255,7 @@ If you set <code class="highlighter-rouge">show_on_map</code> <code class="highl
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -255,7 +255,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -299,7 +299,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -280,7 +280,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -373,7 +373,7 @@ home/bathroom/switch/button 1
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -359,7 +359,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -285,7 +285,7 @@ The firmware version 2.26 doesn’t support TLS/SSL. This means that you are onl
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -287,7 +287,7 @@ You must have the <a href="/components/nest/">Nest component</a> configured to u
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -290,7 +290,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -266,7 +266,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -260,7 +260,7 @@ You must have the <a href="/components/octoprint/">OctoPrint component</a> confi
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -272,7 +272,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -265,7 +265,7 @@ When run on Windows systems, the round trip time attributes are rounded to the n
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -257,7 +257,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

10
components/binary_sensor.raspihats/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>Raspihats Binary Sensor - Home Assistant</title> <title>Raspihats Binary Sensor - Home Assistant</title>
<meta name="author" content="Home Assistant"> <meta name="author" content="Home Assistant">
<meta name="description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor."> <meta name="description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor.">
<meta name="viewport" content="width=device-width"> <meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/components/binary_sensor.raspihats/"> <link rel="canonical" href="https://home-assistant.io/components/binary_sensor.raspihats/">
<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/binary_sensor.raspihats/"> <meta property="og:url" content="https://home-assistant.io/components/binary_sensor.raspihats/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor."> <meta property="og:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor.">
<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="Raspihats Binary Sensor"> <meta name="twitter:title" content="Raspihats Binary Sensor">
<meta name="twitter:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry PI into Home Assistant as a binary_sensor."> <meta name="twitter:description" content="Instructions how to integrate Raspihats add-on boards for Raspberry Pi into Home Assistant as a binary_sensor.">
<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">
@ -143,7 +143,7 @@
70: -- -- -- -- -- -- -- 77 70: -- -- -- -- -- -- -- 77
</code></pre> </code></pre>
</div> </div>
<p>For more details about the <code class="highlighter-rouge">raspihats</code> add-on boards for Raspberry PI, visit <a href="http://www.raspihats.com/">raspihats.com</a>.</p> <p>For more details about the <code class="highlighter-rouge">raspihats</code> add-on boards for Raspberry Pi, visit <a href="http://www.raspihats.com/">raspihats.com</a>.</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">
@ -308,7 +308,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
Raspihats Binary Sensor Raspihats Binary Sensor

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

@ -358,7 +358,7 @@ User-Agent: Home Assistant
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -346,7 +346,7 @@ to configure your new devices and leave it off otherwise.</p>
RFXtrx Binary Sensor RFXtrx Binary Sensor
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -258,7 +258,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

28
components/binary_sensor.rpi_gpio/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>Raspberry PI GPIO Binary Sensor - Home Assistant</title> <title>Raspberry Pi GPIO Binary Sensor - Home Assistant</title>
<meta name="author" content="Home Assistant"> <meta name="author" content="Home Assistant">
<meta name="description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant."> <meta name="description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into 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/binary_sensor.rpi_gpio/"> <link rel="canonical" href="https://home-assistant.io/components/binary_sensor.rpi_gpio/">
<meta property="fb:app_id" content="338291289691179"> <meta property="fb:app_id" content="338291289691179">
<meta property="og:title" content="Raspberry PI GPIO Binary Sensor"> <meta property="og:title" content="Raspberry Pi GPIO Binary Sensor">
<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/binary_sensor.rpi_gpio/"> <meta property="og:url" content="https://home-assistant.io/components/binary_sensor.rpi_gpio/">
<meta property="og:type" content="article"> <meta property="og:type" content="article">
<meta property="og:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant."> <meta property="og:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into 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="Raspberry PI GPIO Binary Sensor"> <meta name="twitter:title" content="Raspberry Pi GPIO Binary Sensor">
<meta name="twitter:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry PI into Home Assistant."> <meta name="twitter:description" content="Instructions how to integrate the GPIO sensor capability of a Raspberry Pi into 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">
@ -70,7 +70,7 @@
<article class="page"> <article class="page">
<header> <header>
<h1 class="title indent"> <h1 class="title indent">
Raspberry PI GPIO Binary Sensor Raspberry Pi GPIO Binary Sensor
</h1> </h1>
</header> </header>
<hr class="divider"> <hr class="divider">
@ -122,15 +122,15 @@
<div class='section'> <div class='section'>
<h1 class='title delta'>Related components</h1> <h1 class='title delta'>Related components</h1>
<ul class='divided'> <ul class='divided'>
<li><a href='/components/rpi_gpio/'>
Raspberry PI GPIO
</a></li>
<li><a href='/components/switch.rpi_gpio/'>
Raspberry PI GPIO Switch
</a></li>
<li><a href='/components/cover.rpi_gpio/'> <li><a href='/components/cover.rpi_gpio/'>
Raspberry Pi Cover Raspberry Pi Cover
</a></li> </a></li>
<li><a href='/components/rpi_gpio/'>
Raspberry Pi GPIO
</a></li>
<li><a href='/components/switch.rpi_gpio/'>
Raspberry Pi GPIO Switch
</a></li>
</ul> </ul>
</div> </div>
<div class='section'> <div class='section'>
@ -263,7 +263,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
Raspberry PI GPIO Binary Sensor Raspberry Pi GPIO Binary Sensor
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -266,7 +266,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -241,7 +241,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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

@ -266,7 +266,7 @@
<a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a> <a href='/components/binary_sensor.rfxtrx/'>RFXtrx Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.rpi_gpio/'>Raspberry PI GPIO Binary Sensor</a> <a href='/components/binary_sensor.rpi_gpio/'>Raspberry Pi GPIO Binary Sensor</a>
</li> </li>
<li> <li>
<a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a> <a href='/components/binary_sensor.raspihats/'>Raspihats Binary Sensor</a>

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