From ec6ad6ac72f5350175c099ee510255aa5c712549 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Sat, 11 Feb 2017 21:51:49 +0000 Subject: [PATCH] Site updated at 2017-02-11 21:51:49 UTC --- atom.xml | 4 +-- .../esp8266-and-micropython-part2/index.html | 4 +-- blog/categories/community/atom.xml | 2 +- blog/categories/device-tracking/atom.xml | 2 +- blog/categories/esp8266/atom.xml | 4 +-- blog/categories/how-to/atom.xml | 4 +-- blog/categories/ibeacons/atom.xml | 2 +- blog/categories/internet-of-things/atom.xml | 2 +- blog/categories/iot-data/atom.xml | 2 +- blog/categories/micropython/atom.xml | 4 +-- blog/categories/mqtt/atom.xml | 4 +-- blog/categories/organisation/atom.xml | 2 +- blog/categories/owntracks/atom.xml | 2 +- blog/categories/presence-detection/atom.xml | 2 +- .../public-service-announcement/atom.xml | 2 +- blog/categories/release-notes/atom.xml | 2 +- blog/categories/survey/atom.xml | 2 +- blog/categories/talks/atom.xml | 2 +- blog/categories/technology/atom.xml | 2 +- blog/categories/user-stories/atom.xml | 2 +- blog/categories/video/atom.xml | 2 +- blog/categories/website/atom.xml | 2 +- blog/posts/2/index.html | 2 +- sitemap.xml | 30 +++++++++---------- 24 files changed, 44 insertions(+), 44 deletions(-) diff --git a/atom.xml b/atom.xml index 3bca036f5e..d29ac8387b 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ @@ -1975,7 +1975,7 @@ So, part 1 of HTTP POST requests, MQTT is the quickest way (from the author’s point of view) to publish information with DIY devices.

-

You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it’s perfectly fine to wait a couple of seconds to retrieve the value. If it’s a motion detector the state change should be available instantly. This means the sensor must take initiative.

+

