Site updated at 2018-01-25 17:33:45 UTC
This commit is contained in:
Travis CI
parent
2a429df2b2
commit
94552b64db
144 changed files with 304 additions and 301 deletions
|
|
@ -91,7 +91,7 @@
|
|||
<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>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of today’s release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p>
|
||||
<p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p>
|
||||
<p>The history component will be enabled for new users by default. For current users, run <code class="highlighter-rouge">scripts/update</code> to upgrade to the latest version and add <code class="highlighter-rouge">[history]</code> to your <code class="highlighter-rouge">home-assistant.conf</code> file.</p>
|
||||
<p class="img">
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
|
|||
|
|
@ -178,7 +178,7 @@
|
|||
</span><span class="kt">char</span><span class="o">*</span> <span class="n">stateTopic</span> <span class="o">=</span> <span class="s">"home-assistant/sensor01/brightness"</span><span class="p">;</span> <span class="c1">// MQTT topic where values are published
|
||||
</span><span class="kt">int</span> <span class="n">sensorPin</span> <span class="o">=</span> <span class="n">A0</span><span class="p">;</span> <span class="c1">// Pin to which the sensor is connected to
|
||||
</span><span class="kt">char</span> <span class="n">buf</span><span class="p">[</span><span class="mi">4</span><span class="p">];</span> <span class="c1">// Buffer to store the sensor value
|
||||
</span><span class="kt">int</span> <span class="n">updateInterval</span> <span class="o">=</span> <span class="mi">1000</span><span class="p">;</span> <span class="c1">// Interval in miliseconds
|
||||
</span><span class="kt">int</span> <span class="n">updateInterval</span> <span class="o">=</span> <span class="mi">1000</span><span class="p">;</span> <span class="c1">// Interval in milliseconds
|
||||
</span>
|
||||
<span class="c1">// MQTT server settings
|
||||
</span><span class="n">IPAddress</span> <span class="n">mqttServer</span><span class="p">(</span><span class="mi">192</span><span class="p">,</span> <span class="mi">168</span><span class="p">,</span> <span class="mi">0</span><span class="p">,</span> <span class="mi">12</span><span class="p">);</span>
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p><img src="/images/supported_brands/glances.png" style="border:none; box-shadow: none; float: right;" height="80" />
|
||||
Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p>
|
||||
Inspired by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p>
|
||||
<a name="read-more"></a>
|
||||
<p>The basic problem is to get the data from the remote host. Starting with <a href="https://pypi.python.org/pypi/psutil">psutil</a> that is used by the systemmonitor sensor, a possible solution is only a click away and named <a href="https://github.com/nicolargo/glances">Glances</a>. Glances has a nice curses-based interface and a <a href="https://github.com/nicolargo/glances/wiki/The-Glances-RESTFULL-JSON-API">RESTful API</a>.</p>
|
||||
<p>The <a href="/components/sensor.glances/">Glances sensor</a> sensor uses that API to get all needed data.</p>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Updated documentation - Home Assistant</title>
|
||||
<meta name="author" content="Paulus Schoutsen">
|
||||
<meta name="description" content="We have reorganised our documentation which should make it easier to get started and develop for Home Assistant.">
|
||||
<meta name="description" content="We have reorganized our documentation which should make it easier to get started and develop for Home Assistant.">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/blog/2016/04/17/updated-documentation/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
|
|
@ -16,13 +16,13 @@
|
|||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/blog/2016/04/17/updated-documentation/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="We have reorganised our documentation which should make it easier to get started and develop for Home Assistant.">
|
||||
<meta property="og:description" content="We have reorganized our documentation which should make it easier to get started and develop for Home Assistant.">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:creator" content="@balloob">
|
||||
<meta name="twitter:title" content="Updated documentation">
|
||||
<meta name="twitter:description" content="We have reorganised our documentation which should make it easier to get started and develop for Home Assistant.">
|
||||
<meta name="twitter:description" content="We have reorganized our documentation which should make it easier to get started and develop for Home Assistant.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
|
@ -88,7 +88,7 @@
|
|||
</header>
|
||||
<p>One of the main complaints that we receive is something along the lines “I read that X is possible yet I am unable to find it on the website.”. This post is to announce that we have taken the first steps to improve it by revamping the <a href="/getting-started/">getting started</a> and <a href="/developers/">developers</a> sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.</p>
|
||||
<p>Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and <a href="/blog/2014/12/18/website-launched/">called it a website</a>. Back then we had a whopping <a href="https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown">11 components</a>.</p>
|
||||
<p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organisation.</p>
|
||||
<p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organization.</p>
|
||||
<p>Today it has been almost 1.5 years since we started the website. We now have <a href="/components/">264 components and platforms</a> under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.</p>
|
||||
<p>Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.</p>
|
||||
</article>
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
@ -86,7 +86,7 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organisation on GitHub</a>.</p>
|
||||
<p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organization on GitHub</a>.</p>
|
||||
<p>On our journey we’ve reached many noteworthy milestones:</p>
|
||||
<ul>
|
||||
<li>#1 on HackerNews</li>
|
||||
|
|
|
|||
|
|
@ -86,8 +86,8 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.</p>
|
||||
<p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organisation on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p>
|
||||
<p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.</p>
|
||||
<p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organization on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p>
|
||||
<p><a href="/demo/"><img src="/images/blog/2016-04-release-18/media_player.png" style="box-shadow: none; border: 0;" /></a></p>
|
||||
<p><img src="/images/supported_brands/bluetooth.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/webos.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/rss.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/eq3.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/thinkingcleaner.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -93,11 +93,11 @@
|
|||
<p>The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in <em>part 1</em>. In <em>part 2</em> I’ll talk about using iBeacons to track devices that can’t track themselves.</p>
|
||||
<h3><a class="title-link" name="using-beacons-to-improve-owntracks-location-data" href="#using-beacons-to-improve-owntracks-location-data"></a> Using beacons to improve OwnTracks location data</h3>
|
||||
<p>When you use OwnTracks in standard <em>major move</em> mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!</p>
|
||||
<p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p>
|
||||
<p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p>
|
||||
<a name="read-more"></a>
|
||||
<h3><a class="title-link" name="getting-started" href="#getting-started"></a> Getting Started</h3>
|
||||
<p>To do this you first need to set up <a href="/components/mqtt/#picking-a-broker">MQTT</a> and <a href="/components/device_tracker.owntracks/">OwnTracks</a> in Home assistant - and make sure that HA can track your phone.</p>
|
||||
<p>You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.</p>
|
||||
<p>You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.</p>
|
||||
<h4><a class="title-link" name="a-tell-home-assistant-where-your-beacon-is-located" href="#a-tell-home-assistant-where-your-beacon-is-located"></a> A. Tell Home Assistant where your beacon is located</h4>
|
||||
<p>You tell HomeAssistant about fixed locations by creating a Zone with the longitude and latitude of your beacon. You should also give the zone a name which you will also use when you set up OwnTracks. An an example this zone specifies the location of my drive way.</p>
|
||||
<p><strong>Example <code class="highlighter-rouge">configuration.yaml</code> entry</strong></p>
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ crw-rw----+ 1 root video 81, 0 Jun 23 08:05 /dev/video0
|
|||
crw-rw----+ 1 root video 81, 1 Jun 23 08:36 /dev/video1
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>We need an additional software part to handle the cameras. <a href="http://lavrsen.dk/foswiki/bin/view/Motion/WebHome">motion</a> is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the <a href="http://rpmfusion.org/">RPM Fusion respository</a> enabled.</p>
|
||||
<p>We need an additional software part to handle the cameras. <a href="http://lavrsen.dk/foswiki/bin/view/Motion/WebHome">motion</a> is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the <a href="http://rpmfusion.org/">RPM Fusion repository</a> enabled.</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo dnf -y install motion
|
||||
</code></pre>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -157,7 +157,7 @@ SQLite version 3.11.0 2016-02-15 17:29:24
|
|||
<span class="n">plt</span><span class="o">.</span><span class="n">savefig</span><span class="p">(</span><span class="s">'sensor.png'</span><span class="p">)</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are splitted into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.</p>
|
||||
<p>Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are split into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.</p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2016-07-reporting/mpl-sensor.png" />
|
||||
Sensor graph generated by matplotlib
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p>When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!</p>
|
||||
<p>Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p>
|
||||
<p>Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p>
|
||||
<p>We have also seen an exciting trend of people starting to visualize their Internet of Things data using <a href="http://jupyter.org/">Jupyter</a> Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the <a href="/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/">blog</a> post by <a href="https://github.com/kireyeu">@kireyeu</a> shows an advanced usecase while our <a href="/cookbook/#jupyter-notebooks">Notebooks</a> in the <a href="https://github.com/home-assistant/home-assistant-notebooks">Home Assistant Notebooks repository</a> cover the basics.</p>
|
||||
<p>This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!</p>
|
||||
<p>The brand-new <a href="/components/panel_iframe/">iFrame panel component</a> allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.</p>
|
||||
|
|
|
|||
|
|
@ -91,11 +91,11 @@
|
|||
<p>Do less and be lazy. It sounds so obvious and it took a while before it started to dawn on me. I think most of the code I write is pretty fast, but I don’t often stop to take a harder look at how and when it runs in practice. When do we need the result, can it be postponed?</p>
|
||||
<p>And thus started my journey to take a critical look at how the Home Assistant app was working and how to make things faster. Below is the list of the different things that I did to make it fast.</p>
|
||||
<p>I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.</p>
|
||||
<p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 miliseconds and on my Nexus 5x in ~6500 miliseconds (~4.5 times slower!).</strong></p>
|
||||
<p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 milliseconds and on my Nexus 5x in ~6500 milliseconds (~4.5 times slower!).</strong></p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.18.2.png" alt="Timeline of loading the front end in Home Assistant 0.18.2" />
|
||||
</p>
|
||||
<p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 miliseconds (-35%) on my Mac and 2400 miliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p>
|
||||
<p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 milliseconds (-35%) on my Mac and 2400 milliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2016-08-optimizing-web-app/performance-diagram.png" alt="diagram showing old and new loading times next to one another" />
|
||||
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.26.png" alt="Timeline of loading the front end in Home Assistant 0.26" />
|
||||
|
|
|
|||
|
|
@ -97,9 +97,9 @@
|
|||
<h3><a class="title-link" name="climate-and--cover" href="#climate-and--cover"></a> Climate and cover</h3>
|
||||
<p>There are countless bugfixes included in this release which will make your experience with the <code class="highlighter-rouge">climate</code> and the <code class="highlighter-rouge">cover</code> platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/djbanks">@djbanks</a>, <a href="https://github.com/danielperna84">@danielperna84</a>, and others the improvements on the code and the frontend side is continuing…</p>
|
||||
<h3><a class="title-link" name="api-documentation" href="#api-documentation"></a> API documentation</h3>
|
||||
<p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p>
|
||||
<p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p>
|
||||
<h3><a class="title-link" name="configuration-validation" href="#configuration-validation"></a> Configuration validation</h3>
|
||||
<p>The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p>
|
||||
<p>The validation of the configuration is still on-going. Approximately 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p>
|
||||
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
|
||||
<p><img src="/images/supported_brands/xbox-live.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/automatic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/pi_hole.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>We have a Raspberry Pi image now - Home Assistant</title>
|
||||
<meta name="author" content="Fredrik Lindqvist">
|
||||
<meta name="description" content="Release of the Rapsberry Pi Image for Home Assistant">
|
||||
<meta name="description" content="Release of the Raspberry Pi Image for Home Assistant">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/blog/2016/10/01/we-have-raspberry-image-now/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
|
|
@ -16,12 +16,12 @@
|
|||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/blog/2016/10/01/we-have-raspberry-image-now/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="Release of the Rapsberry Pi Image for Home Assistant">
|
||||
<meta property="og:description" content="Release of the Raspberry Pi Image for Home Assistant">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/blog/2016-10-hassbian/social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="We have a Raspberry Pi image now">
|
||||
<meta name="twitter:description" content="Release of the Rapsberry Pi Image for Home Assistant">
|
||||
<meta name="twitter:description" content="Release of the Raspberry Pi Image for Home Assistant">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/blog/2016-10-hassbian/social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p>
|
||||
<p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organized by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p>
|
||||
<p>Why contribute to Home Assistant:</p>
|
||||
<ul>
|
||||
<li>Written in Python3 with 94% test coverage</li>
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
|
|||
|
|
@ -182,7 +182,7 @@
|
|||
<li>Switch - Pilight: Implement echo config option (<a href="https://github.com/janLo">@janLo</a>)</li>
|
||||
<li>Core: Support customize in packages (<a href="https://github.com/kellerza">@kellerza</a>)</li>
|
||||
<li>Switch - Flux: Allow disabling setting the brightness (<a href="https://github.com/rytilahti">@rytilahti</a>)</li>
|
||||
<li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no emtpy image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no empty image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Climate: Hold mode (<a href="https://github.com/Duoxilian">@Duoxilian</a>)</li>
|
||||
<li>Switch - TPlink: No longer doing I/O in event bus (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Light - Insteon local: Improve Insteon configuration (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li>
|
||||
|
|
|
|||
|
|
@ -250,7 +250,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
|
|||
<li>Add multi contracts support for Hydroquebec (<a href="https://github.com/titilambert">@titilambert</a>)</li>
|
||||
<li>Add Zwave refresh services (<a href="https://github.com/andrey-git">@andrey-git</a>)</li>
|
||||
<li>Add keep-alive feature to the generic thermostat (<a href="https://github.com/aronsky">@aronsky</a>)</li>
|
||||
<li>Fix wake_on_lan for german version of Windows 10 (#6397) (<a href="https://github.com/siebert">@siebert</a>)</li>
|
||||
<li>Fix wake_on_lan for German version of Windows 10 (#6397) (<a href="https://github.com/siebert">@siebert</a>)</li>
|
||||
<li>flux led lib (<a href="https://github.com/danielhiversen">@danielhiversen</a>)</li>
|
||||
<li>Cleanup async handling (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
|
||||
<li>Restore for automation entities (<a href="https://github.com/kellerza">@kellerza</a>)</li>
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@
|
|||
<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>The decision of the jury will be final. If there will be a dispute then the Top-5 committer of the Home Assistant organization on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p>
|
||||
<p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p>
|
||||
</article>
|
||||
<section id="disqus">
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@
|
|||
<h2>Breaking changes</h2>
|
||||
<ul>
|
||||
<li>We were incorrectly treating groups named <code class="highlighter-rouge">default_view</code> as default views. Make sure you set <code class="highlighter-rouge">view: true</code> in the config for these groups. <a href="https://github.com/home-assistant/home-assistant-polymer/pull/251">#251 (frontend)</a></li>
|
||||
<li>The last release introduced a revamped LIFX platform. We only realised after deploy that this version does not work on Windows. We have added the old LIFX implementation back as <code class="highlighter-rouge">lifx_legacy</code>.</li>
|
||||
<li>The last release introduced a revamped LIFX platform. We only realized after deploy that this version does not work on Windows. We have added the old LIFX implementation back as <code class="highlighter-rouge">lifx_legacy</code>.</li>
|
||||
<li>We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. <a href="https://github.com/home-assistant/home-assistant/pull/6688">#6688</a></li>
|
||||
<li>Z-Wave cover workaround has been removed. Use device config instead. <a href="https://github.com/home-assistant/home-assistant/pull/6832">#6832</a></li>
|
||||
</ul>
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@
|
|||
<p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p>
|
||||
<p>I 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>It may not look the way that I wanted it to initially, with beautiful native UI components, but that’s okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p>
|
||||
<p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p>
|
||||
<p>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>
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@
|
|||
<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 Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that’s used with Amazon Echo, Google Home and Mycroft.ai.</li>
|
||||
<li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li>
|
||||
<li>Install 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>
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@
|
|||
<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>.
|
||||
<p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspberry Pi Zero W</a>.
|
||||
<strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p>
|
||||
<p>What you’ll need:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ Screenshot of the new customize editor.
|
|||
<h2><a class="title-link" name="input-text" href="#input-text"></a> Input text</h2>
|
||||
<p>This release introduces a new input component: <code class="highlighter-rouge">input_text</code> contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.</p>
|
||||
<h2><a class="title-link" name="knx" href="#knx"></a> KNX</h2>
|
||||
<p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p>
|
||||
<p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunneling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p>
|
||||
<div class="videoWrapper">
|
||||
<iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen=""></iframe>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@
|
|||
<p>The most amazing part? It is super easy to set up!</p>
|
||||
<a name="read-more"></a>
|
||||
<h2><a class="title-link" name="setting-up-tor" href="#setting-up-tor"></a> Setting up Tor</h2>
|
||||
<p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailled guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p>
|
||||
<p>Our <a href="/docs/ecosystem/tor/">documentation</a> provides an detailed guide about seting up a <a href="https://www.torproject.org/docs/hidden-services.html.en">Tor’s Hidden Service</a>. The setup is straight-forward:</p>
|
||||
<ol>
|
||||
<li>Install Tor. On a Debian-based system: <code class="highlighter-rouge">$ sudo apt-get install tor</code>. On Fedora: <code class="highlighter-rouge">$ sudo dnf install tor</code></li>
|
||||
<li>
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@
|
|||
The Hass.io release of 0.58 will be delayed by a couple of days because Pascal is moving this weekend.
|
||||
</p>
|
||||
<h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2>
|
||||
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.</p>
|
||||
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.</p>
|
||||
<p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p>
|
||||
<p>And because more translations is more better, <a href="https://github.com/robbiet480">@robbiet480</a> has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.</p>
|
||||
<p><a href="https://home-assistant.io/blog/2017/11/05/frontend-translations/">Learn more about how to help with translations</a></p>
|
||||
|
|
|
|||
|
|
@ -97,12 +97,12 @@
|
|||
Screenshot of the color wheel.
|
||||
</p>
|
||||
<h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2>
|
||||
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editting has been made easier.</p>
|
||||
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editing has been made easier.</p>
|
||||
<h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2>
|
||||
<p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." />
|
||||
Screenshot of the of the Enitity Picker.
|
||||
Screenshot of the of the Entity Picker.
|
||||
</p>
|
||||
<h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2>
|
||||
<p>If you follow our <a href="https://twitter.com/home_assistant">twitter feed</a> then you may already know that <a href="https://github.com/frenck">@frenck</a> spent some time to bring new stuff to the <a href="https://github.com/hassio-addons/repository">Community Hass.io Add-ons repository</a>.</p>
|
||||
|
|
|
|||
|
|
@ -280,7 +280,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -1212,7 +1212,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -1961,7 +1961,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -2151,7 +2151,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Announcements | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/announcements/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -227,7 +227,7 @@ I received emails and forum posts almost every day, even when the app would go w
|
|||
|
||||
I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
|
||||
|
||||
It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
|
||||
It may not look the way that I wanted it to initially, with beautiful native UI components, but that's okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
|
||||
|
||||
Just because the app is released doesn't mean we are at the end of the road. It's only the beginning. There's plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that's pretty hard with how fast the project moves.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Community | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/community/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Device-Tracking | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/device-tracking/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: ESP8266 | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/esp8266/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: How-To | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/how-to/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -181,7 +181,7 @@ The most amazing part? It is super easy to set up!
|
|||
|
||||
## <a class='title-link' name='setting-up-tor' href='#setting-up-tor'></a> Setting up Tor
|
||||
|
||||
Our [documentation](/docs/ecosystem/tor/) provides an detailled guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
|
||||
Our [documentation](/docs/ecosystem/tor/) provides an detailed guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
|
||||
|
||||
1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor`
|
||||
2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines:
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: iBeacons | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/ibeacons/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -183,7 +183,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
|
|||
|
||||
When you use OwnTracks in standard _major move_ mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
|
||||
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
@ -194,7 +194,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
|
|||
[MQTT]: /components/mqtt/#picking-a-broker
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
|
||||
|
||||
#### <a class='title-link' name='a-tell-home-assistant-where-your-beacon-is-located' href='#a-tell-home-assistant-where-your-beacon-is-located'></a> A. Tell Home Assistant where your beacon is located
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Internet-of-Things | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/internet-of-things/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: IoT-Data | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/iot-data/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -205,7 +205,7 @@ plt.xlabel('Time line')
|
|||
plt.savefig('sensor.png')
|
||||
```
|
||||
|
||||
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are splitted into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
|
||||
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are split into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2016-07-reporting/mpl-sensor.png' />
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Media | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/media/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Merchandise | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/merchandise/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Micropython | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/micropython/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: MQTT | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/mqtt/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -673,7 +673,7 @@ char* deviceId = "sensor01"; // Name of the sensor
|
|||
char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published
|
||||
int sensorPin = A0; // Pin to which the sensor is connected to
|
||||
char buf[4]; // Buffer to store the sensor value
|
||||
int updateInterval = 1000; // Interval in miliseconds
|
||||
int updateInterval = 1000; // Interval in milliseconds
|
||||
|
||||
// MQTT server settings
|
||||
IPAddress mqttServer(192, 168, 0, 12);
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<feed xmlns="http://www.w3.org/2005/Atom">
|
||||
|
||||
<title><![CDATA[Category: Organisation | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/>
|
||||
<title><![CDATA[Category: Organization | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/organization/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -173,7 +173,7 @@ The source code of our updater AWS Lambda function is now available [here][sourc
|
|||
<link href="https://home-assistant.io/blog/2016/04/19/to-infinity-and-beyond/"/>
|
||||
<updated>2016-04-19T22:44:00+00:00</updated>
|
||||
<id>https://home-assistant.io/blog/2016/04/19/to-infinity-and-beyond</id>
|
||||
<content type="html"><![CDATA[After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organisation on GitHub][gh-ha].
|
||||
<content type="html"><![CDATA[After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organization on GitHub][gh-ha].
|
||||
|
||||
On our journey we've reached many noteworthy milestones:
|
||||
|
||||
|
|
@ -6,22 +6,22 @@
|
|||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>Category: Organisation - Home Assistant</title>
|
||||
<title>Category: Organization - Home Assistant</title>
|
||||
<meta name="author" content="Home Assistant">
|
||||
<meta name="description" content="Category: Organisation">
|
||||
<meta name="description" content="Category: Organization">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/blog/categories/organisation/">
|
||||
<link rel="canonical" href="https://home-assistant.io/blog/categories/organization/">
|
||||
<meta property="fb:app_id" content="338291289691179">
|
||||
<meta property="og:title" content="Category: Organisation">
|
||||
<meta property="og:title" content="Category: Organization">
|
||||
<meta property="og:site_name" content="Home Assistant">
|
||||
<meta property="og:url" content="https://home-assistant.io/blog/categories/organisation/">
|
||||
<meta property="og:url" content="https://home-assistant.io/blog/categories/organization/">
|
||||
<meta property="og:type" content="website">
|
||||
<meta property="og:description" content="Category: Organisation">
|
||||
<meta property="og:description" content="Category: Organization">
|
||||
<meta property="og:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@home_assistant">
|
||||
<meta name="twitter:title" content="Category: Organisation">
|
||||
<meta name="twitter:description" content="Category: Organisation">
|
||||
<meta name="twitter:title" content="Category: Organization">
|
||||
<meta name="twitter:description" content="Category: Organization">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
|
@ -68,10 +68,10 @@
|
|||
<div class="grid grid-center">
|
||||
<div class="grid__item two-thirds lap-one-whole palm-one-whole">
|
||||
<article class="page">
|
||||
<div class='edit-github'><a href='https://github.com/home-assistant/home-assistant.github.io/tree/current/source/blog/categories/organisation/index.html'>Edit this page on GitHub</a></div>
|
||||
<div class='edit-github'><a href='https://github.com/home-assistant/home-assistant.github.io/tree/current/source/blog/categories/organization/index.html'>Edit this page on GitHub</a></div>
|
||||
<header>
|
||||
<h1 class="title indent">
|
||||
Category: Organisation
|
||||
Category: Organization
|
||||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
|
|
@ -90,7 +90,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -112,7 +112,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -133,7 +133,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -155,7 +155,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
</footer>
|
||||
|
|
@ -189,10 +189,10 @@
|
|||
class="twitter-share-button"
|
||||
data-via="home_assistant"
|
||||
data-related="home_assistant"
|
||||
data-url="https://home-assistant.io/blog/categories/organisation/"
|
||||
data-counturl="https://home-assistant.io/blog/categories/organisation/" >Tweet</a>
|
||||
data-url="https://home-assistant.io/blog/categories/organization/"
|
||||
data-counturl="https://home-assistant.io/blog/categories/organization/" >Tweet</a>
|
||||
<div class="fb-share-button" style='top: -6px;'
|
||||
data-href="https://home-assistant.io/blog/categories/organisation/"
|
||||
data-href="https://home-assistant.io/blog/categories/organization/"
|
||||
data-layout="button_count">
|
||||
</div>
|
||||
<div class="g-plusone" data-size="standard"></div>
|
||||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: OwnTracks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/owntracks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -183,7 +183,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
|
|||
|
||||
When you use OwnTracks in standard _major move_ mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
|
||||
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
@ -194,7 +194,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
|
|||
[MQTT]: /components/mqtt/#picking-a-broker
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
|
||||
|
||||
#### <a class='title-link' name='a-tell-home-assistant-where-your-beacon-is-located' href='#a-tell-home-assistant-where-your-beacon-is-located'></a> A. Tell Home Assistant where your beacon is located
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Presence-Detection | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/presence-detection/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -28,7 +28,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
|
|||
|
||||
When you use OwnTracks in standard _major move_ mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
|
||||
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
|
|||
[MQTT]: /components/mqtt/#picking-a-broker
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
|
||||
|
||||
#### <a class='title-link' name='a-tell-home-assistant-where-your-beacon-is-located' href='#a-tell-home-assistant-where-your-beacon-is-located'></a> A. Tell Home Assistant where your beacon is located
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Public-Service-Announcement | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/public-service-announcement/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Release-Notes | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/release-notes/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -1229,14 +1229,14 @@ With the Dominos Pizza integration made by [@wardcraigj] your home is now taking
|
|||
</p>
|
||||
|
||||
## <a class='title-link' name='shopping-list-tweaks' href='#shopping-list-tweaks'></a> Shopping list tweaks
|
||||
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editting has been made easier.
|
||||
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editing has been made easier.
|
||||
|
||||
## <a class='title-link' name='entity-picker' href='#entity-picker'></a> Entity picker
|
||||
[@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2017-12-0.59/picker.png' alt='Screenshot of the Entity Picker.'>
|
||||
Screenshot of the of the Enitity Picker.
|
||||
Screenshot of the of the Entity Picker.
|
||||
</p>
|
||||
|
||||
## <a class='title-link' name='hassio-add-ons' href='#hassio-add-ons'></a> Hass.io Add-ons
|
||||
|
|
@ -1647,7 +1647,7 @@ The Hass.io release of 0.58 will be delayed by a couple of days because Pascal i
|
|||
|
||||
## <a class='title-link' name='translation-update' href='#translation-update'></a> Translation update
|
||||
|
||||
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.
|
||||
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.
|
||||
|
||||
Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Survey | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/survey/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Talks | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/talks/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Technology | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/technology/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -163,7 +163,7 @@ With the release of 1.21 a small problem with the OpenZWave build script wasn't
|
|||
|
||||
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the `hassbian-scripts` functionality from 1.1.
|
||||
|
||||
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
|
||||
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that's used with Amazon Echo, Google Home and Mycroft.ai.
|
||||
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
|
||||
- Install Libcec. Adds local [HDMI CEC support][cec].
|
||||
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: User-Stories | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/user-stories/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Video | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/video/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Website | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/website/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2018-01-24T13:02:59+00:00</updated>
|
||||
<updated>2018-01-25T17:24:11+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -22,7 +22,7 @@
|
|||
|
||||
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and [called it a website]. Back then we had a whopping [11 components](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown).
|
||||
|
||||
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organisation.
|
||||
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that's quite a feat given our [frequent releases](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
|
||||
|
||||
Today it has been almost 1.5 years since we started the website. We now have [264 components and platforms] under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
|
||||
|
||||
|
|
|
|||
|
|
@ -393,12 +393,12 @@ broadlink.send_packet_192_168_0_107 -> switch.broadlink_send_packet_192_168_0
|
|||
Screenshot of the color wheel.
|
||||
</p>
|
||||
<h2><a class="title-link" name="shopping-list-tweaks" href="#shopping-list-tweaks"></a> Shopping list tweaks</h2>
|
||||
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editting has been made easier.</p>
|
||||
<p><a href="https://github.com/balloob">@balloob</a> has refreshed the shopping list UI to make it more usable. It’s now possible to add items by typing, instead of just voice. Also editing has been made easier.</p>
|
||||
<h2><a class="title-link" name="entity-picker" href="#entity-picker"></a> Entity picker</h2>
|
||||
<p><a href="https://github.com/balloob">@balloob</a> improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it’s much easier to identify the right one! The automation editor will only suggest relevant entities.</p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2017-12-0.59/picker.png" alt="Screenshot of the Entity Picker." />
|
||||
Screenshot of the of the Enitity Picker.
|
||||
Screenshot of the of the Entity Picker.
|
||||
</p>
|
||||
<h2><a class="title-link" name="hassio-add-ons" href="#hassio-add-ons"></a> Hass.io Add-ons</h2>
|
||||
<p>If you follow our <a href="https://twitter.com/home_assistant">twitter feed</a> then you may already know that <a href="https://github.com/frenck">@frenck</a> spent some time to bring new stuff to the <a href="https://github.com/hassio-addons/repository">Community Hass.io Add-ons repository</a>.</p>
|
||||
|
|
@ -492,7 +492,7 @@ broadlink.send_packet_192_168_0_107 -> switch.broadlink_send_packet_192_168_0
|
|||
The Hass.io release of 0.58 will be delayed by a couple of days because Pascal is moving this weekend.
|
||||
</p>
|
||||
<h2><a class="title-link" name="translation-update" href="#translation-update"></a> Translation update</h2>
|
||||
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.</p>
|
||||
<p>Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. <a href="https://github.com/armills">@armills</a> and <a href="https://github.com/c727">@c727</a> are doing an amazing job managing this project. We’ve doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.</p>
|
||||
<p>Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!</p>
|
||||
<p>And because more translations is more better, <a href="https://github.com/robbiet480">@robbiet480</a> has added the iOS app to Lokalise, our translation management platform. The iOS app is currently supported in 7 different languages.</p>
|
||||
<p><a href="https://home-assistant.io/blog/2017/11/05/frontend-translations/">Learn more about how to help with translations</a></p>
|
||||
|
|
@ -635,7 +635,7 @@ For Custom UI users: your custom UI will need to be updated before it can work w
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -200,11 +200,11 @@
|
|||
<p>Do less and be lazy. It sounds so obvious and it took a while before it started to dawn on me. I think most of the code I write is pretty fast, but I don’t often stop to take a harder look at how and when it runs in practice. When do we need the result, can it be postponed?</p>
|
||||
<p>And thus started my journey to take a critical look at how the Home Assistant app was working and how to make things faster. Below is the list of the different things that I did to make it fast.</p>
|
||||
<p>I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.</p>
|
||||
<p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 miliseconds and on my Nexus 5x in ~6500 miliseconds (~4.5 times slower!).</strong></p>
|
||||
<p>The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. <strong>On my Mac the app starts in 1400 milliseconds and on my Nexus 5x in ~6500 milliseconds (~4.5 times slower!).</strong></p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.18.2.png" alt="Timeline of loading the front end in Home Assistant 0.18.2" />
|
||||
</p>
|
||||
<p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 miliseconds (-35%) on my Mac and 2400 miliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p>
|
||||
<p>Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 milliseconds (-35%) on my Mac and 2400 milliseconds (-63%) on my Nexus 5x. <a href="https://home-assistant.io/demo">Check out the demo here.</a></p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2016-08-optimizing-web-app/performance-diagram.png" alt="diagram showing old and new loading times next to one another" />
|
||||
<img src="/images/blog/2016-08-optimizing-web-app/performance-timeline-0.26.png" alt="Timeline of loading the front end in Home Assistant 0.26" />
|
||||
|
|
@ -267,7 +267,7 @@
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!</p>
|
||||
<p>Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p>
|
||||
<p>Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can <a href="/developers/frontend_creating_custom_panels/">add it’s own page to the frontend</a>. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you’ll come up with!</p>
|
||||
<p>We have also seen an exciting trend of people starting to visualize their Internet of Things data using <a href="http://jupyter.org/">Jupyter</a> Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the <a href="/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/">blog</a> post by <a href="https://github.com/kireyeu">@kireyeu</a> shows an advanced usecase while our <a href="/cookbook/#jupyter-notebooks">Notebooks</a> in the <a href="https://github.com/home-assistant/home-assistant-notebooks">Home Assistant Notebooks repository</a> cover the basics.</p>
|
||||
<p>This release also includes a bunch of new integrations, among others three new media player platforms. This means that today Home Assistant can talk to 26 different media players!</p>
|
||||
<p>The brand-new <a href="/components/panel_iframe/">iFrame panel component</a> allows you to add other websites as pages in the Home Assistant frontend. They will show up in the sidebar and can be used the same way as you open the frontend in your browser but all within one view.</p>
|
||||
|
|
@ -550,7 +550,7 @@ Over a year ago I participated in the <a href="https://www.kickstarter.com/proje
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -574,7 +574,7 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -256,7 +256,7 @@
|
|||
<p>The reason I started using iBeacons was to improve presence detection (and I think that’s the case with most people) so that’s what I’ll discuss in <em>part 1</em>. In <em>part 2</em> I’ll talk about using iBeacons to track devices that can’t track themselves.</p>
|
||||
<h3><a class="title-link" name="using-beacons-to-improve-owntracks-location-data" href="#using-beacons-to-improve-owntracks-location-data"></a> Using beacons to improve OwnTracks location data</h3>
|
||||
<p>When you use OwnTracks in standard <em>major move</em> mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!</p>
|
||||
<p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p>
|
||||
<p>Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.</p>
|
||||
<a class="btn pull-right" href="/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/#read-more">Read on →</a>
|
||||
</div>
|
||||
</article>
|
||||
|
|
@ -282,8 +282,8 @@
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.</p>
|
||||
<p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organisation on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p>
|
||||
<p>It’s time for 0.18. This release cycle is 2 days shorter than usual as I’ll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.</p>
|
||||
<p>Since the last release we have moved all Home Assistant source code etc into it’s own <a href="https://github.com/home-assistant">organization on GitHub</a>. We’re growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.</p>
|
||||
<p><a href="/demo/"><img src="/images/blog/2016-04-release-18/media_player.png" style="box-shadow: none; border: 0;" /></a></p>
|
||||
<p><img src="/images/supported_brands/bluetooth.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/webos.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/rss.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/eq3.gif" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="150" /><img src="/images/supported_brands/thinkingcleaner.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
|
||||
<ul>
|
||||
|
|
@ -336,7 +336,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
@ -345,7 +345,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organisation on GitHub</a>.</p>
|
||||
<p>After 2.5 years I think we can proudly say: Home Assistant is a success. I write <em>we</em> because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own <a href="https://github.com/home-assistant/">organization on GitHub</a>.</p>
|
||||
<p>On our journey we’ve reached many noteworthy milestones:</p>
|
||||
<ul>
|
||||
<li>#1 on HackerNews</li>
|
||||
|
|
@ -388,7 +388,7 @@
|
|||
<div class="entry-content clearfix">
|
||||
<p>One of the main complaints that we receive is something along the lines “I read that X is possible yet I am unable to find it on the website.”. This post is to announce that we have taken the first steps to improve it by revamping the <a href="/getting-started/">getting started</a> and <a href="/developers/">developers</a> sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.</p>
|
||||
<p>Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and <a href="/blog/2014/12/18/website-launched/">called it a website</a>. Back then we had a whopping <a href="https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown">11 components</a>.</p>
|
||||
<p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organisation.</p>
|
||||
<p>As Home Assistant grew, so did our documentation. <a href="https://github.com/fabaff">Fabian Affolter</a> does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our <a href="https://home-assistant.io/blog/categories/release-notes/">frequent releases</a>! But despite all the efforts, the documentation outgrew our existing documentation organization.</p>
|
||||
<p>Today it has been almost 1.5 years since we started the website. We now have <a href="/components/">264 components and platforms</a> under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.</p>
|
||||
<p>Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.</p>
|
||||
</div>
|
||||
|
|
@ -534,7 +534,7 @@
|
|||
<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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -650,7 +650,7 @@ Example of the new views in the frontend. <a href="/components/group/">Learn mor
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -475,7 +475,7 @@ The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time se
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -300,7 +300,7 @@ Map in Home Assistant showing two people and three zones (home, school, work)
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p><img src="/images/supported_brands/glances.png" style="border:none; box-shadow: none; float: right;" height="80" />
|
||||
Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p>
|
||||
Inspired by a <a href="https://github.com/home-assistant/home-assistant/issues/310">feature requests</a> I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the <a href="/components/sensor.systemmonitor/">systemmonitor</a> sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.</p>
|
||||
<a class="btn pull-right" href="/blog/2015/09/18/monitoring-with-glances-and-home-assistant/#read-more">Read on →</a>
|
||||
</div>
|
||||
</article>
|
||||
|
|
@ -478,7 +478,7 @@ Inspried by a <a href="https://github.com/home-assistant/home-assistant/issues/3
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -458,7 +458,7 @@ An initial version of voice control for Home Assistant has landed. The current i
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
@ -512,7 +512,7 @@ The old logo, the new detailed logo and the new simple logo.
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -149,7 +149,7 @@
|
|||
<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>By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of today’s release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.</p>
|
||||
<p>Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.</p>
|
||||
<p>The history component will be enabled for new users by default. For current users, run <code class="highlighter-rouge">scripts/update</code> to upgrade to the latest version and add <code class="highlighter-rouge">[history]</code> to your <code class="highlighter-rouge">home-assistant.conf</code> file.</p>
|
||||
<p class="img">
|
||||
|
|
@ -402,7 +402,7 @@ This article will try to explain how they all relate.</p>
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -549,7 +549,7 @@ The Home Assistant sidebar in 12 different languages.
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -361,7 +361,7 @@ Screenshot of the new customize editor.
|
|||
<h2><a class="title-link" name="input-text" href="#input-text"></a> Input text</h2>
|
||||
<p>This release introduces a new input component: <code class="highlighter-rouge">input_text</code> contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.</p>
|
||||
<h2><a class="title-link" name="knx" href="#knx"></a> KNX</h2>
|
||||
<p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p>
|
||||
<p>This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunneling devices. In the background it uses asyncio communication. Check the climate integration in action <a href="https://www.youtube.com/watch?v=JI0VJzlGpx4">here</a> and see the lights in action below:</p>
|
||||
<div class="videoWrapper">
|
||||
<iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen=""></iframe>
|
||||
</div>
|
||||
|
|
@ -607,7 +607,7 @@ Screenshot of the new customize editor.
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -601,7 +601,7 @@ Screenshot of a green dashboard
|
|||
<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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -522,7 +522,7 @@ If you have a security key set in your Open Z-Wave <code class="highlighter-roug
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@
|
|||
<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>.
|
||||
<p>Today we’ll flash the latest HASSbian to a <a href="https://www.raspberrypi.org/products/pi-zero/">Raspberry Pi Zero W</a>.
|
||||
<strong>With an added bonus</strong> that besides for an USB cable for power, there’s no need for any cables!</p>
|
||||
<p>What you’ll need:</p>
|
||||
<ul>
|
||||
|
|
@ -160,7 +160,7 @@ $ sudo systemctl start install_homeassistant.service
|
|||
<h3><a class="title-link" name="hassbian-config" href="#hassbian-config"></a> Hassbian-config</h3>
|
||||
<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 Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that’s used with Amazon Echo, Google Home and Mycroft.ai.</li>
|
||||
<li>Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.</li>
|
||||
<li>Install 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>
|
||||
|
|
@ -406,7 +406,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
|
|||
<p>I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.</p>
|
||||
<p>I 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>It may not look the way that I wanted it to initially, with beautiful native UI components, but that’s okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.</p>
|
||||
<p>Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.</p>
|
||||
<p>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>
|
||||
|
|
@ -489,7 +489,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
|
|||
<li>Dead line: April, 23 2017 - 23.59 UTC</li>
|
||||
<li>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>The decision of the jury will be final. If there will be a dispute then the Top-5 committer of the Home Assistant organization on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the <a href="https://community.home-assistant.io/c/contest-2017">Forum</a> and on <a href="https://twitter.com/home_assistant">Twitter</a>.</p>
|
||||
<p>Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.</p>
|
||||
</div>
|
||||
</article>
|
||||
|
|
@ -557,7 +557,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -721,7 +721,7 @@ On the close horizon from <a href="https://github.com/Landrash">@Landrash</a> th
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -184,7 +184,7 @@
|
|||
<li>Switch - Pilight: Implement echo config option (<a href="https://github.com/janLo">@janLo</a>)</li>
|
||||
<li>Core: Support customize in packages (<a href="https://github.com/kellerza">@kellerza</a>)</li>
|
||||
<li>Switch - Flux: Allow disabling setting the brightness (<a href="https://github.com/rytilahti">@rytilahti</a>)</li>
|
||||
<li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no emtpy image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Media player - Sonos: Add <code class="highlighter-rouge">is_coordinator</code>, set coordinator after join/unjoin, and no empty image (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/andrey-git">@andrey-git</a>, <a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Climate: Hold mode (<a href="https://github.com/Duoxilian">@Duoxilian</a>)</li>
|
||||
<li>Switch - TPlink: No longer doing I/O in event bus (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Light - Insteon local: Improve Insteon configuration (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li>
|
||||
|
|
@ -237,7 +237,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
@ -943,7 +943,7 @@ You have to note:
|
|||
<li><a href="/blog/categories/media/">Media</a></li>
|
||||
<li><a href="/blog/categories/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/organization/">Organization</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>
|
||||
|
|
|
|||
|
|
@ -79,7 +79,7 @@
|
|||
<span>
|
||||
<i class="icon-tags"></i>
|
||||
<ul class="tags unstyled">
|
||||
<li>Organisation</li>
|
||||
<li>Organization</li>
|
||||
</ul>
|
||||
</span>
|
||||
<a class='comments'
|
||||
|
|
@ -534,7 +534,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p>
|
||||
<p>Home Assistant will join this year for <a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a>, an event organized by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!</p>
|
||||
<p>Why contribute to Home Assistant:</p>
|
||||
<ul>
|
||||
<li>Written in Python3 with 94% test coverage</li>
|
||||
|
|
@ -735,9 +735,9 @@
|
|||
<h3><a class="title-link" name="climate-and--cover" href="#climate-and--cover"></a> Climate and cover</h3>
|
||||
<p>There are countless bugfixes included in this release which will make your experience with the <code class="highlighter-rouge">climate</code> and the <code class="highlighter-rouge">cover</code> platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to <a href="https://github.com/turbokongen">@turbokongen</a>, <a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/djbanks">@djbanks</a>, <a href="https://github.com/danielperna84">@danielperna84</a>, and others the improvements on the code and the frontend side is continuing…</p>
|
||||
<h3><a class="title-link" name="api-documentation" href="#api-documentation"></a> API documentation</h3>
|
||||
<p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p>
|
||||
<p>The <a href="https://dev-docs.home-assistant.io/en/dev/">Home Assistant API Documentation</a> is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.</p>
|
||||
<h3><a class="title-link" name="configuration-validation" href="#configuration-validation"></a> Configuration validation</h3>
|
||||
<p>The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p>
|
||||
<p>The validation of the configuration is still on-going. Approximately 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to <a href="https://github.com/kellerza">@kellerza</a>, <a href="https://github.com/fabaff">@fabaff</a>, <a href="https://github.com/Teagan42">@Teagan42</a>, and <a href="https://github.com/pvizeli">@pvizeli</a> for your effort!</p>
|
||||
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
|
||||
<p><img src="/images/supported_brands/xbox-live.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/automatic.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /><img src="/images/supported_brands/pi_hole.png" style="clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;" width="100" /></p>
|
||||
<ul>
|
||||
|
|
@ -1086,7 +1086,7 @@ Heatmap
|
|||
<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/organization/">Organization</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>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue