From 83c3bf8dbff964bca90890847a04342947f6ba58 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Sat, 11 Feb 2017 22:31:24 +0000 Subject: [PATCH] Site updated at 2017-02-11 22:31:24 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 0249ce46c4..1434fb77cc 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 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 or it could be missed. 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 c67dcca0a4..702120be4b 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 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 or it could be missed. 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 d9bf9fadb5..dd9701db99 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: community | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index ebff0d0ff3..097eebcae1 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index c23b983dc6..e02a262fa7 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 or it could be missed. 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 e2b9d94730..90d88c4fe2 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 or it could be missed. 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 fe698ec9dd..cf55d18135 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 8d9590e68d..b03fa0a273 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index 02e98b36e4..03a3c46ad7 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 07e3fe2b79..fbf8bf6e49 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 or it could be missed. 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 f6c4ab66a7..a1e6625dce 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 or it could be missed. 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 af57015145..a426bb98d7 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 3f1f896245..38a3b5aa0c 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 70fe75defa..4dc5298340 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+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 f0fea82ea1..92a26f2b94 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 25fb223847..06af4d107e 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 3aa0c05ac7..e0465f4842 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index ff4f70d2bd..9a455906f1 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index e17e65b025..9288ea2e51 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index e0dd876375..71451f0928 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-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 1524122eef..fe50f85711 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 690e490f1c..4e82bbc5dd 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2017-02-11T22:12:58+00:00 + 2017-02-11T22:28:32+00:00 https://home-assistant.io/ diff --git a/sitemap.xml b/sitemap.xml index 78605975bf..316cf956a9 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2737,62 +2737,62 @@ https://home-assistant.io/demo/frontend.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/index.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2017-02-11T22:12:13+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2017-02-11T22:12:14+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2017-02-11T22:12:14+00:00 +2017-02-11T22:27:34+00:00 https://home-assistant.io/static/mdi-demo.html -2017-02-11T22:12:14+00:00 +2017-02-11T22:27:34+00:00