jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions
home-assistant.github.io/blog/posts/2/index.html
Travis CI 933563f0be Site updated at 2017-06-17 20:00:42 UTC
2017-06-17 20:00:42 +00:00

608 lines
46 KiB
HTML
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!doctype html>
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
<!--[if IE 7]> <html class="no-js lt-ie9 lt-ie8"> <![endif]-->
<!--[if IE 8]> <html class="no-js lt-ie9"> <![endif]-->
<!--[if gt IE 8]><!--> <html> <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Home Assistant</title>
<meta name="author" content="Home Assistant">
<meta name="description" content="Home Assistant is an open-source home automation platform running on Python 3.">
<meta name="viewport" content="width=device-width">
<link rel="canonical" href="https://home-assistant.io/blog/posts/2/">
<meta property="fb:app_id" content="338291289691179">
<meta property="og:title" content="Home Assistant">
<meta property="og:site_name" content="Home Assistant">
<meta property="og:url" content="https://home-assistant.io/blog/posts/2/">
<meta property="og:type" content="website">
<meta property="og:description" content="">
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@home_assistant">
<meta name="twitter:title" content="Home Assistant">
<meta name="twitter:description" content="">
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
<link rel='shortcut icon' href='/images/favicon.ico' />
<link rel='icon' type='image/png' href='/images/favicon-192x192.png' sizes='192x192' />
</head>
<body >
<header>
<div class="grid-wrapper">
<div class="grid">
<div class="grid__item three-tenths lap-two-sixths palm-one-whole ha-title">
<a href="/" class="site-title">
<img width='40' src='/demo/favicon-192x192.png'>
<span>Home Assistant</span>
</a>
</div>
<div class="grid__item seven-tenths lap-four-sixths palm-one-whole">
<nav>
<input type="checkbox" id="toggle">
<label for="toggle" class="toggle" data-open="Main Menu" data-close="Close Menu"></label>
<ul class="menu pull-right">
<li><a href="/getting-started/">Getting started</a></li>
<li><a href="/components/">Components</a></li>
<li><a href="/docs/">Docs</a></li>
<li><a href="/cookbook/">Examples</a></li>
<li><a href="/developers/">Developers</a></li>
<li><a href="/blog/">Blog</a></li>
<li><a href="/help/">Need help?</a></li>
</ul>
</nav>
</div>
</div>
</div>
</header>
<div class="grid-wrapper">
<div class="grid grid-center">
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/05/05/podcast-init-interview/">Podcast.__init__ interview with Paulus Schoutsen</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-05-05T02:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> May 5, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Media</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/05/05/podcast-init-interview/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p class="img">
<a href="https://www.podcastinit.com/"><img src="/images/blog/2017-05-podcast-init/podcast_init.png" /></a>
</p>
<p>Earlier this year I was interviewed by Tobias Macey from <a href="https://www.podcastinit.com/">Podcast.__init__</a> about Python and Home Assistant. Just realized that we never shared this on the blog, oops. Here it is, enjoy!</p>
<script class="podigee-podcast-player" src="//cdn.podigee.com/podcast-player/javascripts/podigee-podcast-player.js" data-configuration="https://www.podcastinit.com?podigee_player=205" async=""></script>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/">Home Assistant on a Pi Zero W in 30 minutes</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-05-01T09:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> May 1, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Avraham David Gelbfish</span>
<span><i class='icon-time'></i> 1 minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/05/01/home-assistant-on-raspberry-pi-zero-in-30-minutes/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p class="img">
<img src="/images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.png" />
</p>
<p>Saw the <a href="/blog/2017/04/30/hassbian-1.21-its-about-time/">announcement</a> yesterday for HASSbian 1.21 and got super excited?</p>
<p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspbery Pi Zero W</a>.
<strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p>
<p>What you’ll need:</p>
<ul>
<li>a Raspberry Pi Zero W (an amazing tiny computer with built-in wifi)</li>
<li>a microSD card</li>
<li>some source of USB power</li>
<li>Wifi</li>
<li>a desktop or laptop</li>
</ul>
<p>Let’s get to it!</p>
<p>First, download the HASSbian 1.21 image from <a href="https://github.com/home-assistant/pi-gen/releases/tag/v1.21">here</a>.</p>
<p>Unzip it.</p>
<p>Flash it to the microSD card. If you need a flash tool, try <a href="https://etcher.io/">Etcher</a></p>
<p>When the flashing finishes, remove it and plug it back in. You should see a drive called “boot”.</p>
<p>Right in there, not in any folders, create a file called <code class="highlighter-rouge">wpa_supplicant.conf</code>.</p>
<p>The contents of the configuration file should be something like this:
(You may have to adjust for your configuration, hints <a href="https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md">here</a> )</p>
<div class="highlighter-rouge"><pre class="highlight"><code>network={
ssid="YOUR_WIFI_NETWORK_NAME_HERE"
psk="YOUR_WIFI_PASSWORD_HERE"
key_mgmt=WPA-PSK
}
</code></pre>
</div>
<p>Next stick your SD card into the Raspberry Pi Zero W, and plug it in.</p>
<p>After about a minute, use your SSH client to connect to HASSbian (or <code class="highlighter-rouge">hassbian.local</code> from a Mac), with the username <code class="highlighter-rouge">pi</code>. The default password is <code class="highlighter-rouge">raspberry</code>.</p>
<p>It’s a good idea to change the password. To do so, use the <code class="highlighter-rouge">passwd</code> command.</p>
<p>Next, type the following two commands into the SSH console:</p>
<div class="highlighter-rouge"><pre class="highlight"><code>$ sudo systemctl enable install_homeassistant.service
$ sudo systemctl start install_homeassistant.service
</code></pre>
</div>
<p>Wait about 15-20 minutes and voilà you have your Home Assistant on your Raspberry Pi Zero W in 30 minutes.</p>
<p>To try it out, go to <a href="http://hassbian:8123">http://hassbian:8123</a> or <a href="http://hassbian.local:8123">http://hassbian.local:8123</a> if you’re using Mac.</p>
<p>For further details about HASSbian, take a look at the <a href="https://home-assistant.io/docs/hassbian/">documentation</a>.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/30/hassbian-1.21-its-about-time/">HASSbian 1.21 - It's about time isn't it</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-30T15:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 30, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Fredrik Lindqvist</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Technology</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/30/hassbian-1.21-its-about-time/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<h3>Hassbian 1.21 - It’s about time isn’t it</h3>
<p>Since I, the developer of HASSbian, have been moving, started a new job and so on I’ve had few moments over for HASSbian development. The 1.2 release has been in pre-release for a few months now and just not communicated out that well. Hopefully this release changes that and I’ll do my best to release more often. There’s no simple way to update from 1.1 to 1.21 but 95% of the changes can be done by installing the <a href="https://github.com/home-assistant/hassbian-scripts/releases/latest">hassbian-config</a> package. For more information have a look at the <a href="https://github.com/home-assistant/hassbian-scripts/">hassbian-config</a> page.</p>
<h3>Hassbian 1.22 - Sins of last night</h3>
<p>Development is sometimes fast and joyful but mistakes are made at times.</p>
<p>With the release of 1.21 a small problem with the OpenZWave build script wasn’t corrected even tough it was a known bug. Problem is simple as it’s only a problem with the symlink created for to the configuration folder for OpenZWave. This has been fixed and we bring some new things since they where ready anyway. The list below has been augmented with the updated information.</p>
<h3><a class="title-link" name="hassbian-config" href="#hassbian-config"></a> Hassbian-config</h3>
<p>To allow you to customize your installation further, we have included a tool called <code class="highlighter-rouge">hassbian-config</code>. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the <code class="highlighter-rouge">hassbian-scripts</code> functionality from 1.1.</p>
<ul>
<li>Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.</li>
<li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li>
<li>Install Libcec. Adds local <a href="/components/hdmi_cec/">HDMI CEC support</a>.</li>
<li>Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.</li>
<li>Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git.</li>
<li>Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it’s usage is not recommended if you share your network with others.</li>
<li>Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick.</li>
<li>Install Tradfri. Installs dependencies for using IKEA Trådfri.</li>
</ul>
<h3><a class="title-link" name="spring-cleaning" href="#spring-cleaning"></a> Spring cleaning</h3>
<p>With this image there also quite a bit of cleaning of the base system and the script that generates our Raspberry Pi image.</p>
<ul>
<li>Replaced the <code class="highlighter-rouge">hassbian-scripts</code> folder with <code class="highlighter-rouge">hassbian-config</code>.</li>
<li>Update <code class="highlighter-rouge">pi-gen</code>. Our build script has been upgraded to follow the Raspbian image closer once again. Now you could build this image with Docker if your so inclined.</li>
<li>Added libtool and autoconf package. Dependencies for some of the pip packages.</li>
<li>Pi ZeroW should now work with the image.</li>
</ul>
<p>To follow discussions about the development of the HASSbian image or to contribute join the <a href="https://gitter.im/home-assistant/hassbian">HASSbian gitter chat</a>.</p>
<p>To get started with the new image, check out the installation instructions in the <a href="/getting-started/installation-raspberry-pi-image/">getting started section</a>.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/25/influxdb-grafana-docker/">Setting up InfluxDB and Grafana using Docker</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-25T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 25, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Alok Saboo</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/25/influxdb-grafana-docker/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Home Assistant collects volumes of (time series) data that are well suited for some fancy graphs. Although the <a href="https://home-assistant.io/components/history/">History</a> component provides some nice plots, I am sure you have always wanted those fancy <a href="https://grafana.com/">Grafana</a> plots. The problem, however, is that low-powered device such as Raspberry Pi that most of us use for our Home Assistant setup are not well suited for such operation.</p>
<p>Instead of running <a href="https://www.influxdata.com/">InfluxDB</a> and Grafana on a Raspberry Pi or a different system and go through the <a href="/blog/2015/12/07/influxdb-and-grafana/">classic approach of installing both tools separately</a>, you can run them in a Docker container on another machine. For this tutorial, I am using a Synology NAS, but the instructions should apply to other devices that can run Docker. Just follow the steps below:</p>
<ol>
<li>SSH into your NAS. You may have to run <code class="highlighter-rouge">sudo su</code> if you are getting permission errors.</li>
<li>Download the <a href="https://hub.docker.com/r/samuelebistoletti/docker-statsd-influxdb-grafana/">docker-statsd-influxdb-grafana</a> image using the command:
<code class="highlighter-rouge">docker pull samuelebistoletti/docker-statsd-influxdb-grafana</code></li>
<li>To start the container for the first-time launch:
<div class="highlighter-rouge"><pre class="highlight"><code>docker run -d \
--name docker-statsd-influxdb-grafana \
-p 3003:3003 \
-p 3004:8083 \
-p 8086:8086 \
-p 22022:22 \
-p 8125:8125/udp \
samuelebistoletti/docker-statsd-influxdb-grafana:latest
</code></pre>
</div>
</li>
<li>The image should now be running and both InfluxBD and Grafana should be now up and running.</li>
<li>You can access InfluxDB at http://NAS_IP_ADDRESS:3004/ and Grafana at http://NAS_IP_ADDRESS:3003/</li>
<li>Navigate to http://NAS_IP_ADDRESS:3004/ and create the database <code class="highlighter-rouge">home_assistant</code> using the command <code class="highlighter-rouge">CREATE DATABASE home_assistant</code>.
<p class="img">
<img src="/images/blog/2017-04-influxdb-grafana/create_HA_database.png" />
</p>
</li>
<li>Now, you need to configure Home Assistant to use InfluxDB. Since, we did not add any username/password to our database, we can simply add the following to our configuration.yaml (replace the IP address with that of the device running Docker) and restart Home Assistant to setup InfluxDB (you will have to fine tune it based on your preferences):
<div class="highlighter-rouge"><pre class="highlight"><code>influxdb:
host: 192.168.2.113
</code></pre>
</div>
</li>
<li>Next, we need to configure Grafana to use InfluxDB. Navigate to http://NAS_IP_ADDRESS:3003/ to access Grafana (login with username and password <code class="highlighter-rouge">root</code>) and add your first data source. Here’s how you can configure Grafana to use InfluxDB database. Note that 192.168.2.113 is the IP address of my NAS.
<p class="img">
<img src="/images/blog/2017-04-influxdb-grafana/add_data_source.png" />
</p>
</li>
<li>You should see <code class="highlighter-rouge">Data source is working</code> if you have configured everything correctly.</li>
<li>With all that configured, you are now ready for the fun stuff. You can create as many dashboards as you want and then import the same in Home Assistant.</li>
<li>To add the Grafana dashboard in HA, use the following config:
<div class="highlighter-rouge"><pre class="highlight"><code>panel_iframe:
router:
title: 'Temperature'
url: 'http://192.168.2.113:3003/dashboard/db/temperature?edit&amp;tab=time%20range'
</code></pre>
</div>
<p>The URL can be obtained by clicking Share Dashboard link on your dashboard:</p>
<p class="img">
<img src="/images/blog/2017-04-influxdb-grafana/share_dashboard.png" />
</p>
</li>
</ol>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/24/hardware-contest-2017/">Hardware Contest 2017</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-24T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 24, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> Less than one minute reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Community</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/24/hardware-contest-2017/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>We have four submissions for our <a href="https://home-assistant.io/blog/2017/04/01/thomas-krenn-award/">Hardware Contest 2017</a>.</p>
<ul>
<li><a href="https://community.home-assistant.io/t/entry-for-hardware-contest-part-of-iot-course/14827">Part of IoT-course</a></li>
<li><a href="https://community.home-assistant.io/t/entry-automating-a-nursing-home/14872">Automating a nursing home!</a></li>
<li><a href="https://community.home-assistant.io/t/entry-dedicated-hardware-for-coding-testing-building-and-contributing-to-home-assistant/15515">Dedicated hardware for coding, testing, building, and contributing to Home Assistant</a></li>
<li><a href="https://community.home-assistant.io/t/entry-hassio-home-assistant-hub-for-dummies/16037">HassIO - Home Assistant hub for dummies</a></li>
</ul>
<p>The voting is now open. To keep things simple are we using the voting feature of the <a href="https://community.home-assistant.io/c/contest-2017">forum</a>. Vote for your choices.</p>
<p>End of the voting period: April, 30 2017 - 23.59 UTC</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/22/ikea-tradfri-spotify/">Home Assistant 0.43: IKEA Trådfri, Spotify and our iOS app is live</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-22T01:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 22, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 14 minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/22/ikea-tradfri-spotify/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#added_in_current_version"><img src="/images/blog/2017-04-0.43/components.png" style="border: 0;box-shadow: none;" /></a></p>
<p>Oooh yeah. It’s time for 0.43 and this is going to be a killer release. For the people that have been following on social media, you might have noticed that <a href="/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/">we got pretty excited about the new IKEA Trådfri line up</a>. And so we are very happy to announce that thanks to the work by <a href="https://github.com/ggravlingen">@ggravlingen</a>, <a href="https://github.com/MartinHjelmare">@MartinHjelmare</a> and myself that this will be the first release to support the IKEA light bulbs. Home Assistant will automatically detect the gateway on your network and after following the instructions, allow you to control your lights.</p>
<p class="img">
<img src="/images/blog/2017-04-tradfri/discovery.png" />
After automatic discovery, Home Assistant will ask the user to finish pairing with the gateway.
</p>
<p>And in case you have missed the other big news: <a href="https://github.com/robbiet480">@robbiet480</a> released the <a href="/blog/2017/04/15/ios/">first version of our iOS app</a>! It took a little over a year but it offers some great ways to make your iDevice work with Home Assistant. Big congrats to Robbie for shipping! As with our other parts, the app is open-sourced under APACHE 2 and contributors are welcome. <a href="https://github.com/home-assistant/home-assistant-ios">Check it out.</a></p>
<p>A big shout out this release to <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> for his constant stream of great contributions to Home Assistant. The first contribution was back in October 2015 and since then <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> has been responsible for many platforms and bug fixes including the Spotify platform this release. Thanks <a href="https://github.com/happyleavesaoc">@happyleavesaoc</a>, you’re a great example of what makes our community awesome.</p>
<p>The new Spotify integration is based on the new Spotify Connect Playback API. It supports playback, album art and switching which Spotify device you’re controlling.</p>
<p>Also note that you have till the end of the weekend to <a href="https://community.home-assistant.io/c/contest-2017">submit an application</a> to our giveaway of low energy servers which we got when <a href="/blog/2017/04/01/thomas-krenn-award/">we won the Thomas Krenn award 2017</a>. <a href="https://community.home-assistant.io/c/contest-2017">Go apply!</a></p>
<h2><a class="title-link" name="new-platforms" href="#new-platforms"></a> New Platforms</h2>
<ul>
<li>MaryTTS platform (<a href="https://github.com/johanpalmqvist">@johanpalmqvist</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6988">#6988</a>) (<a href="/components/tts.marytts/">tts.marytts docs</a>) (new-platform)</li>
<li>Telegram bot component (incl. webhook and polling platform) (<a href="https://github.com/sander76">@sander76</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6913">#6913</a>) (<a href="https://home-assistant.io/components/telegram_bot/">telegram_bot docs</a>) (<a href="https://home-assistant.io/components/telegram_bot.polling/">telegram_bot.polling docs</a>) (<a href="https://home-assistant.io/components/telegram_bot.webhooks/">telegram_bot.webhooks docs</a>) (breaking change) (new-platform)</li>
<li>Support fo map data from Neato (<a href="https://github.com/turbokongen">@turbokongen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6939">#6939</a>) (<a href="/components/neato/">neato docs</a>) (<a href="/components/camera.neato/">camera.neato docs</a>) (<a href="/components/sensor.neato/">sensor.neato docs</a>) (new-platform)</li>
<li>Support for IKEA Trådfri (<a href="https://github.com/ggravlingen">@ggravlingen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7074">#7074</a>) (<a href="/components/light.tradfri/">light.tradfri docs</a>) (new-platform)</li>
<li>MQTT camera (<a href="https://github.com/MrMep">@MrMep</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7092">#7092</a>) (<a href="/components/camera.mqtt/">camera.mqtt docs</a>) (new-platform)</li>
<li>LIFX Cloud scene support (<a href="https://github.com/amelchio">@amelchio</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7124">#7124</a>) (<a href="/components/scene.lifx_cloud/">scene.lifx_cloud docs</a>) (new-platform)</li>
<li>Spotify media player (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6980">#6980</a>) (<a href="/components/media_player.spotify/">media_player.spotify docs</a>) (new-platform)</li>
<li>JSON MQTT Device tracker (<a href="https://github.com/MrMep">@MrMep</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7055">#7055</a>) (new-platform)</li>
<li>Opensky sensor (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7061">#7061</a>) (<a href="/components/sensor.opensky/">sensor.opensky docs</a>) (new-platform)</li>
<li>Ping binary sensor (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7052">#7052</a>) (<a href="/components/binary_sensor.ping/">binary_sensor.ping docs</a>) (new-platform)</li>
<li>myStrom Wifi Bulbs (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7161">#7161</a>) (<a href="/components/light.mystrom/">light.mystrom docs</a>) (new-platform)</li>
</ul>
<a class="btn pull-right" href="/blog/2017/04/22/ikea-tradfri-spotify/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/">IKEA Trådfri: Internet of Things done right</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-17T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 17, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> nine minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Internet-of-Things</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Last month IKEA released a new home automation lineup called <a href="http://www.ikea.com/us/en/catalog/categories/departments/lighting/36812/">Trådfri</a>. It consists of white bulbs, dimming remotes, color temperature remotes and motion sensors. After almost two weeks of research, we have come to the conclusion that this is going to be the perfect companion hardware to work with Home Assistant. Here is the gist of our breakdown:</p>
<ul>
<li><strong>Works out of the box.</strong> You can get started by just buying the already paired light and remote. You only need to buy the gateway if you want to set time-based rules for your lights or use your phone as a remote.</li>
<li><strong>Local only hub.</strong> No cloud that gathers data about how you live your life and it will keep working even if IKEA stops supporting it.</li>
<li><strong>Based on open standards.</strong> It uses Zigbee between devices and CoAP/dTLS to talk to the gateway. This means that you are not locked into a single vendor. You can pair it with Philips Hue bulbs and other compatible vendors.</li>
<li><strong>Affordable.</strong> Lights start at $12 standalone and $20 if bundled with a remote (USA prices).</li>
<li><strong>Useful design.</strong> The gateway has built-in space to hide excess cables and remotes come with magnetic holders for on the wall.</li>
<li><strong>Able to subscribe to changes (local push).</strong> Automations will be able to instantly respond to changes to device states by subscribing to the gateway for changes.</li>
<li><strong>Full integration in Home Assistant 0.43 (scheduled for release April 22).</strong> Our community built a standalone library <a href="https://github.com/ggravlingen/pytradfri">pytradfri</a> and we use it in Home Assistant. Home Assistant will automatically discover gateways on your network and guide the user to set them up.</li>
<li><strong>Downside: no integration with other systems yet.</strong> There are rumors that Homekit support will land in October and I expect both Google Home and Amazon Echo to eventually add support. Use Home Assistant to connect them all in the meanwhile.</li>
<li><strong>Semi-downside: you can’t control your lights remotely.</strong> Because it’s local only, you won’t be able to control your lights remotely unless via a third-party integration.</li>
</ul>
<p>Full breakdown available after clicking read more.</p>
<p><em>(Note: we are not affiliated with IKEA nor do we receive commission for sales. We are just big fans of their new line up!)</em></p>
<a class="btn pull-right" href="/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/15/ios/">1 year and 22 days ago I had an idea...</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-15T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 16, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Robbie Trencheny</span>
<span><i class='icon-time'></i> three minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Announcements</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/15/ios/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>1 year and 22 days ago, or 387 days ago, on March 25th, 2016, I started a project to bring Home Assistant to the iPhone.</p>
<p>I thought the existing notification and location solutions were lacking in one way or another and had wanted for <em>years</em> to have a project I could call my own which would allow me to learn iOS development. What better way then implementing an extremely complex application like Home Assistant?</p>
<p>I started with a lot of steam. I remember cranking out the initial work that night and showing Paulus who was astounded at how fast the UI was coming together.</p>
<p>Little would I know how many problems I would create and uncover throughout the process. Writing a mobile app for a project that moves as fast as Home Assistant is… tricky, to say the least. In the time since I started writing the app, Home Assistant had 90 releases. I started writing the day before 0.16 was released. Now we are at 0.42.3. Time flies…</p>
<p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p>
<p>I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.</p>
<p>I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.</p>
<p>It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p>
<p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p>
<p>The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.</p>
<p>The app is <a href="https://github.com/home-assistant/home-assistant-iOS">open source</a>, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.</p>
<p><strong>1 year and 22 days ago, on March 25th, 2016 I began work on Home Assistant for iOS.</strong></p>
<p><strong>Today, April 16th, 2017, I am <em>extremely</em> excited to announce that Home Assistant for iOS has been approved by Apple and is now available to download for <del>a monthly subscription starting at $9.99</del> free! (had to get a joke in here somewhere!) on the iOS App Store in every country.</strong></p>
<p style="text-align: center;"><a target="_blank" href="https://itunes.apple.com/us/app/home-assistant-open-source-home-automation/id1099568401?mt=8" style="display:inline-block;overflow:hidden;background:url(//linkmaker.itunes.apple.com/assets/shared/badges/en-us/appstore-lrg.svg) no-repeat;width:135px;height:40px;background-size:contain;"></a></p>
<p><em>Please note, you must have Home Assistant 0.42.4 or later installed for the app to function properly.</em></p>
<p>Thanks for everything so far, I’m looking forward to the road that lies ahead for Home Assistant on iOS!</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/">Home Assistant 0.42: Eddystone Beacons, Lockitron locks and Total Connect alarm systems</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-08T08:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 8, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
<span><i class='icon-time'></i> 11 minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Release-Notes</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><a href="/components/#added_in_current_version"><img src="/images/blog/2017-04-0.42/social.png" style="border: 0;box-shadow: none;" /></a></p>
<p>It’s time for Home Assistant 0.42. This release has been focused on refining the system and fixing a lot of bugs. We have also upgraded to the latest version of our HTTP library which should give us a significant boost serving files and API.</p>
<p>On our social media front, we have crossed the 1000 likes on <a href="https://www.facebook.com/homeassistantio">our Facebook page</a>! Also on the social media front, the YouTube channel diyAutomate has been putting out a lot of great getting started videos about Home Assistant, <a href="https://www.youtube.com/c/diyautomate">go check them out!</a></p>
<p>Also want to take a moment to thank Austin Andrews aka <a href="https://github.com/templarian">Templarian</a> for his <a href="https://materialdesignicons.com/">Material Design Icons</a>. He is part of what makes Home Assistant so beautiful 🤗.</p>
<h2>New integrations</h2>
<ul>
<li>Lockitron locks (<a href="https://github.com/aarya123">@aarya123</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6805">#6805</a>)</li>
<li>Met Office weather and sensor components (<a href="https://github.com/jacobtomlinson">@jacobtomlinson</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6742">#6742</a>)</li>
<li>Total Connect alarm systems (<a href="https://github.com/wardcraigj">@wardcraigj</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6887">#6887</a>)</li>
<li>Eddystone Beacon Temperature Sensor (<a href="https://github.com/citruz">@citruz</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6789">#6789</a>)</li>
<li>CrimeReports.com integration shows crimes around a location in the US (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6966">#6966</a>)</li>
<li>The Ring doorbell has been integrated further with the inclusion of binary sensors (<a href="https://github.com/tchellomello">@tchellomello</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6520">#6520</a>)</li>
</ul>
<a class="btn pull-right" href="/blog/2017/04/08/eddystone-beacons-lockitron-locks-total-connect/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/04/01/thomas-krenn-award/">Thomas Krenn award 2017</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-04-01T06:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> April 01, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> two minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>Community</li>
</ul>
</span>
<a class='comments'
href="/blog/2017/04/01/thomas-krenn-award/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the <a href="https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/">Thomas-Krenn-Award</a> put us on the 2nd place. This is an awesome achievment for an independent community project.</p>
<p>I would like to thanks all contributors. Your endless effort made this possible.</p>
<p><img src="/images/blog/2017-04-award/award.jpg" style="border: 0;box-shadow: none;" /></p>
<p>The prize beside the very nice trophy contains hardware and we want to give that hardware partically away. We won four <a href="https://www.thomas-krenn.com/en/products/low-energy-systems/les-v2.html">Low Energy Server v2 (LES)</a> units with an Intel Celeron N2930, 8 GB of RAM, and a mSATA of 128 GB (one unit with 64 GB). We were thinking about to keep one of those units in Europe and one in North America for testing and to use during workshops and events. But the other two will go to interested parties.</p>
<p>As a raffle would be to easy, we make a contest out of it. This means that we are looking for your application. Of course, we would like to see those systems goes to active or future developers who can justify their need for one of the systems to run CI, UI tests, public accessible Home Assistant demo instances, etc. At the other hand we would like to keep it open, to see with what people are coming up. Please participate as well if you are planning to automate the public school of your kids with 1000 switches or light, need a server to run it, and want to provide regular feedback about the user experience.</p>
<p>Create an entry in our <a href="https://community.home-assistant.io/c/contest-2017">Forum</a>. Be creative and use your imagination.</p>
<h3><a class="title-link" name="the-details" href="#the-details"></a> The details</h3>
<ul>
<li>Jury: The Home Assistant community</li>
<li>Dead line: April, 23 2017 - 23.59 UTC</li>
<li>Voting period: April, 24th till April, 30 2017 - 23.59 UTC</li>
</ul>
<p>The decision of the jury will be final. If there will be a dispute then the Top-5 commiter of the Home Assistant organisation on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p>
<p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p>
</div>
</article>
<hr>
<div class="pagination">
<a class="btn pull-left" href="/blog/posts/3">&larr; Older</a>
<a class="btn pull-right" href="/blog/">Newer &rarr;</a>
</div>
</div>
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">
<div class="grid">
<section class="aside-module grid__item one-whole lap-one-half">
<h1 class="title delta">About Home Assistant</h1>
<ul class="divided">
<li>
Home Assistant is an open-source home automation platform running on Python 3. Track and control all devices at home and automate control.
</li>
<li><a href='/getting-started/'>Get started with Home Assistant</a></li>
<li><a href='/demo/'>Try the online demo</a></li>
<li><a class="twitter-follow-button" href="https://twitter.com/Home_Assistant">Follow Home Assistant on Twitter</a></li>
<li><div class="fb-like" data-href="https://www.facebook.com/homeassistantio/" data-layout="standard" data-action="like" data-size="small" data-show-faces="true" data-share="false"></div></li>
</ul>
</section>
<div id="fb-root"></div>
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.async=true;js.src='//platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document, 'script', 'twitter-wjs');</script>
<script>(function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(d.getElementById(id)){return;}js=d.createElement(s);js.id=id;js.async=true;js.src="//connect.facebook.net/en_US/all.js#appId=338291289691179&xfbml=1";fjs.parentNode.insertBefore(js,fjs);}(document,'script','facebook-jssdk'));</script>
<section class="aside-module grid__item one-whole lap-one-half">
<h1 class="title delta">Categories</h1>
<ul class="divided">
<li><a href="/blog/categories/announcements/">Announcements</a></li>
<li><a href="/blog/categories/community/">Community</a></li>
<li><a href="/blog/categories/device-tracking/">Device Tracking</a></li>
<li><a href="/blog/categories/esp8266/">ESP8266</a></li>
<li><a href="/blog/categories/how-to/">How To</a></li>
<li><a href="/blog/categories/internet-of-things/">Internet of Things</a></li>
<li><a href="/blog/categories/iot-data/">IoT Data</a></li>
<li><a href="/blog/categories/mqtt/">MQTT</a></li>
<li><a href="/blog/categories/media/">Media</a></li>
<li><a href="/blog/categories/merchandise/">Merchandise</a></li>
<li><a href="/blog/categories/micropython/">Micropython</a></li>
<li><a href="/blog/categories/organisation/">Organisation</a></li>
<li><a href="/blog/categories/owntracks/">OwnTracks</a></li>
<li><a href="/blog/categories/presence-detection/">Presence Detection</a></li>
<li><a href="/blog/categories/public-service-announcement/">Public Service Announcement</a></li>
<li><a href="/blog/categories/release-notes/">Release Notes</a></li>
<li><a href="/blog/categories/survey/">Survey</a></li>
<li><a href="/blog/categories/talks/">Talks</a></li>
<li><a href="/blog/categories/technology/">Technology</a></li>
<li><a href="/blog/categories/user-stories/">User Stories</a></li>
<li><a href="/blog/categories/video/">Video</a></li>
<li><a href="/blog/categories/website/">Website</a></li>
<li><a href="/blog/categories/ibeacons/">iBeacons</a></li>
</ul>
</section>
</div>
</aside>
</div>
</div>
<footer>
<div class="grid-wrapper">
<div class="grid">
<div class="grid__item">
<div class="copyright">
<a rel="me" href='https://twitter.com/home_assistant'><i class="icon-twitter"></i></a>
<a rel="me" href='https://facebook.com/homeassistantio'><i class="icon-facebook"></i></a>
<a rel="me" href='https://plus.google.com/110560654828510104551'><i class="icon-google-plus"></i></a>
<a rel="me" href='https://github.com/home-assistant/home-assistant'><i class="icon-github"></i></a>
<div class="credit">
Contact us at <a href='mailto:hello@home-assistant.io'>hello@home-assistant.io</a> (no support!).<br>
Website powered by <a href='http://jekyllrb.com/'>Jekyll</a> and the <a href='https://github.com/coogie/oscailte'>Oscalite theme</a>.<br />
Hosted by <a href='https://pages.github.com/'>GitHub</a> and served by <a href='https://cloudflare.com'>CloudFlare</a>.
</div>
<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png" /></a><br /><span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">home-assistant.io</span> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.
</div>
</div>
</div>
</div>
</footer>
<script>
var _gaq=[['_setAccount','UA-57927901-1'],['_trackPageview']];
(function(d,t){var g=d.createElement(t),s=d.getElementsByTagName(t)[0];
g.src=('https:'==location.protocol?'//ssl':'//www')+'.google-analytics.com/ga.js';
s.parentNode.insertBefore(g,s)}(document,'script'));
</script>
<script>
var disqus_shortname = 'home-assistant';
var disqus_script = 'count.js';
(function () {
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
dsq.src = '//' + disqus_shortname + '.disqus.com/' + disqus_script;
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
}());
</script>
</body>
</html>
Reference in a new issue View git blame Copy permalink