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

Site updated at 2017-02-11 22:50:44 UTC

Browse source
This commit is contained in:
Travis CI 2017-02-11 22:50:44 +00:00
parent 83c3bf8dbf
commit 4bedc7a4cc
627 changed files with 11192 additions and 2416 deletions
Download patch file Download diff file Expand all files Collapse all files

101
blog/posts/3/index.html
View file

@ -79,6 +79,57 @@
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/08/31/esp8266-and-micropython-part2/">ESP8266 and MicroPython - Part 2</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-08-31T04:17:25+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> August 31, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> four minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>ESP8266</li>
<li>How-To</li>
<li>MQTT</li>
<li>Micropython</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/08/31/esp8266-and-micropython-part2/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><img src="/images/blog/2016-07-micropython/micropython.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" />
So, part 1 of <a href="/blog/2016/07/28/esp8266-and-micropython-part1/">ESP8266 and MicroPython</a> was pretty lame, right? Instead of getting information out of Home Assistant we are going a step forward and create our own sensor which is sending details about its state to a Home Assistant instance.</p>
<a class="btn pull-right" href="/blog/2016/08/31/esp8266-and-micropython-part2/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<article class="listing">
<header>
@ -869,56 +920,6 @@ One of the graphs created with this tutorial.
</article>
<hr>
<article class="listing">
<header>
<h1 class="beta">
<a href="/blog/2016/07/19/visualizing-your-iot-data/">Visualize your IoT data</a>
</h1>
<div class="meta clearfix">
<time datetime="2016-07-19T16:00:00+00:00" pubdate data-updated="true"><i class="icon-calendar"></i> July 19, 2016</time>
<span class="byline author vcard"><i class='icon-user'></i> Fabian Affolter</span>
<span><i class='icon-time'></i> five minutes reading time</span>
<span>
<i class="icon-tags"></i>
<ul class="tags unstyled">
<li>How-To</li>
<li>IoT-Data</li>
</ul>
</span>
<a class='comments'
href="/blog/2016/07/19/visualizing-your-iot-data/#disqus_thread"
>Comments</a>
</div>
</header>
<div class="entry-content clearfix">
<p><img src="/images/blog/2016-07-reporting/mpl-sensor.png" style="clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;" width="200" /></p>
<p>The <a href="/components/history/">history component</a> is tracking everything that is going on within Home Assistant. This means that you have access to all stored information about your home. Our history is not a full-fledged graphical processing and visualization component as you may know from systems and network monitoring tools. The current limitation is that you only can select a day for a visual output of your information and not a period. Also, there is no possibility to drill down on a specific entity.</p>
<p>This blog post will show you ways to export data for reporting, visualization, or further analysis of automation rules.</p>
<a class="btn pull-right" href="/blog/2016/07/19/visualizing-your-iot-data/#read-more">Read on &rarr;</a>
</div>
</article>
<hr>
<div class="pagination">