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

Site updated at 2017-07-29 22:06:40 UTC

Browse source
This commit is contained in:
Travis CI 2017-07-29 22:06:40 +00:00
parent e55d4ce725
commit 59edc9bad6
744 changed files with 14665 additions and 3545 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -67,6 +67,63 @@
<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/06/15/zwave-entity-ids/">ZWave Entity IDs</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-06-15T12:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> June 15, 2017</time>
<span class="byline author vcard"><i class='icon-user'></i> Adam Mills</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/06/15/zwave-entity-ids/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.</p>
<p>Thanks to the awesome work of <a href="https://github.com/turbokongen">@turbokongen</a>, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.</p>
<p>Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.</p>
<p>With the release of 0.47, this feature will be opt-in. Setting <code class="highlighter-rouge">new_entity_ids: true</code> under <code class="highlighter-rouge">zwave:</code> in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared <code class="highlighter-rouge">new_entity_ids: false</code> you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.</p>
<p>I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.</p>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2017/06/10/interview-with-jupiter-broadcasting/">Linux Action Show special about Home Assistant</a>
</h1>
<div class="meta clearfix">
<time datetime="2017-06-10T01:04:05+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> June 10, 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/06/10/interview-with-jupiter-broadcasting/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p>Our founder Paulus Schoutsen is interviewed by Chris Fisher for a Linux Action Show special about home automation, <a href="https://community.home-assistant.io/t/introducing-hass-io/17296/48">Hass.io</a> and the new <a href="https://hasspodcast.io/">Home Assistant podcast</a>.</p>
<div class="videoWrapper">
<iframe width="560" height="315" src="https://www.youtube.com/embed/LQbOtUmITv8" frameborder="0" allowfullscreen=""></iframe>
</div>
</div>
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
@ -426,121 +483,6 @@ If you have a security key set in your Open Z-Wave <code class="highlighter-roug
</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 our <a href="https://discord.gg/8X8DTH4">Discord chat server</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>