You have to make a decision: Do you want to pull or to [poll](https://en.wikipedia.org/wiki/Polling_(computer_science) the information for the sensor? For slowly changing values like temperature it’s perfectly fine to wait a couple of seconds to retrieve the value. If it’s a motion detector the state change should be available instantly in Home Assistant. This means the sensor must take initiative and send the data to Home Assistant.

An example for pulling is aREST. This is a great way to work with the ESP8266 based units and the Ardunio IDE.

diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html index acaaa7e9ba..26e76b1959 100644 --- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html +++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html @@ -88,7 +88,7 @@
Fabian Affolter - three minutes reading time + four minutes reading time
    @@ -122,7 +122,7 @@ So, part 1 of ESP8266

    Beside HTTP POST requests, MQTT is the quickest way (from the author’s point of view) to publish information with DIY devices.

    -

    You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it’s perfectly fine to wait a couple of seconds to retrieve the value. If it’s a motion detector the state change should be available instantly. This means the sensor must take initiative.

    +

    You have to make a decision: Do you want to pull or to [poll](https://en.wikipedia.org/wiki/Polling_(computer_science) the information for the sensor? For slowly changing values like temperature it’s perfectly fine to wait a couple of seconds to retrieve the value. If it’s a motion detector the state change should be available instantly in Home Assistant. This means the sensor must take initiative and send the data to Home Assistant.

    An example for pulling is aREST. This is a great way to work with the ESP8266 based units and the Ardunio IDE.

    diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 8ee658ec7c..80913ee28d 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: community | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index b201663550..1bf8169010 100644 --- a/blog/categories/device-tracking/atom.xml +++ b/blog/categories/device-tracking/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Device-Tracking | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index c6a265064c..8b22a20c0a 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ @@ -25,7 +25,7 @@ So, part 1 of [ESP8266 and MicroPython](/blog/2016/07/28/esp8266-and-micropython Beside [HTTP POST](https://en.wikipedia.org/wiki/POST_(HTTP)) requests, MQTT is the quickest way (from the author's point of view) to publish information with DIY devices. -You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly. This means the sensor must take initiative. +You have to make a decision: Do you want to pull or to [poll](https://en.wikipedia.org/wiki/Polling_(computer_science) the information for the sensor? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly in Home Assistant. This means the sensor must take initiative and send the data to Home Assistant. An example for pulling is [aREST](/components/sensor.arest/). This is a great way to work with the ESP8266 based units and the Ardunio IDE. diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index f562959c8c..64e96bf2d7 100644 --- a/blog/categories/how-to/atom.xml +++ b/blog/categories/how-to/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: How-To | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ @@ -167,7 +167,7 @@ So, part 1 of [ESP8266 and MicroPython](/blog/2016/07/28/esp8266-and-micropython Beside [HTTP POST](https://en.wikipedia.org/wiki/POST_(HTTP)) requests, MQTT is the quickest way (from the author's point of view) to publish information with DIY devices. -You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly. This means the sensor must take initiative. +You have to make a decision: Do you want to pull or to [poll](https://en.wikipedia.org/wiki/Polling_(computer_science) the information for the sensor? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly in Home Assistant. This means the sensor must take initiative and send the data to Home Assistant. An example for pulling is [aREST](/components/sensor.arest/). This is a great way to work with the ESP8266 based units and the Ardunio IDE. diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 8624583816..8eb57485f5 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/internet-of-things/atom.xml b/blog/categories/internet-of-things/atom.xml index 93fe80cfbd..c76ce3dc1d 100644 --- a/blog/categories/internet-of-things/atom.xml +++ b/blog/categories/internet-of-things/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Internet-of-Things | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index b0702e9b30..f68553e805 100644 --- a/blog/categories/iot-data/atom.xml +++ b/blog/categories/iot-data/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: IoT-Data | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 8773b47246..08f921d6b1 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ @@ -25,7 +25,7 @@ So, part 1 of [ESP8266 and MicroPython](/blog/2016/07/28/esp8266-and-micropython Beside [HTTP POST](https://en.wikipedia.org/wiki/POST_(HTTP)) requests, MQTT is the quickest way (from the author's point of view) to publish information with DIY devices. -You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly. This means the sensor must take initiative. +You have to make a decision: Do you want to pull or to [poll](https://en.wikipedia.org/wiki/Polling_(computer_science) the information for the sensor? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly in Home Assistant. This means the sensor must take initiative and send the data to Home Assistant. An example for pulling is [aREST](/components/sensor.arest/). This is a great way to work with the ESP8266 based units and the Ardunio IDE. diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 338f37ba78..9ff847ffba 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ @@ -25,7 +25,7 @@ So, part 1 of [ESP8266 and MicroPython](/blog/2016/07/28/esp8266-and-micropython Beside [HTTP POST](https://en.wikipedia.org/wiki/POST_(HTTP)) requests, MQTT is the quickest way (from the author's point of view) to publish information with DIY devices. -You have to make a decision: Do you want to pull or to poll? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly. This means the sensor must take initiative. +You have to make a decision: Do you want to pull or to [poll](https://en.wikipedia.org/wiki/Polling_(computer_science) the information for the sensor? For slowly changing values like temperature it's perfectly fine to wait a couple of seconds to retrieve the value. If it's a motion detector the state change should be available instantly in Home Assistant. This means the sensor must take initiative and send the data to Home Assistant. An example for pulling is [aREST](/components/sensor.arest/). This is a great way to work with the ESP8266 based units and the Ardunio IDE. diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index aa9a3d9e2b..8e985f8b3c 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 3abd894bc8..3a15c982ba 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 906e592f4d..2b552c278c 100644 --- a/blog/categories/presence-detection/atom.xml +++ b/blog/categories/presence-detection/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Presence-Detection | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/public-service-announcement/atom.xml b/blog/categories/public-service-announcement/atom.xml index 6cb17d2cdd..4020d2e326 100644 --- a/blog/categories/public-service-announcement/atom.xml +++ b/blog/categories/public-service-announcement/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Public-Service-Announcement | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index d9ac9e2256..dd457d5a5d 100644 --- a/blog/categories/release-notes/atom.xml +++ b/blog/categories/release-notes/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Release-Notes | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index b9fc43111e..ee31b7c4be 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 036142f0ee..8edf0417e9 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 18e3892523..8e2aa17101 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index e84f372dbb..69bd8d6f45 100644 --- a/blog/categories/user-stories/atom.xml +++ b/blog/categories/user-stories/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: User-Stories | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index af14a5385b..fd877296a4 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index ed1ee2756b..45cfa29ffa 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-02-10T18:19:45+00:00 + 2017-02-11T21:49:12+00:00 https://home-assistant.io/ diff --git a/blog/posts/2/index.html b/blog/posts/2/index.html index 755f713eb2..484adc55f3 100644 --- a/blog/posts/2/index.html +++ b/blog/posts/2/index.html @@ -1373,7 +1373,7 @@
    Fabian Affolter - three minutes reading time + four minutes reading time
      diff --git a/sitemap.xml b/sitemap.xml index f119092fbd..fd46683046 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2737,62 +2737,62 @@ https://home-assistant.io/demo/frontend.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/index.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00 https://home-assistant.io/static/mdi-demo.html -2017-02-10T18:18:58+00:00 +2017-02-11T21:48:27+00:00