diff --git a/atom.xml b/atom.xml index 32c0a6b0ef..0e20c4083d 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index d2243f611f..02dee445ff 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index 53ae2a4d61..08b32c33de 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index 730cea4f6b..936d75e909 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 39d01244eb..ee0299a6df 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 5a7edfd678..38e8e6def2 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+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 fc9f54d1fa..419181585f 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/iot-data/atom.xml b/blog/categories/iot-data/atom.xml index fdac556d21..052155ac76 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/micropython/atom.xml b/blog/categories/micropython/atom.xml index 3339e52cbe..36f9022bbd 100644 --- a/blog/categories/micropython/atom.xml +++ b/blog/categories/micropython/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Micropython | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index bd43851e06..b42cb44ecb 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 608e6ccb01..e372a86051 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 94f1e1693e..f89276d62b 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index cada740031..1b43df6579 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+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 f02f14b20e..58cb0a3513 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index 314642284f..2720c8f276 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 79ad71da7e..e89d4e915f 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 2c7f11648b..de1f0e4438 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index 45b4038434..73f93edbdb 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index efd564bcb8..4ebda8ce44 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-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index e22ed59342..f8cac0b3ee 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 2c4f9171d7..d4486f0925 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-09-06T07:55:14+00:00 + 2016-09-06T14:36:10+00:00 https://home-assistant.io/ diff --git a/components/binary_sensor.zigbee/index.html b/components/binary_sensor.zigbee/index.html index 9d75be626b..e24b261086 100644 --- a/components/binary_sensor.zigbee/index.html +++ b/components/binary_sensor.zigbee/index.html @@ -89,9 +89,9 @@
-

A zigbee binary sensor in this context is a device connected to one of the digital input pins on a ZigBee module. The states reported by such a device are limited to ‘on’ or ‘off’. By default, a binary sensor is considered ‘on’ when the ZigBee device’s digital input pin is held ‘high’ and considered ‘off’ when it is held ‘low’. This behaviour can be inverted by setting the on_state configuration variable to low.

+

A zigbee binary sha_release: 0.13ensor in this context is a device connected to one of the digital input pins on a ZigBee module. The states reported by such a device are limited to on or off. By default, a binary sensor is considered on when the ZigBee device’s digital input pin is held ‘high’ and considered off when it is held low. This behaviour can be inverted by setting the on_state configuration variable to low.

-

To enable the ZigBee binary sensors in your installation, add the following lines to your configuration.yaml:

+

To enable a digital input pin as binary sensor in your installation, add the following lines to your configuration.yaml:

# Example configuration.yaml entry
 binary_sensor:
@@ -106,11 +106,10 @@
 

Configuration variables:

    -
  • name (Required): The name you’d like to give the binary sensor in Home Assistant.
  • -
  • platform (Required): Set to zigbee.
  • +
  • name (Required): The name you wouldd like to give the binary sensor in Home Assistant.
  • pin (Required): The number identifying which pin to use.
  • address: The long 64bit address of the remote ZigBee device whose digital input pin you’d like to sample. Do not include this variable if you want to sample the local ZigBee device’s pins.
  • -
  • on_state: Either high (default) or low, depicting whether the binary sensor is considered ‘on’ when the pin is ‘high’ or ‘low’.
  • +
  • on_state: Either high (default) or low, depicting whether the binary sensor is considered on when the pin is high or low.
@@ -130,6 +129,12 @@
+
+ IoT class: Local Polling +
+
+ Introduced in release: 0.12 +

Related components

    diff --git a/components/light.zigbee/index.html b/components/light.zigbee/index.html index a3346b18c8..6507456b5a 100644 --- a/components/light.zigbee/index.html +++ b/components/light.zigbee/index.html @@ -89,19 +89,9 @@
    -

    A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered ‘on’ when the ZigBee device’s digital output is held ‘high’ and considered ‘off’ when it is held ‘low’. This behaviour can be inverted by setting the on_state configuration variable to low.

    +

    A ZigBee light in this context is a light connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a light is considered on when the ZigBee device’s digital output is held high and considered off when it is held low. This behaviour can be inverted by setting the on_state configuration variable to low.

    -

    To configure a digital output pin as a light, use the following variables:

    - -
      -
    • name (Required): The name you’d like to give the light in Home Assistant.
    • -
    • platform (Required): Set to zigbee.
    • -
    • pin (Required): The number identifying which pin to use.
    • -
    • address: The long 64bit address of the remote ZigBee device whose digital output pin you’d like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
    • -
    • on_state: Either high (default) or low, depicting whether the digital output pin is pulled high or low when the light is turned on.
    • -
    - -

    Example

    +

    To configure a digital output pin as light, add the following to your configuration.yaml file:

    light:
       - name: Desk Lamp
    @@ -112,6 +102,15 @@
     
    +

    Configuration variables:

    + +
      +
    • name (Required): The name you’ would like to give the light in Home Assistant.
    • +
    • pin (Required): The number identifying which pin to use.
    • +
    • address: The long 64 bit address of the remote ZigBee device whose digital output pin you wouldd like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
    • +
    • on_state: Either high (default) or low, depicting whether the digital output pin is pulled high or low when the light is turned on.
    • +
    + @@ -128,6 +127,12 @@
    +
    + IoT class: Local Polling +
    +
    + Introduced in release: 0.12 +
    This is a platform for the Lights component. diff --git a/components/sensor.torque/index.html b/components/sensor.torque/index.html index e54f654627..204d7b7b83 100644 --- a/components/sensor.torque/index.html +++ b/components/sensor.torque/index.html @@ -129,8 +129,8 @@

    Configuration variables:

      -
    • name (Required): Vehicle name (your choice).
    • -
    • email: Email address configured in Torque application.
    • +
    • name (Optional): Vehicle name (your choice).
    • +
    • email (Required): Email address configured in Torque application.
    diff --git a/components/sensor.zigbee/index.html b/components/sensor.zigbee/index.html index c7a5dc458b..a570a3dd1d 100644 --- a/components/sensor.zigbee/index.html +++ b/components/sensor.zigbee/index.html @@ -170,6 +170,12 @@
    +
    + IoT class: Local Polling +
    +
    + Introduced in release: 0.12 +

    Related components

      diff --git a/components/switch.zigbee/index.html b/components/switch.zigbee/index.html index d40d9d2c50..698f92555b 100644 --- a/components/switch.zigbee/index.html +++ b/components/switch.zigbee/index.html @@ -89,19 +89,9 @@
      -

      A ZigBee switch in this context is a device connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a switch is considered ‘on’ when the ZigBee device’s digital output is held ‘high’ and considered ‘off’ when it is held ‘low’. This behaviour can be inverted by setting the on_state configuration variable to low.

      +

      A ZigBee switch in this context is a device connected to one of the digital output pins on a ZigBee module. It can simply be switched on and off. By default, a switch is considered on when the ZigBee device’s digital output is held high and considered off when it is held low. This behaviour can be inverted by setting the on_state configuration variable to low.

      -

      To configure a digital output pin as a switch, use the following variables:

      - -
        -
      • name (Required): The name you’d like to give the switch in Home Assistant.
      • -
      • platform (Required): Set to zigbee.
      • -
      • pin (Required): The number identifying which pin to use.
      • -
      • address: The long 64bit address of the remote ZigBee device whose digital output pin you’d like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
      • -
      • on_state: Either high (default) or low, depicting whether the digital output pin is pulled high or low when the switch is turned on.
      • -
      - -

      Example

      +

      To configure a digital output pin as switch, add the following to your configuration.yaml file:

      switch:
         - name: Pond Fountain
      @@ -112,6 +102,15 @@
       
      +

      Configuration variables:

      + +
        +
      • name (Required): The name you would like to give the switch in Home Assistant.
      • +
      • pin (Required): The number identifying which pin to use.
      • +
      • address: The long 6 4bit address of the remote ZigBee device whose digital output pin you would like to switch. Do not include this variable if you want to switch the local ZigBee device’s pins.
      • +
      • on_state: Either high (default) or low, depicting whether the digital output pin is pulled high or low when the switch is turned on.
      • +
      + @@ -128,6 +127,12 @@
      +
      + IoT class: Local Polling +
      +
      + Introduced in release: 0.12 +
      This is a platform for the Switches component. diff --git a/components/zigbee/index.html b/components/zigbee/index.html index d8c03b803f..939eeb6204 100644 --- a/components/zigbee/index.html +++ b/components/zigbee/index.html @@ -155,6 +155,9 @@ The port may also appear as /dev/ttyACM* if you’re communicating with the ZigB
      +
      + IoT class: Local Polling +
      Introduced in release: 0.12
      diff --git a/sitemap.xml b/sitemap.xml index 56657bea1f..2717652623 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1980,62 +1980,62 @@ https://home-assistant.io/demo/frontend.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/index.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-event.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-info.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-service.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-state.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-dev-template.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-history.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-iframe.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-logbook.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/demo/panels/ha-panel-map.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/googlef4f3693c209fe788.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:06+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:07+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:07+00:00 https://home-assistant.io/static/mdi-demo.html -2016-09-06T07:54:05+00:00 +2016-09-06T14:35:07+00:00