798 lines
No EOL
31 KiB
HTML
798 lines
No EOL
31 KiB
HTML
<!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="Paulus Schoutsen">
|
||
<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/5/">
|
||
|
||
<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/5/">
|
||
<meta property="og:type" content="website">
|
||
<meta property="og:description" content="">
|
||
<meta property="og:image" content="https://home-assistant.io/images/home-assistant-logo-2164x2164.png">
|
||
|
||
<meta name="twitter:card" content="summary">
|
||
<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/home-assistant-logo-2164x2164.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>Getting started <i class="icon icon-caret-down"></i></a>
|
||
<ul>
|
||
<li><a href='/getting-started/'>Installing Home Assistant</a></li>
|
||
<li><a href='/getting-started/configuration/'>Configuration Basics</a></li>
|
||
<li><a href='/getting-started/devices/'>Adding devices</a></li>
|
||
<li><a href='/getting-started/presence-detection/'>Presence Detection</a></li>
|
||
<li><a href='/getting-started/automation/'>Automation</a></li>
|
||
<li><a href='/topics/'>Advanced Topics</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href='/components/'>Components</a></li>
|
||
<li><a href='/cookbook'>Examples</a></li>
|
||
<li>
|
||
<a>Developers <i class="icon icon-caret-down"></i></a>
|
||
<ul>
|
||
<li><a href="/developers/">Setup Development</a></li>
|
||
<li><a href="/developers/architecture/">Architecture</a></li>
|
||
<li><a href="/developers/frontend/">Frontend Development</a></li>
|
||
<li><a href="/developers/creating_components/">
|
||
Creating Components
|
||
</a></li>
|
||
<li><a href="/developers/add_new_platform/">
|
||
Adding Platform Support
|
||
</a></li>
|
||
<li><a href="/developers/api/">API and SSE</a></li>
|
||
<li><a href="/developers/credits/">Credits</a></li>
|
||
</ul>
|
||
</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/2015/03/11/release-notes/">Release notes for March 11, 2015</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-03-11T18:36:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 11, 2015</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
|
||
<span><i class='icon-time'></i> two minutes reading time</span>
|
||
<span>
|
||
<i class="icon-tags"></i>
|
||
<ul class="tags unstyled">
|
||
|
||
|
||
<li><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/03/11/release-notes/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>It has only been a little over a week since Theodor introduced YAML support for Home Assistant but so much has already happened that it is time for a summary of recent changes. Before mentioning the highlights I want to thank <a href="https://github.com/andythigpen">andythigpen</a>, <a href="https://github.com/jamespcole">jamespcole</a> and <a href="https://github.com/theolind">theolind</a> for numerous bug fixes, enhancements and new contributions. Thanks!</p>
|
||
|
||
<p><strong>Monitor local resources.</strong><br /><br />
|
||
Theodor has contributed a new sensor platform to allow you to monitor disk usage, memory usage, CPU usage and running processes. This platform has superseded the process component which is now considered deprecated.</p>
|
||
|
||
<div class="highlighter-coderay"><div class="CodeRay">
|
||
<div class="code"><pre><span class="comment"># Example configuration.yaml entry</span>
|
||
<span class="key">sensor</span>:
|
||
- <span class="string"><span class="content">platform: systemmonitor</span></span>
|
||
<span class="key">resources</span>:
|
||
- <span class="string"><span class="content">type: disk_use_percent</span></span>
|
||
<span class="key">arg</span>: <span class="string"><span class="content">/home</span></span>
|
||
- <span class="string"><span class="content">type: memory_free</span></span>
|
||
- <span class="string"><span class="content">type: process</span></span>
|
||
<span class="key">arg</span>: <span class="string"><span class="content">kodi</span></span>
|
||
</pre></div>
|
||
</div>
|
||
</div>
|
||
|
||
<p><strong>Experimental Z-Wave support</strong><br /><br />
|
||
There is now experimental support for connecting Z-Wave networks using a Z-Wave USB stick. Right now it only integrates Z-Wave sensors into Home Assistant. Our goal is to get this tested by more people before adding support for other Z-Wave devices.</p>
|
||
|
||
<p>The new component is built on top of <a href="https://code.google.com/p/python-openzwave/">python-openzwave</a>. This package is currently not distributed on PyPi so we’ve added a script <code>scripts/build_python_openzwave</code> to install it on your machine. Alternatively you can use the Docker image which is ready to go.</p>
|
||
|
||
<p>The development was done using an AEON Z-Wave USB stick and an AEON Z-Wave MultiSensor.</p>
|
||
|
||
<div class="highlighter-coderay"><div class="CodeRay">
|
||
<div class="code"><pre><span class="comment"># Example configuration.yaml entry</span>
|
||
<span class="key">zwave</span>:
|
||
<span class="key">usb_path</span>: <span class="string"><span class="content">/dev/ttyUSB0</span></span>
|
||
</pre></div>
|
||
</div>
|
||
</div>
|
||
|
||
<p><strong>Voice control</strong><br /><br />
|
||
An initial version of voice control for Home Assistant has landed. The current implementation consists of two parts.</p>
|
||
|
||
<p>The first part is a component called <code>conversation</code> that exposes the service <code>conversation/process</code>. This service is capable of processing text and translating them into commands for devices. For now it will only support commands in the format of <code>Turn <Friendly Name> <on/off></code>.</p>
|
||
|
||
<p>The second part is an upgrade to the frontend to use the speech-to-text in Chrome to allow users to speak commands. If you’re using Chrome, you can test this out in <a href="/demo/">the demo</a>.</p>
|
||
|
||
<div class="highlighter-coderay"><div class="CodeRay">
|
||
<div class="code"><pre><span class="comment"># Example configuration.yaml entry</span>
|
||
<span class="key">conversation</span>:
|
||
</pre></div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/03/08/new-logo/">New logo for Home Assistant</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-03-08T22:16:10+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 8, 2015</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><a class='category' href='/blog/categories/branding/'>Branding</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/03/08/new-logo/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>It is well known that you are either a good programmer or a good designer. It’s rare you’ll meet someone that is both. That’s why it wasn’t surprising to anyone that the logo that I made was mediocre — at best. Luckily, <a href="http://jeremygeltman.com/">Jeremy Geltman</a> has come to the rescue and contributed a brand new logo for Home Assistant.</p>
|
||
|
||
<p>The new logo follows Googles material design spec. It uses the blue color that Home Assistant uses in the interface and it comes in two versions: a high detailed version (for homescreen icon etc) and a simple version (for favicon etc).</p>
|
||
|
||
<p class="img">
|
||
<img src="/images/blog/ha-logo-history.png" />
|
||
The old logo, the new detailed logo and the new simple logo.
|
||
</p>
|
||
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/03/01/home-assistant-migrating-to-yaml/">Home Assistant moving to YAML</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-03-01T19:38:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> March 1, 2015</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Theodor Lindquist</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><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/03/01/home-assistant-migrating-to-yaml/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>Home Assistant is now using <a href="http://yaml.org/">YAML</a> for it’s configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.</p>
|
||
|
||
<p>The new file is named configuration.yaml and if it can’t be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.</p>
|
||
|
||
<p>The home-assistant.conf.example has been replaced with an updated <a href="https://github.com/balloob/home-assistant/blob/dev/config/configuration.yaml.example">configuration.yaml.example</a>.</p>
|
||
|
||
<p>Users of Home Assistant should migrate as the old configuration format is deprecated.</p>
|
||
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/02/24/streaming-updates/">Streaming updates</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-02-24T22:41:27+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> February 24, 2015</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
|
||
<span><i class='icon-time'></i> 1 minute reading time</span>
|
||
<span>
|
||
<i class="icon-tags"></i>
|
||
<ul class="tags unstyled">
|
||
|
||
|
||
<li><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/02/24/streaming-updates/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.</p>
|
||
|
||
<p>A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.</p>
|
||
|
||
<p class="img"><img src="/images/screenshots/streaming-updates.png" /></p>
|
||
|
||
|
||
|
||
<a class="btn pull-right" href="/blog/2015/02/24/streaming-updates/#read-more">Read on →</a>
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/02/08/looking-at-the-past/">Looking at the past</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-02-08T17:01:23+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> February 8, 2015</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
|
||
<span><i class='icon-time'></i> 1 minute reading time</span>
|
||
<span>
|
||
<i class="icon-tags"></i>
|
||
<ul class="tags unstyled">
|
||
|
||
|
||
<li><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/02/08/looking-at-the-past/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>Ever since the launch of Home Assistant you have been able to track the state of your house. But the view has always been limited to what the current state is. Not what it was. Today we are going to change that by introducing two brand new components:</p>
|
||
|
||
<ul>
|
||
<li>Recorder component that will record every event to a SQLite database</li>
|
||
<li>History component that will query and aggregate the recorded events</li>
|
||
</ul>
|
||
|
||
<p>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p>
|
||
|
||
<p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p>
|
||
|
||
<p>The history component will be enabled for new users by default. For current users, run <code>scripts/update</code> to upgrade to the latest version and add <code>[history]</code> to your <code>home-assistant.conf</code> file.</p>
|
||
|
||
<p class="img">
|
||
<a href="/images/screenshots/component_history_24h.png">
|
||
<img src="/images/screenshots/component_history_24h.png" />
|
||
</a>
|
||
</p>
|
||
|
||
<p class="note">
|
||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
|
||
</p>
|
||
|
||
|
||
|
||
<a class="btn pull-right" href="/blog/2015/02/08/looking-at-the-past/#read-more">Read on →</a>
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/01/24/release-notes/">Release notes for January 24, 2015</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-01-24T18:36:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 24, 2015</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
|
||
<span><i class='icon-time'></i> 1 minute reading time</span>
|
||
<span>
|
||
<i class="icon-tags"></i>
|
||
<ul class="tags unstyled">
|
||
|
||
|
||
<li><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/01/24/release-notes/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>I have just merged the latest version of the development branch into master. Here are some of the highlights of this release:</p>
|
||
|
||
<p><strong>Configuration via the frontend</strong><br /><br />
|
||
Phliips Hue will now be auto discovered and uses the new <code>configurator</code> component to interact with the user to finish the setup process.</p>
|
||
|
||
<p><strong>Wink Hub support</strong><br /><br />
|
||
Thanks to the work done by John McLaughlin and Geoff Norton we now support the lights, switches and sensors that are connected to the Wink hub.</p>
|
||
|
||
<p><strong>The getting started guide and component page have been reorganized</strong><br /><br />
|
||
The getting started instructions have been split into separate pages per component and a general overview page. The goal is to have a page per component that describes:</p>
|
||
|
||
<ul>
|
||
<li>What it does</li>
|
||
<li>How to set it up</li>
|
||
<li>Which states it maintains</li>
|
||
<li>Which services it provides</li>
|
||
<li>Additional development tips</li>
|
||
</ul>
|
||
|
||
<p><strong>More reasonable errors</strong><br /><br />
|
||
Home Assistant should now throw better errors and offer solutions if you do not have the right version of Python 3, forgot to clone the git submodules or install the dependencies.</p>
|
||
|
||
<p><strong>Streamlined first launch</strong><br /><br />
|
||
Home Assistant now supports <code>--open-ui</code> and <code>--demo-mode</code> command line properties to open the browser automatically and have something to show. Home Assistant now supports to be run without a password, allowing the interface to login automatically on launch.</p>
|
||
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/01/13/nest-in-da-house/">Nest in the house!</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-01-13T16:29:04+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 13, 2015</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><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/01/13/nest-in-da-house/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>For thet majority of its existence, Home Assistant primary focus was on presence detection, lights and switches. But not anymore as we’re expanding the supported devices. Today, we’re proud to introduce Nest Thermostat integration for Home Assistant contributed by <a href="https://github.com/sfiorini">Stefano Fiorini</a>!</p>
|
||
|
||
<p class="img">
|
||
<img src="/images/screenshots/nest-thermostat-card.png" />
|
||
</p>
|
||
|
||
<p>The new integration exists out of two parts: a generic thermostat component and a Nest platform implementation. The initial version implements provides a read-only card and services to control it. The plan is in the future to add temperature and away mode controls from the thermostat card and more info dialog. Internally, we are using the Python package <a href="https://github.com/jkoelker/python-nest">python-nest by jkoelker</a> to talk to the Nest.</p>
|
||
|
||
<p>If you own a Nest thermostat, add the following lines to your <code>home-assistant.conf</code>:</p>
|
||
|
||
<div class="highlighter-coderay"><div class="CodeRay">
|
||
<div class="code"><pre>[thermostat]
|
||
platform=nest
|
||
username=YOUR_USERNAME
|
||
password=YOUR_PASSWORD
|
||
</pre></div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/01/11/bootstrapping-your-setup-with-discovery/">Bootstrapping your setup with Discovery</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-01-11T21:49:08+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 11, 2015</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><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/01/11/bootstrapping-your-setup-with-discovery/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.</p>
|
||
|
||
<p>The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.</p>
|
||
|
||
<p>Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.</p>
|
||
|
||
<p>To enable the discovery component, add the following to your <code>home-assistant.conf</code>:</p>
|
||
|
||
<div class="highlighter-coderay"><div class="CodeRay">
|
||
<div class="code"><pre>[discovery]
|
||
</pre></div>
|
||
</div>
|
||
</div>
|
||
|
||
<p>A new <a href="/developers/add_new_platform/#discovery">discovery section</a> has been added to the Adding a new platform page with instructions how to make your platform discoverable.</p>
|
||
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/">Hello PushBullet, nice talking to you</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2015-01-04T21:29:07+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> January 4, 2015</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
|
||
<span><i class='icon-time'></i> 1 minute reading time</span>
|
||
<span>
|
||
<i class="icon-tags"></i>
|
||
<ul class="tags unstyled">
|
||
|
||
|
||
<li><a class='category' href='/blog/categories/release-notes/'>Release-Notes</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>One of the things that was missing in Home Assistant for a while was a way to communicate with users. Wouldn’t it be nice to get a message when important events happen like the lights being turned on while no one is home? Since the Home Assistant frontend runs as a web application on the phone, we have no way to bring ourselves to the front. This is where the new notify component comes in, powered by PushBullet.</p>
|
||
|
||
<p>The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome <a href="https://www.pushbullet.com/">PushBullet</a> but any other messaging platform can be easily added.</p>
|
||
|
||
<p class="img">
|
||
<img src="/images/screenshots/pushbullet_moto360.png" />
|
||
A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
|
||
</p>
|
||
|
||
<p>Read on to learn how to enable the notify component and integrate it with other components.</p>
|
||
|
||
|
||
|
||
<a class="btn pull-right" href="/blog/2015/01/04/hey-pushbullet-nice-talking-to-you/#read-more">Read on →</a>
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
<article class="listing">
|
||
<header>
|
||
|
||
<h1 class="beta">
|
||
<a href="/blog/2014/12/26/home-control-home-automation-and-the-smart-home/">Home Control, Automation & the Smart Home</a>
|
||
</h1>
|
||
|
||
|
||
|
||
<div class="meta clearfix">
|
||
<time datetime="2014-12-26T18:23:13+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> December 26, 2014</time>
|
||
<span class="byline author vcard"><i class='icon-user'></i> Paulus Schoutsen</span>
|
||
<span><i class='icon-time'></i> four minutes reading time</span>
|
||
<span>
|
||
<i class="icon-tags"></i>
|
||
<ul class="tags unstyled">
|
||
|
||
|
||
<li><a class='category' href='/blog/categories/internet-of-things/'>Internet-of-Things</a></li>
|
||
|
||
|
||
</ul>
|
||
</span>
|
||
|
||
<a class='comments'
|
||
href="/blog/2014/12/26/home-control-home-automation-and-the-smart-home/#disqus_thread"
|
||
>Comments</a>
|
||
|
||
</div>
|
||
|
||
</header>
|
||
|
||
|
||
<div class="entry-content clearfix">
|
||
<p>The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.<br />
|
||
This article will try to explain how they all relate.</p>
|
||
|
||
<p>The first thing to introduce is the <strong>Internet of Things</strong> (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.</p>
|
||
|
||
<p>There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a <strong>hub</strong>.</p>
|
||
|
||
<p>As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers <strong>home control</strong>.</p>
|
||
|
||
<p class="img">
|
||
<a href="/images/screenshots/nexus_7_dashboard.png">
|
||
<img alt="Hub dashboard example" src="/images/screenshots/nexus_7_dashboard.png" />
|
||
</a>
|
||
Example of a hub’s dashboard. Showing the state of 2 persons, 4 lights and the sun.
|
||
</p>
|
||
|
||
|
||
|
||
<a class="btn pull-right" href="/blog/2014/12/26/home-control-home-automation-and-the-smart-home/#read-more">Read on →</a>
|
||
|
||
</div>
|
||
</article>
|
||
<hr>
|
||
|
||
|
||
<div class="pagination">
|
||
|
||
<a class="btn pull-left" href="/blog/posts/6">← Older</a>
|
||
|
||
|
||
|
||
<a class="btn pull-right" href="/blog/posts/4">Newer →</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>
|
||
</ul>
|
||
</section>
|
||
<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>
|
||
|
||
|
||
<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/branding/">Branding</a></li>
|
||
|
||
<li><a href="/blog/categories/community/">Community</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/mqtt/">MQTT</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/user-stories/">User Stories</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://github.com/balloob/home-assistant'><i class="icon-github"></i></a>
|
||
|
||
<div class="credit">
|
||
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>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</footer>
|
||
|
||
<!--[if lt IE 7]>
|
||
<p class="chromeframe">You are using an <strong>outdated</strong> browser. Please <a href="http://browsehappy.com/">upgrade your browser</a> or <a href="http://www.google.com/chromeframe/?redirect=true">activate Google Chrome Frame</a> to improve your experience.</p>
|
||
<![endif]-->
|
||
|
||
<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> |