From 71ff7e5d48fa75ca5189ce90920239a24f41a566 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Sat, 11 Feb 2017 22:15:34 +0000 Subject: [PATCH] Site updated at 2017-02-11 22:15:34 UTC --- atom.xml | 4 +-- .../esp8266-and-micropython-part2/index.html | 2 +- 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 +- sitemap.xml | 30 +++++++++---------- 23 files changed, 42 insertions(+), 42 deletions(-) diff --git a/atom.xml b/atom.xml index d29ac8387b..0249ce46c4 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+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](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.

+

You have to make a decision: Do you want to pull or to poll 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 26e76b1959..c67dcca0a4 100644 --- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html +++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html @@ -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](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.

+

You have to make a decision: Do you want to pull or to poll 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 80913ee28d..d9bf9fadb5 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: community | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 1bf8169010..ebff0d0ff3 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 8b22a20c0a..c23b983dc6 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+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](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. +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 64e96bf2d7..e2b9d94730 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+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](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. +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 8eb57485f5..fe698ec9dd 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+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 c76ce3dc1d..8d9590e68d 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index f68553e805..02e98b36e4 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 08f921d6b1..07e3fe2b79 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+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](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. +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 9ff847ffba..f6c4ab66a7 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+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](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. +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 8e985f8b3c..af57015145 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 3a15c982ba..3f1f896245 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 2b552c278c..70fe75defa 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+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 4020d2e326..f0fea82ea1 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index dd457d5a5d..25fb223847 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index ee31b7c4be..3aa0c05ac7 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 8edf0417e9..ff4f70d2bd 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 8e2aa17101..e17e65b025 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 69bd8d6f45..e0dd876375 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-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index fd877296a4..1524122eef 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 45cfa29ffa..690e490f1c 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-02-11T21:49:12+00:00 + 2017-02-11T22:12:58+00:00 https://home-assistant.io/ diff --git a/sitemap.xml b/sitemap.xml index fd46683046..78605975bf 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2737,62 +2737,62 @@ https://home-assistant.io/demo/frontend.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/index.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:13+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:14+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:14+00:00 https://home-assistant.io/static/mdi-demo.html -2017-02-11T21:48:27+00:00 +2017-02-11T22:12:14+00:00