Site updated at 2017-10-07 22:49:55 UTC
This commit is contained in:
Travis CI
parent
f9a8fad682
commit
9ff55add23
128 changed files with 676 additions and 657 deletions
|
|
@ -88,7 +88,7 @@
|
|||
</header>
|
||||
<p>The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
|
||||
This article will try to explain how they all relate.</p>
|
||||
<p>The first thing to introduce is the <strong>Internet of Things</strong> (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.</p>
|
||||
<p>The first thing to introduce is the <strong>Internet of Things</strong> (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.</p>
|
||||
<p>There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a <strong>hub</strong>.</p>
|
||||
<p>As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers <strong>home control</strong>.</p>
|
||||
<p class="img">
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p>Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.</p>
|
||||
<p>The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.</p>
|
||||
<p>The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.</p>
|
||||
<p>Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.</p>
|
||||
<p>To enable the discovery component, add the following to your <code class="highlighter-rouge">home-assistant.conf</code>:</p>
|
||||
<div class="language-conf highlighter-rouge"><pre class="highlight"><code>[<span class="n">discovery</span>]
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@
|
|||
</a>
|
||||
</p>
|
||||
<p class="note">
|
||||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
|
||||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.
|
||||
</p>
|
||||
<a name="read-more"></a>
|
||||
<p>Tracking history is an exciting next step for Home Assistant and will power the next generation of features. Here a list of some of the cool things that can now be build:</p>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p>Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.</p>
|
||||
<p>A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.</p>
|
||||
<p>A new toggle has been added to the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.</p>
|
||||
<p class="img"><img src="/images/screenshots/streaming-updates.png" /></p>
|
||||
<a name="read-more"></a>
|
||||
<p>Streaming updates has been implemented using the HTML5 <code class="highlighter-rouge">EventSource</code> tag. Implementation is pretty straight forward as all the reconnection logic will be handled by the event source tag. The <a href="https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/api.py#L90">server-side code</a> is 50 lines and the <a href="https://github.com/home-assistant/home-assistant-js/blob/master/src/actions/stream.js">client-side code</a> is 80 lines of code.</p>
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>We discovered two issues annoying enough to warrent the release of 0.7.5:</p>
|
||||
<p>We discovered two issues annoying enough to warrant the release of 0.7.5:</p>
|
||||
<ul>
|
||||
<li>Home Assistant package did not include the CloudMQTT certificate.</li>
|
||||
<li>A bug in the core caused issues when some platforms are loaded twice.</li>
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p><img src="/images/supported_brands/influxdb.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" /><img src="/images/supported_brands/grafana.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" />
|
||||
The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time series database primarly designed to store sensor data and real-time analytics.</p>
|
||||
The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time series database primarily designed to store sensor data and real-time analytics.</p>
|
||||
<p>The <code class="highlighter-rouge">influxdb</code> component makes it possible to transfer all state changes from Home Assistant to an external <a href="https://influxdb.com/">InfluxDB</a> database.</p>
|
||||
<a name="read-more"></a>
|
||||
<p>The first step is to install the InfluxDB packages. If you are not running Fedora, check the <a href="https://influxdb.com/docs/v0.9/introduction/installation.html">installation</a> section for further details.</p>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p>Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.</p>
|
||||
<p>I would like to give a shout out to <a href="https://github.com/pavoni">Greg Dowling (@pavoni)</a> as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!</p>
|
||||
<p>I would like to give a shout out to <a href="https://github.com/pavoni">Greg Dowling (@pavoni)</a> as every release includes new work from him. He is constantly adding support for new platforms or improving the reliability of existing components and platforms. Keep up the good work!</p>
|
||||
<p>This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See <a href="/demo/">the demo</a> to see this in action and read more in the <a href="/components/group/">group documentation</a> how to get started.</p>
|
||||
<p class="img">
|
||||
<a href="/demo/"><img src="/images/blog/2016-01-release-12/views.png" /></a>
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@
|
|||
<span class="s">broker</span><span class="pi">:</span> <span class="s">localhost</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>Replace <code class="highlighter-rouge">localhost</code> with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path <code class="highlighter-rouge">smartthings/<Device Name>/<Atribute></code></p>
|
||||
<p>Replace <code class="highlighter-rouge">localhost</code> with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path <code class="highlighter-rouge">smartthings/<Device Name>/<Attribute></code></p>
|
||||
<p>For example, my Dimmer Z-Wave Lamp is called “Fireplace Lights” in SmartThings. The following topics are published:</p>
|
||||
<table>
|
||||
<thead>
|
||||
|
|
|
|||
|
|
@ -194,7 +194,7 @@
|
|||
<h3><a class="title-link" name="no-control-available" href="#no-control-available"></a> No control available</h3>
|
||||
<p>These devices are not able to be controlled. They will only offer state.</p>
|
||||
<h3><a class="title-link" name="poll-state-after-sending-command" href="#poll-state-after-sending-command"></a> Poll State after sending command</h3>
|
||||
<p>These devices will require the state to be polled after sending a command to see if a command was successfull.</p>
|
||||
<p>These devices will require the state to be polled after sending a command to see if a command was successful.</p>
|
||||
<p>Advantages:</p>
|
||||
<ul>
|
||||
<li>The state will be known right after the command was issued.</li>
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@
|
|||
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||||
<title>0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV - Home Assistant</title>
|
||||
<meta name="author" content="Paulus Schoutsen">
|
||||
<meta name="description" content="This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionaly was the Wink support improv...">
|
||||
<meta name="description" content="This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionally was the Wink support impro...">
|
||||
<meta name="viewport" content="width=device-width">
|
||||
<link rel="canonical" href="https://home-assistant.io/blog/2016/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/">
|
||||
<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/07/01/envisalink-homematic-hdmi-cec-and-sony-bravia-tv/">
|
||||
<meta property="og:type" content="article">
|
||||
<meta property="og:description" content="This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionaly was the Wink support improved and CherryPy is the new WSGI server.">
|
||||
<meta property="og:description" content="This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionally was the Wink support improved and CherryPy is the new WSGI server.">
|
||||
<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="0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV">
|
||||
<meta name="twitter:description" content="This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionaly was the Wink support improved and CherryPy is the new WSGI server.">
|
||||
<meta name="twitter:description" content="This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionally was the Wink support improved and CherryPy is the new WSGI server.">
|
||||
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
|
||||
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
|
||||
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ Leaving...
|
|||
</code></pre>
|
||||
</div>
|
||||
<p>Now reset the device. You should then be able to use the <a href="http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt">REPL (Read Evaluate Print Loop)</a>. On Linux there is <code class="highlighter-rouge">minicom</code> or <code class="highlighter-rouge">picocom</code>, on a Mac you can use <code class="highlighter-rouge">screen</code> (eg. <code class="highlighter-rouge">screen /dev/tty.SLAB_USBtoUART 115200</code>), and on Windows there is Putty to open a serial connection and get the REPL prompt.</p>
|
||||
<p>The <a href="http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi">WebREPL</a> work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at <a href="http://micropython.org/webrepl">http://micropython.org/webrepl</a>. Alternatively, you can create a local clone of their <a href="https://github.com/micropython/webrepl">GitHub repository</a>. This is neccessary if your want to use the command-line tool <code class="highlighter-rouge">webrepl_cli.py</code> which is mentionend later in this post.</p>
|
||||
<p>The <a href="http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi">WebREPL</a> work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at <a href="http://micropython.org/webrepl">http://micropython.org/webrepl</a>. Alternatively, you can create a local clone of their <a href="https://github.com/micropython/webrepl">GitHub repository</a>. This is necessary if your want to use the command-line tool <code class="highlighter-rouge">webrepl_cli.py</code> which is mentionend later in this post.</p>
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>sudo minicom -D /dev/ttyUSB0
|
||||
<span class="c">#4 ets_task(4020e374, 29, 3fff70e8, 10) </span>
|
||||
WebREPL daemon started on ws://192.168.4.1:8266
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@
|
|||
<li>Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened</li>
|
||||
<li>All the power of Python - use any of Python’s libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!</li>
|
||||
</ul>
|
||||
<p>It is in fact a testament to Home Assistant’s open nature that a component like <code class="highlighter-rouge">AppDaemon</code> can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant’s underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for <code class="highlighter-rouge">AppDaemon</code> - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additonal functions to make things that were already possible easier.</p>
|
||||
<p>It is in fact a testament to Home Assistant’s open nature that a component like <code class="highlighter-rouge">AppDaemon</code> can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant’s underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for <code class="highlighter-rouge">AppDaemon</code> - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additional functions to make things that were already possible easier.</p>
|
||||
<h2><a class="title-link" name="how-it-works" href="#how-it-works"></a> How it Works</h2>
|
||||
<p>The best way to show what <code class="highlighter-rouge">AppDaemon</code> does is through a few simple examples.</p>
|
||||
<h3><a class="title-link" name="sunrisesunset-lighting" href="#sunrisesunset-lighting"></a> Sunrise/Sunset Lighting</h3>
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@
|
|||
<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 whant 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 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>
|
||||
<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>
|
||||
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p>Yes, after only nine days comes 0.30. Don’t worry, we will try to keep our usual release cycle and not start to release every day.</p>
|
||||
<p>We guess that you already know: The <a href="/blog/2016/10/01/we-have-raspberry-image-now/">Raspberry Pi image</a> is available now. For Hassbian, <a href="https://github.com/Landrash">@Landrash</a> has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve <a href="https://community.home-assistant.io/c/installation/hassbian">feedback</a>, <a href="https://community.home-assistant.io/c/installation/hassbian">issue report</a>, and <a href="https://community.home-assistant.io/c/installation/hassbian">suggestions</a> to improve it.</p>
|
||||
<p>We guess that you already know: The <a href="/blog/2016/10/01/we-have-raspberry-image-now/">Raspberry Pi image</a> is available now. For Hassbian, <a href="https://github.com/Landrash">@Landrash</a> has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive <a href="https://community.home-assistant.io/c/installation/hassbian">feedback</a>, <a href="https://community.home-assistant.io/c/installation/hassbian">issue report</a>, and <a href="https://community.home-assistant.io/c/installation/hassbian">suggestions</a> to improve it.</p>
|
||||
<p>A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It’s a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.</p>
|
||||
<p>To reduce the run-time of your tests, <a href="https://github.com/balloob">@balloob</a> did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half.</p>
|
||||
<h3><a class="title-link" name="documentation" href="#documentation"></a> Documentation</h3>
|
||||
|
|
|
|||
|
|
@ -319,7 +319,7 @@
|
|||
<li>Weather: Allow tracking severe weather alerts with <a href="https://home-assistant.io/components/sensor.wunderground/">WUnderground</a> (<a href="https://github.com/tchellomello">@tchellomello</a>)</li>
|
||||
<li>Sensor: New support added to track <a href="https://home-assistant.io/components/sensor.min_max/">min/max/mean</a> (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
<li>Convert EntityComponent to be async (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Z-Wave: Add assocation service (<a href="https://github.com/turbokongen">@turbokongen</a>)</li>
|
||||
<li>Z-Wave: Add association service (<a href="https://github.com/turbokongen">@turbokongen</a>)</li>
|
||||
<li>Frontend - Services dev tool: persist state and tweak UI (<a href="https://github.com/justweb1">@justweb1</a>)</li>
|
||||
<li>Sensor: Support added for <a href="https://home-assistant.io/components/sensor.scrape/">scraping</a> websites (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
<li>Clean up of tests (<a href="https://github.com/capellini">@capellini</a>)</li>
|
||||
|
|
|
|||
|
|
@ -183,7 +183,7 @@
|
|||
<li>Fix InfluxDB without authentication (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix Kodi without authentication (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix incorrect caching of /api/error_log (<a href="https://github.com/armills">@armills</a>)</li>
|
||||
<li>Fix incorrect ordering of service calls which could cause delays inbetween turning on multiple entities (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix incorrect ordering of service calls which could cause delays between turning on multiple entities (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix Nest Climate temperature issues (<a href="https://github.com/technicalpickles">@technicalpickles</a>)</li>
|
||||
</ul>
|
||||
<h3><a class="title-link" name="release-0345---december-12" href="#release-0345---december-12"></a> Release 0.34.5 - December 12</h3>
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<p>A year ago <a href="https://home-assistant.io/blog/2015/12/22/amazon-echo-icloud-and-templates/">Home Assistant 0.10</a> landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that’s more than 7 a day!</p>
|
||||
<p>One of the things that Jon Walker, the founder of the company I work for (<a href="http://www.appfolioinc.com/">AppFolio</a>), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Everytime you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.</p>
|
||||
<p>One of the things that Jon Walker, the founder of the company I work for (<a href="http://www.appfolioinc.com/">AppFolio</a>), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.</p>
|
||||
<p>That’s why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it’s clear when things go out and people are not afraid to miss a release.</p>
|
||||
<p>However, being on a two week release cycle also means that the community has to rally each two weeks to make sure everything is ready to go. A lot of people are involved in making sure that all pieces are in place, to all of those: thank you! Thank you for all the time and effort you put in to make Home Assistant the best home automation software out there.</p>
|
||||
<p>Another big thanks goes out to the developers of the Python language and all the open source libraries and tools that Home Assistant depends on. Making quality software is not a small feat and all of you can be proud of yourself.</p>
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@
|
|||
</header>
|
||||
<p>Hello and Happy New Year!</p>
|
||||
<p>I am not Paulus. My name is Ben. I’m the creator of the <a href="https://www.youtube.com/channel/UCLecVrux63S6aYiErxdiy4w">BRUH Automation YouTube channel</a>. If you’ve ever seen any of my videos then you’ll know I love home automation and Home Assistant.</p>
|
||||
<p>I wanted to share some exciting stats from one of my latest projects - <a href="https://github.com/bruhautomation/BRUH-Christmas-Tree-2016">Control My Christmas tree!</a> For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.</p>
|
||||
<p>I wanted to share some exciting stats from one of my latest projects - <a href="https://github.com/bruhautomation/BRUH-Christmas-Tree-2016">Control My Christmas tree!</a> For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publicly accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.</p>
|
||||
<p>I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!</p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2017-01-bruh-christmas/christmas-tree.gif" />
|
||||
|
|
|
|||
|
|
@ -165,7 +165,7 @@
|
|||
<li>Light - tellstick.py: Tellstick light fix (<a href="https://github.com/stefan-jonasson">@stefan-jonasson</a>)</li>
|
||||
<li>Switch - insteon_local.py: only check for devices when not defined in config (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li>
|
||||
<li>Notify - Twitter: Allow direct messaging to user (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
<li>Fan - MQTT: Dont set a speed when fan turns on (<a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Fan - MQTT: Don’t set a speed when fan turns on (<a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Config: Allow easier customization of whole domain, entity lists, globs (<a href="https://github.com/andrey-git">@andrey-git</a>)</li>
|
||||
<li>Sensor - Homematic: Update device support (<a href="https://github.com/danielperna84">@danielperna84</a>)</li>
|
||||
<li>Binary sensor - ISS: Add location to attributes and option to show position on the map (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.</p>
|
||||
<p>One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assistant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.</p>
|
||||
<p>Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.</p>
|
||||
<a name="read-more"></a>
|
||||
<h3><a class="title-link" name="setup" href="#setup"></a> Setup</h3>
|
||||
|
|
|
|||
|
|
@ -240,7 +240,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
|
|||
<li>twilio component (<a href="https://github.com/happyleavesaoc">@happyleavesaoc</a>)</li>
|
||||
<li>Add Z-Wave battery level as a sensor. (<a href="https://github.com/andrey-git">@andrey-git</a>)</li>
|
||||
<li>OwnTrack Async (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
|
||||
<li>Fix possibility that have multible topic subscribe mqtt (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
|
||||
<li>Fix possibility that have multiple topic subscribe mqtt (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
|
||||
<li>Migrate mqtt tracker and arwn sensor to async / cleanup owntrack (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
|
||||
<li>Z-Wave prevent I/O event loop (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Update pwaqi to 3.0 to use public API (<a href="https://github.com/valentinalexeev">@valentinalexeev</a>)</li>
|
||||
|
|
@ -290,7 +290,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
|
|||
<li>Allow configurable conditions for Pi-Hole sensor (<a href="https://github.com/colinodell">@colinodell</a>)</li>
|
||||
<li>Improved iCloud 2FA support. (<a href="https://github.com/reedriley">@reedriley</a>)</li>
|
||||
<li>Update pymyq requirement (<a href="https://github.com/arraylabs">@arraylabs</a>)</li>
|
||||
<li>Not always asume manufacturername is present (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Not always assume manufacturername is present (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Add first pass at Z-Wave light tests (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Bugfix mqtt socket memory error (<a href="https://github.com/pvizeli">@pvizeli</a>)</li>
|
||||
<li>Increase upper limit on light transitions (<a href="https://github.com/amelchio">@amelchio</a>)</li>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>The idea of creating <a href="https://github.com/petkov/http_to_mqtt">HTTP to MQTT bridge</a> appeared when I was trying to integrate Google Assistant with my Home Assistant after watching <a href="https://youtu.be/087tQ7Ly7f4?t=265">BRUH Automation</a> video. Right now there is no MQTT service available in <a href="https://ifttt.com/about">IFTTT</a>. Existing integration solution uses <a href="https://ifttt.com/maker_webhooks">Maker Webhooks</a> which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.</p>
|
||||
<p>The idea of creating <a href="https://github.com/petkov/http_to_mqtt">HTTP to MQTT bridge</a> appeared when I was trying to integrate Google Assistant with my Home Assistant after watching <a href="https://youtu.be/087tQ7Ly7f4?t=265">BRUH Automation</a> video. Right now there is no MQTT service available in <a href="https://ifttt.com/about">IFTTT</a>. Existing integration solution uses <a href="https://ifttt.com/maker_webhooks">Maker Webhooks</a> which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.</p>
|
||||
<p>The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with <a href="https://expressjs.com/">Express</a> for the server part and <a href="https://www.npmjs.com/package/mqtt">MQTT.js</a> for the client.</p>
|
||||
<a name="read-more"></a>
|
||||
<p>The app could be hosted on any Node.js hosting. I prefer <a href="https://www.heroku.com/home">Heroku: Cloud Application Platform</a> for its simplicity.</p>
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@
|
|||
>Comments</a>
|
||||
</div>
|
||||
</header>
|
||||
<p>You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the <a href="https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/">Thomas-Krenn-Award</a> put us on the 2nd place. This is an awesome achievment for an independent community project.</p>
|
||||
<p>You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the <a href="https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/">Thomas-Krenn-Award</a> put us on the 2nd place. This is an awesome achievement for an independent community project.</p>
|
||||
<p>I would like to thanks all contributors. Your endless effort made this possible.</p>
|
||||
<p><img src="/images/blog/2017-04-award/award.jpg" style="border: 0;box-shadow: none;" /></p>
|
||||
<p>The prize beside the very nice trophy contains hardware and we want to give that hardware partically away. We won four <a href="https://www.thomas-krenn.com/en/products/low-energy-systems/les-v2.html">Low Energy Server v2 (LES)</a> units with an Intel Celeron N2930, 8 GB of RAM, and a mSATA of 128 GB (one unit with 64 GB). We were thinking about to keep one of those units in Europe and one in North America for testing and to use during workshops and events. But the other two will go to interested parties.</p>
|
||||
|
|
|
|||
|
|
@ -208,7 +208,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
|
|||
<li>Upgrade sendgrid to 4.0.0 (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7038">#7038</a>) (<a href="/components/notify.sendgrid/">notify.sendgrid docs</a>)</li>
|
||||
<li>Missing line name restriction added (fixes #7039) (<a href="https://github.com/DavidMStraub">@DavidMStraub</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7040">#7040</a>) (<a href="/components/sensor.mvglive/">sensor.mvglive docs</a>)</li>
|
||||
<li>Plug file leak on LIFX unregister (<a href="https://github.com/amelchio">@amelchio</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7031">#7031</a>) (<a href="/components/light.lifx/">light.lifx docs</a>)</li>
|
||||
<li>Make core to look avilable state of device on servicecall (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7045">#7045</a>)</li>
|
||||
<li>Make core to look available state of device on servicecall (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7045">#7045</a>)</li>
|
||||
<li>Remove configuration sample (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7048">#7048</a>)</li>
|
||||
<li>Bugfix wait on start event (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7013">#7013</a>)</li>
|
||||
<li>Bugfix slider (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7047">#7047</a>) (<a href="/components/input_slider/">input_slider docs</a>)</li>
|
||||
|
|
@ -271,7 +271,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
|
|||
<li>Value of 0 should not be considered <code class="highlighter-rouge">unknown</code>. (<a href="https://github.com/aequitas">@aequitas</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7139">#7139</a>)</li>
|
||||
<li>Upgrade netdisco (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7171">#7171</a>)</li>
|
||||
<li>Added new services to platform kodi (<a href="https://github.com/alexmogavero">@alexmogavero</a> - <a href="https://github.com/home-assistant/home-assistant/pull/6426">#6426</a>) (<a href="/components/media_player/">media_player docs</a>) (<a href="/components/media_player.kodi/">media_player.kodi docs</a>)</li>
|
||||
<li>Supress trackback and upgrade PyMata to 2.14 (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7176">#7176</a>) (<a href="/components/arduino/">arduino docs</a>)</li>
|
||||
<li>Suppress trackback and upgrade PyMata to 2.14 (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7176">#7176</a>) (<a href="/components/arduino/">arduino docs</a>)</li>
|
||||
<li>Disable invalid-sequence-index (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7177">#7177</a>)</li>
|
||||
<li>Upgrade mypy to 0.501 (was renamed from mypy-lang) (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7117">#7117</a>)</li>
|
||||
<li>Add condition for API failure (<a href="https://github.com/sytone">@sytone</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7181">#7181</a>)</li>
|
||||
|
|
|
|||
|
|
@ -218,7 +218,7 @@
|
|||
<li>Use expected behvaior for above/below (<a href="https://github.com/armills">@armills</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7857">#7857</a>) (breaking change)</li>
|
||||
<li>log time delay of domain setup in info level (<a href="https://github.com/azogue">@azogue</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7808">#7808</a>)</li>
|
||||
<li>Optimize history_stats efficiency and database usage (<a href="https://github.com/bokub">@bokub</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7858">#7858</a>) (<a href="https://home-assistant.io/components/sensor.history_stats/">sensor.history_stats docs</a>)</li>
|
||||
<li>dont use default for switch name, so that the object id is used (<a href="https://github.com/abmantis">@abmantis</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7845">#7845</a>) (<a href="https://home-assistant.io/components/switch.broadlink/">switch.broadlink docs</a>) (breaking change)</li>
|
||||
<li>don’t use default for switch name, so that the object id is used (<a href="https://github.com/abmantis">@abmantis</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7845">#7845</a>) (<a href="https://home-assistant.io/components/switch.broadlink/">switch.broadlink docs</a>) (breaking change)</li>
|
||||
<li>Disallow ambiguous color descriptors in the light.turn_on schema (<a href="https://github.com/amelchio">@amelchio</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7765">#7765</a>) (breaking change)</li>
|
||||
<li>Make monkey patch work in Python 3.6 (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7848">#7848</a>)</li>
|
||||
<li>fix permissions issue for Insteon Local #6558 (<a href="https://github.com/wardcraigj">@wardcraigj</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7860">#7860</a>) (<a href="https://home-assistant.io/components/insteon_local/">insteon_local docs</a>)</li>
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@
|
|||
<li>Fix TP-Link light brightness issue #8744. (<a href="https://github.com/gollo">@gollo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8755">#8755</a>)</li>
|
||||
<li>Fix typo in script error (<a href="https://github.com/n8henrie">@n8henrie</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8754">#8754</a>)</li>
|
||||
<li>Fix tradfri error spam (<a href="https://github.com/MartinHjelmare">@MartinHjelmare</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8738">#8738</a>) (<a href="https://home-assistant.io/components/light.tradfri/">light.tradfri docs</a>)</li>
|
||||
<li>Media Player - Pioneer: Supress exception if host is not available (fixes #8684) (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8732">#8732</a>) (<a href="https://home-assistant.io/components/media_player.pioneer/">media_player.pioneer docs</a>)</li>
|
||||
<li>Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8732">#8732</a>) (<a href="https://home-assistant.io/components/media_player.pioneer/">media_player.pioneer docs</a>)</li>
|
||||
<li>Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again (<a href="https://github.com/azogue">@azogue</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8716">#8716</a>) (<a href="https://home-assistant.io/components/telegram_bot.webhooks/">telegram_bot.webhooks docs</a>)</li>
|
||||
<li>Fixed sensor issue with Google Wifi routers in bridge mode (<a href="https://github.com/fronzbot">@fronzbot</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8710">#8710</a>) (<a href="https://home-assistant.io/components/sensor.google_wifi/">sensor.google_wifi docs</a>)</li>
|
||||
<li>Fix alexa cards (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8708">#8708</a>) (<a href="https://home-assistant.io/components/alexa/">alexa docs</a>)</li>
|
||||
|
|
|
|||
|
|
@ -214,7 +214,7 @@ Screenshot of the new customize editor.
|
|||
<li>Skip automatic events older than latest data (<a href="https://github.com/armills">@armills</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9230">#9230</a>) (<a href="https://home-assistant.io/components/device_tracker.automatic/">device_tracker.automatic docs</a>)</li>
|
||||
<li>title and message was swapped in pushbullet (<a href="https://github.com/danielhiversen">@danielhiversen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9241">#9241</a>) (<a href="https://home-assistant.io/components/notify.pushbullet/">notify.pushbullet docs</a>)</li>
|
||||
<li>Fix possible KeyError (<a href="https://github.com/MartinHjelmare">@MartinHjelmare</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9242">#9242</a>) (<a href="https://home-assistant.io/components/mysensors/">mysensors docs</a>)</li>
|
||||
<li>WIP: Homematic improvments with new hass interfaces (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9058">#9058</a>) (<a href="https://home-assistant.io/components/homematic/">homematic docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.homematic/">binary_sensor.homematic docs</a>) (<a href="https://home-assistant.io/components/climate.homematic/">climate.homematic docs</a>) (<a href="https://home-assistant.io/components/cover.homematic/">cover.homematic docs</a>) (<a href="https://home-assistant.io/components/light.homematic/">light.homematic docs</a>) (<a href="https://home-assistant.io/components/sensor.homematic/">sensor.homematic docs</a>) (<a href="https://home-assistant.io/components/switch.homematic/">switch.homematic docs</a>) (breaking change)</li>
|
||||
<li>WIP: Homematic improvements with new hass interfaces (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9058">#9058</a>) (<a href="https://home-assistant.io/components/homematic/">homematic docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.homematic/">binary_sensor.homematic docs</a>) (<a href="https://home-assistant.io/components/climate.homematic/">climate.homematic docs</a>) (<a href="https://home-assistant.io/components/cover.homematic/">cover.homematic docs</a>) (<a href="https://home-assistant.io/components/light.homematic/">light.homematic docs</a>) (<a href="https://home-assistant.io/components/sensor.homematic/">sensor.homematic docs</a>) (<a href="https://home-assistant.io/components/switch.homematic/">switch.homematic docs</a>) (breaking change)</li>
|
||||
<li>Add available to sonos (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9243">#9243</a>) (<a href="https://home-assistant.io/components/media_player.sonos/">media_player.sonos docs</a>)</li>
|
||||
<li>Make sure Ring binary_sensor state will update only if device_id matches (<a href="https://github.com/tchellomello">@tchellomello</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9247">#9247</a>) (<a href="https://home-assistant.io/components/binary_sensor.ring/">binary_sensor.ring docs</a>)</li>
|
||||
<li>
|
||||
|
|
|
|||
|
|
@ -152,7 +152,7 @@
|
|||
<li>Clean up OwnTracks (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9569">#9569</a>) (<a href="https://home-assistant.io/components/device_tracker.owntracks/">device_tracker.owntracks docs</a>)</li>
|
||||
<li>MQTT Cover: Add availability topic and configurable payloads (<a href="https://github.com/marthoc">@marthoc</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9445">#9445</a>) (<a href="https://home-assistant.io/components/cover.mqtt/">cover.mqtt docs</a>)</li>
|
||||
<li>Upgrade dsmr_parser to 0.11 (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9576">#9576</a>) (<a href="https://home-assistant.io/components/sensor.dsmr/">sensor.dsmr docs</a>)</li>
|
||||
<li>Added new statistic attributes (<a href="https://github.com/sti0">@sti0</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9433">#9433</a>) (<a href="https://home-assistant.io/components/vacuum.xiaomi/">vacuum.xiaomi docs</a>)</li>
|
||||
<li>Added new statistic attributes (<a href="https://github.com/sti0">@sti0</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9433">#9433</a>) (<a href="https://home-assistant.io/components/vacuum.xiaomi_miio/">vacuum.xiaomi docs</a>)</li>
|
||||
<li>Upgrade youtube_dl to 2017.9.24 (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9575">#9575</a>) (<a href="https://home-assistant.io/components/media_extractor/">media_extractor docs</a>)</li>
|
||||
<li>Upgrade lyft_rides to 0.2 (<a href="https://github.com/enriquegh">@enriquegh</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9578">#9578</a>) (<a href="https://home-assistant.io/components/sensor.lyft/">sensor.lyft docs</a>)</li>
|
||||
<li>Increase Comed timeout since it sometimes takes a long time for the API to respond (<a href="https://github.com/joe248">@joe248</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9536">#9536</a>) (<a href="https://home-assistant.io/components/sensor.comed_hourly_pricing/">sensor.comed_hourly_pricing docs</a>)</li>
|
||||
|
|
@ -168,7 +168,7 @@
|
|||
<li>Add OwnTracks over HTTP (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9582">#9582</a>) (<a href="https://home-assistant.io/components/http/">http docs</a>) (<a href="https://home-assistant.io/components/device_tracker.owntracks/">device_tracker.owntracks docs</a>) (<a href="https://home-assistant.io/components/device_tracker.owntracks_http/">device_tracker.owntracks_http docs</a>) (new-platform)</li>
|
||||
<li>upgrade python-ecobee-api (<a href="https://github.com/nkgilley">@nkgilley</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9612">#9612</a>) (<a href="https://home-assistant.io/components/ecobee/">ecobee docs</a>)</li>
|
||||
<li>Change TP-Link Switch power statistics attribute names (<a href="https://github.com/djchen">@djchen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9607">#9607</a>) (<a href="https://home-assistant.io/components/switch.tplink/">switch.tplink docs</a>) (breaking change)</li>
|
||||
<li>Migrate Alexa smart home to registry (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9616">#9616</a>) (<a href="https://home-assistant.io/components/alexa.smart_home/">alexa.smart_home docs</a>)</li>
|
||||
<li>Migrate Alexa smart home to registry (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9616">#9616</a>) (<a href="https://home-assistant.io/components/alexa/">alexa.smart_home docs</a>)</li>
|
||||
<li>Add an input_datetime (<a href="https://github.com/tinloaf">@tinloaf</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9313">#9313</a>) (<a href="https://home-assistant.io/components/input_datetime/">input_datetime docs</a>) (new-platform)</li>
|
||||
<li>Cover component for RFlink (<a href="https://github.com/passie">@passie</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9432">#9432</a>) (<a href="https://home-assistant.io/components/rflink/">rflink docs</a>) (<a href="https://home-assistant.io/components/cover.rflink/">cover.rflink docs</a>) (new-platform)</li>
|
||||
<li>Introducing support to Melnor RainCloud sprinkler systems (<a href="https://github.com/tchellomello">@tchellomello</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9287">#9287</a>) (<a href="https://home-assistant.io/components/raincloud/">raincloud docs</a>) (<a href="https://home-assistant.io/components/binary_sensor.raincloud/">binary_sensor.raincloud docs</a>) (<a href="https://home-assistant.io/components/sensor.raincloud/">sensor.raincloud docs</a>) (<a href="https://home-assistant.io/components/switch.raincloud/">switch.raincloud docs</a>) (new-platform)</li>
|
||||
|
|
@ -196,23 +196,23 @@
|
|||
<li>Upgrade googlemaps to 2.5.1 (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9653">#9653</a>) (<a href="https://home-assistant.io/components/sensor.google_travel_time/">sensor.google_travel_time docs</a>)</li>
|
||||
<li>mqtt_statestream: Add options to publish attributes/timestamps (<a href="https://github.com/mw-white">@mw-white</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9645">#9645</a>) (<a href="https://home-assistant.io/components/mqtt_statestream/">mqtt_statestream docs</a>)</li>
|
||||
<li>Fixed bugs related to exception handling in pythonegardia. Updating package requirement accordingly (<a href="https://github.com/jeroenterheerdt">@jeroenterheerdt</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9663">#9663</a>) (<a href="https://home-assistant.io/components/alarm_control_panel.egardia/">alarm_control_panel.egardia docs</a>)</li>
|
||||
<li>Update google-api-python-client to 1.6.4 (<a href="https://github.com/arsaboo">@arsaboo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9658">#9658</a>) (<a href="https://home-assistant.io/components/google/">google docs</a>)</li>
|
||||
<li>Update google-api-python-client to 1.6.4 (<a href="https://github.com/arsaboo">@arsaboo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9658">#9658</a>) (<a href="https://home-assistant.io/components/calendar.google/">google docs</a>)</li>
|
||||
<li>Bump abode to 0.11.9 (<a href="https://github.com/MisterWil">@MisterWil</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9660">#9660</a>) (<a href="https://home-assistant.io/components/abode/">abode docs</a>)</li>
|
||||
<li>Unit tests to improve core coverage (<a href="https://github.com/armills">@armills</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9659">#9659</a>)</li>
|
||||
<li>Upgrade pyitachip2ir to 0.0.7 (<a href="https://github.com/alanfischer">@alanfischer</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9669">#9669</a>) (<a href="https://home-assistant.io/components/remote.itach/">remote.itach docs</a>)</li>
|
||||
<li>Fix typo in cancel_command description (<a href="https://github.com/FletcherAU">@FletcherAU</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9671">#9671</a>)</li>
|
||||
<li>Rename input_slider to input_number and add numeric text box option (<a href="https://github.com/BioSehnsucht">@BioSehnsucht</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9494">#9494</a>) (<a href="https://home-assistant.io/components/demo/">demo docs</a>) (<a href="https://home-assistant.io/components/input_number/">input_number docs</a>) (breaking change)</li>
|
||||
<li>Properly handle an invalid end_time (<a href="https://github.com/alanfischer">@alanfischer</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9675">#9675</a>) (<a href="https://home-assistant.io/components/history/">history docs</a>)</li>
|
||||
<li>Support new feature to push API data to hassio (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9679">#9679</a>) (<a href="https://home-assistant.io/components/hassio/">hassio docs</a>)</li>
|
||||
<li>Support new feature to push API data to hassio (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9679">#9679</a>) (<a href="https://home-assistant.io/hassio/">hassio docs</a>)</li>
|
||||
<li>Adding ignore capability to Egardia component (<a href="https://github.com/jeroenterheerdt">@jeroenterheerdt</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9676">#9676</a>) (<a href="https://home-assistant.io/components/alarm_control_panel.egardia/">alarm_control_panel.egardia docs</a>)</li>
|
||||
<li>Fix Google Calendar/oauth2client warning (<a href="https://github.com/mbrrg">@mbrrg</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9677">#9677</a>) (<a href="https://home-assistant.io/components/google/">google docs</a>)</li>
|
||||
<li>Fix Google Calendar/oauth2client warning (<a href="https://github.com/mbrrg">@mbrrg</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9677">#9677</a>) (<a href="https://home-assistant.io/components/calendar.google/">google docs</a>)</li>
|
||||
<li>Implement DSMR5 support. (<a href="https://github.com/aequitas">@aequitas</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9686">#9686</a>) (<a href="https://home-assistant.io/components/sensor.dsmr/">sensor.dsmr docs</a>)</li>
|
||||
<li>Add Tibber sensor (<a href="https://github.com/danielhiversen">@danielhiversen</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9661">#9661</a>) (<a href="https://home-assistant.io/components/sensor.tibber/">sensor.tibber docs</a>) (new-platform)</li>
|
||||
<li>Add recorder purge service, rework purge timer (<a href="https://github.com/milanvo">@milanvo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9523">#9523</a>) (breaking change)</li>
|
||||
<li>Fix restore state by filter out null value row from DB query (<a href="https://github.com/milanvo">@milanvo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9690">#9690</a>) (<a href="https://home-assistant.io/components/history/">history docs</a>)</li>
|
||||
<li>Updating clicksendaudio component based on feedback (<a href="https://github.com/jeroenterheerdt">@jeroenterheerdt</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9692">#9692</a>) (<a href="https://home-assistant.io/components/notify.clicksendaudio/">notify.clicksendaudio docs</a>) (new-platform)</li>
|
||||
<li>Refactoring of onewire sensor component (<a href="https://github.com/bestlibre">@bestlibre</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9691">#9691</a>) (<a href="https://home-assistant.io/components/sensor.onewire/">sensor.onewire docs</a>)</li>
|
||||
<li>HassIO replace config changes (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9695">#9695</a>) (<a href="https://home-assistant.io/components/hassio/">hassio docs</a>)</li>
|
||||
<li>HassIO replace config changes (<a href="https://github.com/pvizeli">@pvizeli</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9695">#9695</a>) (<a href="https://home-assistant.io/hassio/">hassio docs</a>)</li>
|
||||
<li>Fixed typo in opencv (<a href="https://github.com/arsaboo">@arsaboo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9697">#9697</a>) (<a href="https://home-assistant.io/components/image_processing.opencv/">image_processing.opencv docs</a>) (breaking change)</li>
|
||||
<li>[light.tradfri] async support with resource observation. (<a href="https://github.com/lwis">@lwis</a> - <a href="https://github.com/home-assistant/home-assistant/pull/7815">#7815</a>) (<a href="https://home-assistant.io/components/tradfri/">tradfri docs</a>) (<a href="https://home-assistant.io/components/light.tradfri/">light.tradfri docs</a>) (breaking change)</li>
|
||||
<li>Create secrets file in default config (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/9685">#9685</a>)</li>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -151,7 +151,7 @@ Leaving...
|
|||
|
||||
Now reset the device. You should then be able to use the [REPL (Read Evaluate Print Loop)](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt). On Linux there is `minicom` or `picocom`, on a Mac you can use `screen` (eg. `screen /dev/tty.SLAB_USBtoUART 115200`), and on Windows there is Putty to open a serial connection and get the REPL prompt.
|
||||
|
||||
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is neccessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
|
||||
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is necessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
|
||||
|
||||
```bash
|
||||
$ sudo minicom -D /dev/ttyUSB0
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -315,7 +315,7 @@ Instead of running [InfluxDB](https://www.influxdata.com/) and Grafana on a Rasp
|
|||
<link href="https://home-assistant.io/blog/2017/03/28/http-to-mqtt-bridge/"/>
|
||||
<updated>2017-03-28T06:00:00+00:00</updated>
|
||||
<id>https://home-assistant.io/blog/2017/03/28/http-to-mqtt-bridge</id>
|
||||
<content type="html">< appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.
|
||||
<content type="html">< appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.
|
||||
|
||||
The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with [Express](https://expressjs.com/) for the server part and [MQTT.js](https://www.npmjs.com/package/mqtt) for the client.
|
||||
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -309,7 +309,7 @@ Controlling a device can, just like state, be done through cloud and/or local co
|
|||
These devices are not able to be controlled. They will only offer state.
|
||||
|
||||
### <a class='title-link' name='poll-state-after-sending-command' href='#poll-state-after-sending-command'></a> Poll State after sending command
|
||||
These devices will require the state to be polled after sending a command to see if a command was successfull.
|
||||
These devices will require the state to be polled after sending a command to see if a command was successful.
|
||||
|
||||
Advantages:
|
||||
|
||||
|
|
@ -392,7 +392,7 @@ When this happens, your house should be able to keep functioning. The cloud shou
|
|||
<content type="html"><![CDATA[The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
|
||||
This article will try to explain how they all relate.
|
||||
|
||||
The first thing to introduce is the **Internet of Things** (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.
|
||||
The first thing to introduce is the **Internet of Things** (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.
|
||||
|
||||
There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a **hub**.
|
||||
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -168,7 +168,7 @@ Leaving...
|
|||
|
||||
Now reset the device. You should then be able to use the [REPL (Read Evaluate Print Loop)](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt). On Linux there is `minicom` or `picocom`, on a Mac you can use `screen` (eg. `screen /dev/tty.SLAB_USBtoUART 115200`), and on Windows there is Putty to open a serial connection and get the REPL prompt.
|
||||
|
||||
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is neccessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
|
||||
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is necessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
|
||||
|
||||
```bash
|
||||
$ sudo minicom -D /dev/ttyUSB0
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -220,7 +220,7 @@ mqtt:
|
|||
broker: localhost
|
||||
```
|
||||
|
||||
Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings/<Device Name>/<Atribute>`
|
||||
Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings/<Device Name>/<Attribute>`
|
||||
|
||||
For example, my Dimmer Z-Wave Lamp is called "Fireplace Lights" in SmartThings. The following topics are published:
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
<title><![CDATA[Category: Organisation | Home Assistant]]></title>
|
||||
<link href="https://home-assistant.io/blog/categories/organisation/atom.xml" rel="self"/>
|
||||
<link href="https://home-assistant.io/"/>
|
||||
<updated>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
@ -305,7 +305,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
[abode docs]: https://home-assistant.io/components/abode/
|
||||
[alarm_control_panel.egardia docs]: https://home-assistant.io/components/alarm_control_panel.egardia/
|
||||
[alarm_control_panel.manual_mqtt docs]: https://home-assistant.io/components/alarm_control_panel.manual_mqtt/
|
||||
[alexa.smart_home docs]: https://home-assistant.io/components/alexa.smart_home/
|
||||
[alexa.smart_home docs]: https://home-assistant.io/components/alexa/
|
||||
[apple_tv docs]: https://home-assistant.io/components/apple_tv/
|
||||
[arlo docs]: https://home-assistant.io/components/arlo/
|
||||
[binary_sensor.raincloud docs]: https://home-assistant.io/components/binary_sensor.raincloud/
|
||||
|
|
@ -324,9 +324,9 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
[duckdns docs]: https://home-assistant.io/components/duckdns/
|
||||
[ecobee docs]: https://home-assistant.io/components/ecobee/
|
||||
[emulated_hue docs]: https://home-assistant.io/components/emulated_hue/
|
||||
[google docs]: https://home-assistant.io/components/google/
|
||||
[google docs]: https://home-assistant.io/components/calendar.google/
|
||||
[group docs]: https://home-assistant.io/components/group/
|
||||
[hassio docs]: https://home-assistant.io/components/hassio/
|
||||
[hassio docs]: https://home-assistant.io/hassio/
|
||||
[history docs]: https://home-assistant.io/components/history/
|
||||
[homematic docs]: https://home-assistant.io/components/homematic/
|
||||
[http docs]: https://home-assistant.io/components/http/
|
||||
|
|
@ -381,7 +381,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
[tradfri docs]: https://home-assistant.io/components/tradfri/
|
||||
[upnp docs]: https://home-assistant.io/components/upnp/
|
||||
[usps docs]: https://home-assistant.io/components/usps/
|
||||
[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi/
|
||||
[vacuum.xiaomi docs]: https://home-assistant.io/components/vacuum.xiaomi_miio/
|
||||
[wink docs]: https://home-assistant.io/components/wink/
|
||||
[zwave docs]: https://home-assistant.io/components/zwave/
|
||||
[forum]: https://community.home-assistant.io/
|
||||
|
|
@ -889,7 +889,7 @@ frontend:
|
|||
- Skip automatic events older than latest data ([@armills] - [#9230]) ([device_tracker.automatic docs])
|
||||
- title and message was swapped in pushbullet ([@danielhiversen] - [#9241]) ([notify.pushbullet docs])
|
||||
- Fix possible KeyError ([@MartinHjelmare] - [#9242]) ([mysensors docs])
|
||||
- WIP: Homematic improvments with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change)
|
||||
- WIP: Homematic improvements with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change)
|
||||
- Add available to sonos ([@pvizeli] - [#9243]) ([media_player.sonos docs])
|
||||
- Make sure Ring binary_sensor state will update only if device_id matches ([@tchellomello] - [#9247]) ([binary_sensor.ring docs])
|
||||
- Added configurable timeout for receiver HTTP requests | Additional AV… ([@scarface-4711] - [#9244]) ([media_player.denonavr docs])
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+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>2017-10-07T22:15:46+00:00</updated>
|
||||
<updated>2017-10-07T22:42:05+00:00</updated>
|
||||
<id>https://home-assistant.io/</id>
|
||||
<author>
|
||||
<name><![CDATA[Home Assistant]]></name>
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.</p>
|
||||
<p>I would like to give a shout out to <a href="https://github.com/pavoni">Greg Dowling (@pavoni)</a> as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!</p>
|
||||
<p>I would like to give a shout out to <a href="https://github.com/pavoni">Greg Dowling (@pavoni)</a> as every release includes new work from him. He is constantly adding support for new platforms or improving the reliability of existing components and platforms. Keep up the good work!</p>
|
||||
<p>This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See <a href="/demo/">the demo</a> to see this in action and read more in the <a href="/components/group/">group documentation</a> how to get started.</p>
|
||||
<p class="img">
|
||||
<a href="/demo/"><img src="/images/blog/2016-01-release-12/views.png" /></a>
|
||||
|
|
@ -368,7 +368,7 @@ In this tutorial I will explain how you can activate Tasker tasks from Home Assi
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p><img src="/images/supported_brands/influxdb.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" /><img src="/images/supported_brands/grafana.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" />
|
||||
The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time series database primarly designed to store sensor data and real-time analytics.</p>
|
||||
The <a href="https://influxdb.com/">InfluxDB</a> database is a so-called time series database primarily designed to store sensor data and real-time analytics.</p>
|
||||
<p>The <code class="highlighter-rouge">influxdb</code> component makes it possible to transfer all state changes from Home Assistant to an external <a href="https://influxdb.com/">InfluxDB</a> database.</p>
|
||||
<a class="btn pull-right" href="/blog/2015/12/07/influxdb-and-grafana/#read-more">Read on →</a>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -252,7 +252,7 @@ Home Assistant will keep track of historical values and allow you to integrate i
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>We discovered two issues annoying enough to warrent the release of 0.7.5:</p>
|
||||
<p>We discovered two issues annoying enough to warrant the release of 0.7.5:</p>
|
||||
<ul>
|
||||
<li>Home Assistant package did not include the CloudMQTT certificate.</li>
|
||||
<li>A bug in the core caused issues when some platforms are loaded twice.</li>
|
||||
|
|
|
|||
|
|
@ -202,7 +202,7 @@ The old logo, the new detailed logo and the new simple logo.
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.</p>
|
||||
<p>A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.</p>
|
||||
<p>A new toggle has been added to the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.</p>
|
||||
<p class="img"><img src="/images/screenshots/streaming-updates.png" /></p>
|
||||
<a class="btn pull-right" href="/blog/2015/02/24/streaming-updates/#read-more">Read on →</a>
|
||||
</div>
|
||||
|
|
@ -243,7 +243,7 @@ The old logo, the new detailed logo and the new simple logo.
|
|||
</a>
|
||||
</p>
|
||||
<p class="note">
|
||||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
|
||||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.
|
||||
</p>
|
||||
<a class="btn pull-right" href="/blog/2015/02/08/looking-at-the-past/#read-more">Read on →</a>
|
||||
</div>
|
||||
|
|
@ -349,7 +349,7 @@ Home Assistant now supports <code class="highlighter-rouge">--open-ui</code> and
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.</p>
|
||||
<p>The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.</p>
|
||||
<p>The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.</p>
|
||||
<p>Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.</p>
|
||||
<p>To enable the discovery component, add the following to your <code class="highlighter-rouge">home-assistant.conf</code>:</p>
|
||||
<div class="language-conf highlighter-rouge"><pre class="highlight"><code>[<span class="n">discovery</span>]
|
||||
|
|
@ -414,7 +414,7 @@ Home Assistant now supports <code class="highlighter-rouge">--open-ui</code> and
|
|||
<div class="entry-content clearfix">
|
||||
<p>The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
|
||||
This article will try to explain how they all relate.</p>
|
||||
<p>The first thing to introduce is the <strong>Internet of Things</strong> (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.</p>
|
||||
<p>The first thing to introduce is the <strong>Internet of Things</strong> (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.</p>
|
||||
<p>There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a <strong>hub</strong>.</p>
|
||||
<p>As a bare minimum a hub has to keep track of the state of each device and should be able to control them if possible. For example, it has to know which lights are on or off and offer a way to control the lights. For a sensor it only has to know the value. A hub with these capabilities offers <strong>home control</strong>.</p>
|
||||
<p class="img">
|
||||
|
|
|
|||
|
|
@ -231,7 +231,7 @@
|
|||
<li>Fix TP-Link light brightness issue #8744. (<a href="https://github.com/gollo">@gollo</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8755">#8755</a>)</li>
|
||||
<li>Fix typo in script error (<a href="https://github.com/n8henrie">@n8henrie</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8754">#8754</a>)</li>
|
||||
<li>Fix tradfri error spam (<a href="https://github.com/MartinHjelmare">@MartinHjelmare</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8738">#8738</a>) (<a href="https://home-assistant.io/components/light.tradfri/">light.tradfri docs</a>)</li>
|
||||
<li>Media Player - Pioneer: Supress exception if host is not available (fixes #8684) (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8732">#8732</a>) (<a href="https://home-assistant.io/components/media_player.pioneer/">media_player.pioneer docs</a>)</li>
|
||||
<li>Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) (<a href="https://github.com/fabaff">@fabaff</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8732">#8732</a>) (<a href="https://home-assistant.io/components/media_player.pioneer/">media_player.pioneer docs</a>)</li>
|
||||
<li>Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again (<a href="https://github.com/azogue">@azogue</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8716">#8716</a>) (<a href="https://home-assistant.io/components/telegram_bot.webhooks/">telegram_bot.webhooks docs</a>)</li>
|
||||
<li>Fixed sensor issue with Google Wifi routers in bridge mode (<a href="https://github.com/fronzbot">@fronzbot</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8710">#8710</a>) (<a href="https://home-assistant.io/components/sensor.google_wifi/">sensor.google_wifi docs</a>)</li>
|
||||
<li>Fix alexa cards (<a href="https://github.com/balloob">@balloob</a> - <a href="https://github.com/home-assistant/home-assistant/pull/8708">#8708</a>) (<a href="https://home-assistant.io/components/alexa/">alexa docs</a>)</li>
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the <a href="https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/">Thomas-Krenn-Award</a> put us on the 2nd place. This is an awesome achievment for an independent community project.</p>
|
||||
<p>You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the <a href="https://www.thomas-krenn.com/de/tkmag/allgemein/zammad-home-assistant-und-freifunk-das-sind-die-gewinner-des-thomas-krenn-awards-2017/">Thomas-Krenn-Award</a> put us on the 2nd place. This is an awesome achievement for an independent community project.</p>
|
||||
<p>I would like to thanks all contributors. Your endless effort made this possible.</p>
|
||||
<p><img src="/images/blog/2017-04-award/award.jpg" style="border: 0;box-shadow: none;" /></p>
|
||||
<p>The prize beside the very nice trophy contains hardware and we want to give that hardware partically away. We won four <a href="https://www.thomas-krenn.com/en/products/low-energy-systems/les-v2.html">Low Energy Server v2 (LES)</a> units with an Intel Celeron N2930, 8 GB of RAM, and a mSATA of 128 GB (one unit with 64 GB). We were thinking about to keep one of those units in Europe and one in North America for testing and to use during workshops and events. But the other two will go to interested parties.</p>
|
||||
|
|
@ -126,7 +126,7 @@
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>The idea of creating <a href="https://github.com/petkov/http_to_mqtt">HTTP to MQTT bridge</a> appeared when I was trying to integrate Google Assistant with my Home Assistant after watching <a href="https://youtu.be/087tQ7Ly7f4?t=265">BRUH Automation</a> video. Right now there is no MQTT service available in <a href="https://ifttt.com/about">IFTTT</a>. Existing integration solution uses <a href="https://ifttt.com/maker_webhooks">Maker Webhooks</a> which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.</p>
|
||||
<p>The idea of creating <a href="https://github.com/petkov/http_to_mqtt">HTTP to MQTT bridge</a> appeared when I was trying to integrate Google Assistant with my Home Assistant after watching <a href="https://youtu.be/087tQ7Ly7f4?t=265">BRUH Automation</a> video. Right now there is no MQTT service available in <a href="https://ifttt.com/about">IFTTT</a>. Existing integration solution uses <a href="https://ifttt.com/maker_webhooks">Maker Webhooks</a> which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.</p>
|
||||
<p>The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with <a href="https://expressjs.com/">Express</a> for the server part and <a href="https://www.npmjs.com/package/mqtt">MQTT.js</a> for the client.</p>
|
||||
<a class="btn pull-right" href="/blog/2017/03/28/http-to-mqtt-bridge/#read-more">Read on →</a>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -152,7 +152,7 @@ On the close horizon from <a href="https://github.com/Landrash">@Landrash</a> th
|
|||
</div>
|
||||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.</p>
|
||||
<p>One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assistant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.</p>
|
||||
<p>Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.</p>
|
||||
<a class="btn pull-right" href="/blog/2017/02/03/babyphone/#read-more">Read on →</a>
|
||||
</div>
|
||||
|
|
@ -258,7 +258,7 @@ On the close horizon from <a href="https://github.com/Landrash">@Landrash</a> th
|
|||
<li>Light - tellstick.py: Tellstick light fix (<a href="https://github.com/stefan-jonasson">@stefan-jonasson</a>)</li>
|
||||
<li>Switch - insteon_local.py: only check for devices when not defined in config (<a href="https://github.com/wardcraigj">@wardcraigj</a>)</li>
|
||||
<li>Notify - Twitter: Allow direct messaging to user (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
<li>Fan - MQTT: Dont set a speed when fan turns on (<a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Fan - MQTT: Don’t set a speed when fan turns on (<a href="https://github.com/robbiet480">@robbiet480</a>)</li>
|
||||
<li>Config: Allow easier customization of whole domain, entity lists, globs (<a href="https://github.com/andrey-git">@andrey-git</a>)</li>
|
||||
<li>Sensor - Homematic: Update device support (<a href="https://github.com/danielperna84">@danielperna84</a>)</li>
|
||||
<li>Binary sensor - ISS: Add location to attributes and option to show position on the map (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
|
|
@ -517,7 +517,7 @@ You have to note:
|
|||
<div class="entry-content clearfix">
|
||||
<p>Hello and Happy New Year!</p>
|
||||
<p>I am not Paulus. My name is Ben. I’m the creator of the <a href="https://www.youtube.com/channel/UCLecVrux63S6aYiErxdiy4w">BRUH Automation YouTube channel</a>. If you’ve ever seen any of my videos then you’ll know I love home automation and Home Assistant.</p>
|
||||
<p>I wanted to share some exciting stats from one of my latest projects - <a href="https://github.com/bruhautomation/BRUH-Christmas-Tree-2016">Control My Christmas tree!</a> For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.</p>
|
||||
<p>I wanted to share some exciting stats from one of my latest projects - <a href="https://github.com/bruhautomation/BRUH-Christmas-Tree-2016">Control My Christmas tree!</a> For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publicly accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.</p>
|
||||
<p>I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!</p>
|
||||
<p class="img">
|
||||
<img src="/images/blog/2017-01-bruh-christmas/christmas-tree.gif" />
|
||||
|
|
@ -549,7 +549,7 @@ You have to note:
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>A year ago <a href="https://home-assistant.io/blog/2015/12/22/amazon-echo-icloud-and-templates/">Home Assistant 0.10</a> landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that’s more than 7 a day!</p>
|
||||
<p>One of the things that Jon Walker, the founder of the company I work for (<a href="http://www.appfolioinc.com/">AppFolio</a>), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Everytime you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.</p>
|
||||
<p>One of the things that Jon Walker, the founder of the company I work for (<a href="http://www.appfolioinc.com/">AppFolio</a>), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.</p>
|
||||
<p>That’s why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it’s clear when things go out and people are not afraid to miss a release.</p>
|
||||
<p>However, being on a two week release cycle also means that the community has to rally each two weeks to make sure everything is ready to go. A lot of people are involved in making sure that all pieces are in place, to all of those: thank you! Thank you for all the time and effort you put in to make Home Assistant the best home automation software out there.</p>
|
||||
<p>Another big thanks goes out to the developers of the Python language and all the open source libraries and tools that Home Assistant depends on. Making quality software is not a small feat and all of you can be proud of yourself.</p>
|
||||
|
|
@ -773,7 +773,7 @@ You have to note:
|
|||
<li>Fix InfluxDB without authentication (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix Kodi without authentication (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix incorrect caching of /api/error_log (<a href="https://github.com/armills">@armills</a>)</li>
|
||||
<li>Fix incorrect ordering of service calls which could cause delays inbetween turning on multiple entities (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix incorrect ordering of service calls which could cause delays between turning on multiple entities (<a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Fix Nest Climate temperature issues (<a href="https://github.com/technicalpickles">@technicalpickles</a>)</li>
|
||||
</ul>
|
||||
<h3><a class="title-link" name="release-0345---december-12" href="#release-0345---december-12"></a> Release 0.34.5 - December 12</h3>
|
||||
|
|
|
|||
|
|
@ -548,7 +548,7 @@
|
|||
<li>Weather: Allow tracking severe weather alerts with <a href="https://home-assistant.io/components/sensor.wunderground/">WUnderground</a> (<a href="https://github.com/tchellomello">@tchellomello</a>)</li>
|
||||
<li>Sensor: New support added to track <a href="https://home-assistant.io/components/sensor.min_max/">min/max/mean</a> (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
<li>Convert EntityComponent to be async (<a href="https://github.com/pvizeli">@pvizeli</a>, <a href="https://github.com/balloob">@balloob</a>)</li>
|
||||
<li>Z-Wave: Add assocation service (<a href="https://github.com/turbokongen">@turbokongen</a>)</li>
|
||||
<li>Z-Wave: Add association service (<a href="https://github.com/turbokongen">@turbokongen</a>)</li>
|
||||
<li>Frontend - Services dev tool: persist state and tweak UI (<a href="https://github.com/justweb1">@justweb1</a>)</li>
|
||||
<li>Sensor: Support added for <a href="https://home-assistant.io/components/sensor.scrape/">scraping</a> websites (<a href="https://github.com/fabaff">@fabaff</a>)</li>
|
||||
<li>Clean up of tests (<a href="https://github.com/capellini">@capellini</a>)</li>
|
||||
|
|
@ -612,7 +612,7 @@
|
|||
</header>
|
||||
<div class="entry-content clearfix">
|
||||
<p>Yes, after only nine days comes 0.30. Don’t worry, we will try to keep our usual release cycle and not start to release every day.</p>
|
||||
<p>We guess that you already know: The <a href="/blog/2016/10/01/we-have-raspberry-image-now/">Raspberry Pi image</a> is available now. For Hassbian, <a href="https://github.com/Landrash">@Landrash</a> has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve <a href="https://community.home-assistant.io/c/installation/hassbian">feedback</a>, <a href="https://community.home-assistant.io/c/installation/hassbian">issue report</a>, and <a href="https://community.home-assistant.io/c/installation/hassbian">suggestions</a> to improve it.</p>
|
||||
<p>We guess that you already know: The <a href="/blog/2016/10/01/we-have-raspberry-image-now/">Raspberry Pi image</a> is available now. For Hassbian, <a href="https://github.com/Landrash">@Landrash</a> has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive <a href="https://community.home-assistant.io/c/installation/hassbian">feedback</a>, <a href="https://community.home-assistant.io/c/installation/hassbian">issue report</a>, and <a href="https://community.home-assistant.io/c/installation/hassbian">suggestions</a> to improve it.</p>
|
||||
<p>A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It’s a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.</p>
|
||||
<p>To reduce the run-time of your tests, <a href="https://github.com/balloob">@balloob</a> did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half.</p>
|
||||
<h3><a class="title-link" name="documentation" href="#documentation"></a> Documentation</h3>
|
||||
|
|
@ -936,7 +936,7 @@
|
|||
<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 whant 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 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>
|
||||
<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>
|
||||
<h3><a class="title-link" name="all-changes" href="#all-changes"></a> All changes</h3>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue