From c3d2095713cd70cef8840a8b08077bdb339e19e1 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Fri, 2 Sep 2016 05:58:21 +0000 Subject: [PATCH] Site updated at 2016-09-02 05:58:21 UTC --- atom.xml | 2 +- blog/categories/community/atom.xml | 2 +- blog/categories/device-tracking/atom.xml | 2 +- blog/categories/esp8266/atom.xml | 2 +- blog/categories/how-to/atom.xml | 2 +- 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 | 2 +- blog/categories/mqtt/atom.xml | 2 +- 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 +- components/ecobee/index.html | 10 +++---- .../sensor.fritzbox_callmonitor/index.html | 8 +++-- getting-started/z-wave-settings/index.html | 20 ++++++++----- sitemap.xml | 30 +++++++++---------- 25 files changed, 60 insertions(+), 50 deletions(-) diff --git a/atom.xml b/atom.xml index f9f64c0663..3508095d14 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index 56173c51c5..64a730e04c 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index aba8097c8c..e0b7ad1590 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 2b5db51601..8c415228fb 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 90608951b6..a723dd002a 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index d082b0c8bf..2021c16ec7 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+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 7cee9ae654..7a7fa74af4 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index daa9013171..90a08414cc 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index e3c5d06f01..cf37012542 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 66149eb0f6..bdf152f617 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index f9a04b648d..907b2f279a 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index d1dc7c6fcb..50364ba969 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index 0178efa17d..8d97d50a14 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+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 1b11d231f3..ba1d3ed338 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index a0c91563d8..25ca642375 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 9f1bb0b24a..6a7cff1bc5 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index c233bf5dca..f1e5c2a91b 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index a607ffa653..b6bc76321b 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 8780533371..f95b5016ed 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]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index 97d3859ad8..13b4015f78 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 22ca14dd67..ffc7db2389 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-09-01T19:25:17+00:00 + 2016-09-02T05:56:41+00:00 https://home-assistant.io/ diff --git a/components/ecobee/index.html b/components/ecobee/index.html index bd37836624..d4b63594f1 100644 --- a/components/ecobee/index.html +++ b/components/ecobee/index.html @@ -89,11 +89,11 @@
-

The Ecobee platform lets you control a thermostats and view sensor data from the Ecobee thermostat.

+

The ecobee component lets you control a thermostats and view sensor data from ecobee thermostats.

-

You will need to obtain an API key from ecobee’s developer site to use this component. To get the key, first you need to register your thermostat. Once you have done that, click on the ‘Become a developer’ link on the developer site. Login with your ecobee credentials, accept the SDK agreement, fill in the fields, and click save. Now login to the regular consumer portal, and in the hamburger menu there will br a new option ‘Developer’. Select that, then select ‘Create New’. Give your app a name (it appears to need to be unique across all users, as I tried ‘home-assistant’ and it said it was already in use) and a summary (neither of these are important as they are not used anywhere). For Authorization method select ‘ecobee PIN’. You don’t need an Application Icon or Detailed Description. Click Save. Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the ‘X’ to close the Developer section.

+

You will need to obtain an API key from ecobee’s developer site to use this component. To get the key, first you need to register your thermostat. Once you have done that, click on the Become a developer link on the developer site. Login with your Ecobee credentials, accept the SDK agreement, fill in the fields, and click save. Now login to the regular consumer portal, and in the hamburger menu there will be a new option Developer. Select that, then select Create New. Give your app a name (it appears to need to be unique across all users, as I tried ‘home-assistant’ and it said it was already in use) and a summary (neither of these are important as they are not used anywhere). For Authorization method select ecobee PIN. You don’t need an Application Icon or Detailed Description. Click Save. Now under the Name and Summary Section you will have an API key. Copy this key and use it in you configuration section below. Click the X to close the Developer section.

-

The first time you run Home-Assistant with this component it will give you a PIN code that you need to authorize in the ecobee consumer portal. You can do this by clicking ‘Add Application’ in the ‘My Apps’ section in the sidebar. Enter the PIN code from the Home Assistant screeen. To get the PIN code select the item in the Ecobee card. If you do not have an Ecobee card, you may be using groups with default_view that don’t show the card. To get around this you can temporarily comment out the default_view section or add the configurator.ecobee component to your default_view and restart Home Assistant. Once you enter the PIN on the Ecobee site, wait approximately 5 minutes and then click on the ‘I have authorized the app’ link at the bottom of the Ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full Ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your default_view (if you had to disable it) and add the Ecobee sensors to a group and/or view.

+

The first time you run Home Assistant with this component it will give you a PIN code that you need to authorize in the ecobee consumer portal. You can do this by clicking Add Application in the My Apps section in the sidebar. Enter the PIN code from the Home Assistant screeen. To get the PIN code select the item in the ecobee card. If you do not have an ecobee card, you may be using groups with default_view that don’t show the card. To get around this you can temporarily comment out the default_view section or add the configurator.ecobee component to your default_view and restart Home Assistant. Once you enter the PIN on the ecobee site, wait approximately 5 minutes and then click on the I have authorized the app link at the bottom of the ecobee popup window. If everything worked correctly, you should now be able to restart Home Assistant again to see the full ecobee card with all of the sensors populated or see the list of sensors in the developer tools. Now you can re-enable your default_view (if you had to disable it) and add the ecobee sensors to a group and/or view.

To set it up, add the following information to your configuration.yaml file:

@@ -106,8 +106,8 @@

Configuration variables:

    -
  • api_key (Required): Your Ecobee api key.
    • -
  • hold_temp (Optional): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event (False, default).
    • +
  • api_key (Required): Your ecobee API key.
    • +
  • hold_temp (Optional): True/False whether or not to hold changes indefinitely (True) or until the next scheduled event. Defaults to False.

diff --git a/components/sensor.fritzbox_callmonitor/index.html b/components/sensor.fritzbox_callmonitor/index.html index 9d20d1234e..e5a4c9d68e 100644 --- a/components/sensor.fritzbox_callmonitor/index.html +++ b/components/sensor.fritzbox_callmonitor/index.html @@ -90,8 +90,9 @@

The fritzbox_callmonitor sensor monitors the call monitor exposed by AVM Fritz!Box routers -on TCP port 1012. It will assume the values ‘idle’, ‘ringing’, ‘dialing’, or ‘talking’, -with the phone numbers involved contained in the state attributes.

+on TCP port 1012. It will assume the values idle, ringing, dialing, or talking with the phone numbers involved contained in the state attributes.

+ +

To activate the call monitor on your Fritz!Box, dial #965 from any phone connected to it.

To use the Fritz!Box call monitor in your installation, add the following to your configuration.yaml file:

@@ -124,6 +125,9 @@ with the phone numbers involved contained in the state attributes.

+
+ IoT class: Local Polling +
Introduced in release: 0.27
diff --git a/getting-started/z-wave-settings/index.html b/getting-started/z-wave-settings/index.html index 015ebc1503..403cb50a7d 100644 --- a/getting-started/z-wave-settings/index.html +++ b/getting-started/z-wave-settings/index.html @@ -89,19 +89,25 @@
-

You may wish to modify the zwave settings ozw*.xml file in your .homeassistant root folder, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize Open-Zwave Control Panel. Alternatively, use Domoticz, which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image.

+

You may wish to modify the Z-Wave settings in your ozw*.xml file stored in the .homeassistant directory, or certain situations/devices may require it (i.e. Aeon Multisensor 6). To do this, utilize Open-Zwave Control Panel. Alternatively, use Domoticz, which incorporates the Open-Zwave Control Panel project into an easy to use Raspberry Pi image.

-

The reasoning for using these tools is that your Zwave controller stores the values and data that are used to control the network. The XML file in the .homeassistant folder acts as a settings/values cache for the zwave network, so modifying it directly won’t change the network values. The Open-Zwave Control Panel writes values directly to the network, and will provide you with an updated .xml file to overwrite in your .homeassistant folder. This is the most foolproof way to make modifications to your zwave devices.

+

The reasoning for using these tools is that your Z-Wave controller stores the values and data that are used to control the network. The XML file in the .homeassistant folder acts as a settings/values cache for the Z-Wave network, so modifying it directly won’t change the network values. The Open-Zwave Control Panel writes values directly to the network and will provide you with an updated .xml file to overwrite in your .homeassistant folder. This is the most foolproof way to make modifications to your Z-Wave devices.

-

Although totally normal for your ZWave stick (Aeon Aeotec Z-Stick Gen5 for example) to cycle through LEDs (Yellow, Blue and Red) while plugged into your Pi, it’s also super annoying. If you want to turn off the cycling color, you can use the following commands from a terminal session to your Pi.

+

Although totally normal for your Z-Wave stick (Aeon Aeotec Z-Stick Gen5 for example) to cycle through its LEDs (Yellow, Blue and Red) while plugged into your system. If you don like this behaviour then you could turn it off.

-

Turn off Disco lights

+

Use the following commands from a terminal session to your Pi where your Z-Wave stick is connected as an example.

-

echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00

+

Turn off “Disco lights”:

-

Turn on Disco lights

+
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x00\x05\x01\x51" > /dev/serial/by-id/usb-0658_0200-if00
+
+
-

echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00

+

Turn on “Disco lights”:

+ +
$ echo -e -n "\x01\x08\x00\xF2\x51\x01\x01\x05\x01\x50" > /dev/serial/by-id/usb-0658_0200-if00
+
+
diff --git a/sitemap.xml b/sitemap.xml index 3e7f332ae4..02acd55fec 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1980,62 +1980,62 @@ https://home-assistant.io/demo/frontend.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/index.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00 https://home-assistant.io/static/mdi-demo.html -2016-09-01T19:24:30+00:00 +2016-09-02T05:55:52+00:00