From 5ac15fb614471d24316d2252745fb7c3844bf911 Mon Sep 17 00:00:00 2001 From: Travis CI Date: Thu, 9 Jun 2016 05:10:48 +0000 Subject: [PATCH] Site updated at 2016-06-09 05:10:48 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/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/binary_sensor.template/index.html | 1 + components/switch.template/index.html | 1 + components/zwave/index.html | 254 +----------- getting-started/android/index.html | 8 + getting-started/automation-action/index.html | 8 + .../automation-condition/index.html | 8 + .../automation-create-first/index.html | 8 + .../automation-examples/index.html | 8 + .../automation-templating/index.html | 8 + getting-started/automation-trigger/index.html | 8 + .../automation-troubleshooting/index.html | 8 + getting-started/automation/index.html | 8 + getting-started/autostart-macos/index.html | 8 + getting-started/autostart-synology/index.html | 8 + getting-started/autostart-systemd/index.html | 8 + getting-started/autostart-upstart/index.html | 8 + getting-started/autostart/index.html | 8 + getting-started/basic/index.html | 8 + getting-started/browsers/index.html | 8 + getting-started/configuration/index.html | 8 + .../customizing-devices/index.html | 8 + getting-started/devices/index.html | 8 + getting-started/index.html | 8 + .../installation-docker/index.html | 8 + .../index.html | 8 + .../installation-raspberry-pi/index.html | 8 + .../installation-synology/index.html | 8 + .../installation-vagrant/index.html | 8 + .../installation-virtualenv/index.html | 8 + getting-started/presence-detection/index.html | 8 + getting-started/scripts-conditions/index.html | 8 + .../scripts-service-calls/index.html | 8 + getting-started/scripts/index.html | 8 + .../troubleshooting-configuration/index.html | 8 + getting-started/troubleshooting/index.html | 8 + getting-started/updating/index.html | 8 + getting-started/yaml/index.html | 8 + .../z-wave-controllers}/index.html | 107 ++++- .../z-wave-device-specific/index.html | 280 +++++++++++++ getting-started/z-wave-settings/index.html | 208 ++++++++++ getting-started/z-wave/index.html | 381 ++++++++++++++++++ sitemap.xml | 27 +- topics/index.html | 3 - 62 files changed, 1267 insertions(+), 305 deletions(-) rename {topics/z-wave => getting-started/z-wave-controllers}/index.html (54%) create mode 100644 getting-started/z-wave-device-specific/index.html create mode 100644 getting-started/z-wave-settings/index.html create mode 100644 getting-started/z-wave/index.html diff --git a/atom.xml b/atom.xml index ed6ae1c118..11d12ce7a3 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml index b8e5757c70..93d6bf7c6e 100644 --- a/blog/categories/community/atom.xml +++ b/blog/categories/community/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Community | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/device-tracking/atom.xml b/blog/categories/device-tracking/atom.xml index c4347b829b..6256d1e547 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/esp8266/atom.xml b/blog/categories/esp8266/atom.xml index e0f641a473..5b737e45c1 100644 --- a/blog/categories/esp8266/atom.xml +++ b/blog/categories/esp8266/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: ESP8266 | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/how-to/atom.xml b/blog/categories/how-to/atom.xml index 2592ea10ea..1d997d91d9 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/ibeacons/atom.xml b/blog/categories/ibeacons/atom.xml index 2a3e3e3aa0..37e668cf5f 100644 --- a/blog/categories/ibeacons/atom.xml +++ b/blog/categories/ibeacons/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: iBeacons | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+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 eab15b4a0c..b37f72ed56 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/mqtt/atom.xml b/blog/categories/mqtt/atom.xml index 6689096dbe..afb822cb89 100644 --- a/blog/categories/mqtt/atom.xml +++ b/blog/categories/mqtt/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: MQTT | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml index 8cc2e664b7..65b112d545 100644 --- a/blog/categories/organisation/atom.xml +++ b/blog/categories/organisation/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Organisation | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/owntracks/atom.xml b/blog/categories/owntracks/atom.xml index 8fdac2594b..1531efe189 100644 --- a/blog/categories/owntracks/atom.xml +++ b/blog/categories/owntracks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: OwnTracks | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/presence-detection/atom.xml b/blog/categories/presence-detection/atom.xml index b505e9dadf..f0329665bc 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+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 608c4b43fd..598afb6134 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml index d47bf1e901..10bbe178e1 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml index 3a681f04e3..5c52eb551a 100644 --- a/blog/categories/survey/atom.xml +++ b/blog/categories/survey/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Survey | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/talks/atom.xml b/blog/categories/talks/atom.xml index 1af194ba5c..c0b69b740c 100644 --- a/blog/categories/talks/atom.xml +++ b/blog/categories/talks/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Talks | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml index f020226300..65c8316bd7 100644 --- a/blog/categories/technology/atom.xml +++ b/blog/categories/technology/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Technology | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/user-stories/atom.xml b/blog/categories/user-stories/atom.xml index 06b5833948..05f7aa9cb2 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-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/video/atom.xml b/blog/categories/video/atom.xml index d9417450bf..1a3180a401 100644 --- a/blog/categories/video/atom.xml +++ b/blog/categories/video/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Video | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/blog/categories/website/atom.xml b/blog/categories/website/atom.xml index 42b13ea203..8a643e3a7b 100644 --- a/blog/categories/website/atom.xml +++ b/blog/categories/website/atom.xml @@ -4,7 +4,7 @@ <![CDATA[Category: Website | Home Assistant]]> - 2016-06-08T15:57:19+00:00 + 2016-06-09T05:10:06+00:00 https://home-assistant.io/ diff --git a/components/binary_sensor.template/index.html b/components/binary_sensor.template/index.html index bebbac53a1..eedb087333 100644 --- a/components/binary_sensor.template/index.html +++ b/components/binary_sensor.template/index.html @@ -114,6 +114,7 @@
  • sensor_class (Optional): The type/class of the sensor to set the icon in the frontend.
  • value_template (Optional): Defines a template to extract a value from the payload.
  • warnings (Optional): Turn off warnings (useful if the sensor is loaded before devices it depends on).
    • +
  • entity_id (Optional): Add a list of entity_ids so the sensor only reacts to state changes of these entities. This will reduce the number of times the sensor will try to update it’s state.
    • diff --git a/components/switch.template/index.html b/components/switch.template/index.html index 631b245236..f50095624c 100644 --- a/components/switch.template/index.html +++ b/components/switch.template/index.html @@ -124,6 +124,7 @@
  • value_template (Required): Defines a template to set the state of the switch.
  • turn_on (Required): Defines an action to run when the switch is turned on.
  • turn_off (Required): Defines an action to run when the switch is turned off.
    • +
  • entity_id (Optional): Add a list of entity_ids so the sensor only reacts to state changes of these entities. This will reduce the number of times the sensor will try to update it’s state.
    • diff --git a/components/zwave/index.html b/components/zwave/index.html index fafdf2b8d7..e341e656bd 100644 --- a/components/zwave/index.html +++ b/components/zwave/index.html @@ -89,260 +89,8 @@
    -

    Z-Wave integration for Home Assistant allows you to observe and control connected Z-Wave devices. Z-Wave support requires a supported Z-Wave USB stick to be plugged into the host.

    +

    Please see the getting started section for in-depth documentation on how to use the Z-Wave component.

    -

    There is currently support for switches, lights and sensors. All will be picked up automatically after configuring this platform.

    - -

    Installation

    - -

    To allow Home Assistant to talk to your Z-Wave USB stick you will have to compile the OpenZWave library and install the related python-OpenZWave package. This can be done as follows. (Note: The Home Assistant docker image has support for Z-Wave built-in)

    - -

    Make sure you have the correct dependencies installed before running the script:

    - -
    - 
    $ sudo apt-get install cython3 libudev-dev python3-sphinx python3-setuptools
-
    -
    -
    - -

    Make sure you have at least version 0.23 of cython.

    - -
    - 
    $ sudo pip3 install --upgrade cython
-
    -
    -
    - -

    Then get the OpenZWave files and switch to the python3 branch:

    -

    Do not use root to build python-openzwave as it will surely fail.

    -
    - 
    $ git clone https://github.com/OpenZWave/python-openzwave.git
-$ cd python-openzwave
-$ git checkout python3
-$ PYTHON_EXEC=$(which python3) make build
-$ sudo PYTHON_EXEC=$(which python3) make install
-
    -
    -
    -

    -Instead of make install, you can alternatively build your own python-openzwave package which can be easily uninstalled: - -$ sudo PYTHON_EXEC=$(which python3) checkinstall --pkgname python-openzwave --pkgversion 1.0 --provides python-openzwave - -

    - -

    With this installation, your config_path needed below will resemble:

    - -
    - 
    /usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.0b8-py3.4-linux-x86_64.egg/config
-
    -
    -
    - -

    Configuration

    - -
    - 
    # Example configuration.yaml entry
-zwave:
-  usb_path: /dev/ttyUSB0
-  config_path: /usr/local/share/python-openzwave/config
-  polling_interval: 60000
-  customize:
-    sensor.greenwave_powernode_6_port_energy_10:
-        polling_intensity: 1
-
    -
    -
    - -

    Configuration variables:

    - -
      -
    • usb_path (Required): The port where your device is connected to your Home Assistant host.
      • -
    • config_path (Optional): The path to the Python Open Z-Wave configuration files.
      • -
    • autoheal (Optional): Allows disabling auto ZWave heal at midnight. Defaults to True.
      • -
    • polling_interval (Optional): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.
      • -
    • customize (Optional): This attribute contains node-specific override values: -
        -
      • polling_intensity (Optional): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2-every other time, etc). If not specified then your device will not be polled.
        • -
      -
      • -
    - -

    To find the path of your Z-Wave stick, run:

    - -
    - 
    $ ls /dev/ttyUSB*
-
    -
    -
    - -

    Or, on some other systems (such as Raspberry Pi), use:

    - -
    - 
    $ ls /dev/ttyACM*
-
    -
    -
    - -

    -Depending on what’s plugged into your USB ports, the name found above may change. You can lock in a name, such as /dev/zwave, by following these instructions. -

    - -

    Events

    - -

    Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):

    - -
    - 
    # Example configuration.yaml automation entry
-automation:
-  - alias: Turn on Desk light
-    trigger:
-      platform: event
-      event_type: zwave.scene_activated
-      event_data:
-        entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
-        scene_id: 11
-
    -
    -
    - -

    The entity_id and scene_id of all triggered events can be seen in the console output.

    - -

    Services

    - -

    The Z-Wave component exposes four services to help maintain the network.

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    ServiceDescription
    add_nodePut the zwave controller in inclusion mode. Allows one to add a new device to the zwave network.
    remove_nodePut the zwave controller in exclusion mode. Allows one to remove a device from the zwave network.
    heal_networkTells the controller to “heal” the network. Bascially asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing.
    soft_resetTells the controller to do a “soft reset”. This is not supposed to lose any data, but different controllers can behave differently to a “soft reset” command.
    test_networkTells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked “presumed dead”.
    - -

    The soft_reset and heal_network commands can be used as part of an automation script
    -to help keep a zwave network running relliably. For example:

    - -
    - 
    # Example configuration.yaml automation entry
-automation:
-  - alias: soft reset at 2:30am
-    trigger:
-      platform: time
-      after: '2:30:00'
-    action:
-      service: zwave.soft_reset
-
-  - alias: heal at 2:31am
-    trigger:
-      platform: time
-      after: '2:31:00'
-    action:
-      service: zwave.heal_network
-
    -
    -
    - -

    Device Specific Notes & Configuration

    - -
    Aeon Minimote
    - -

    Here’s a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into automation.yaml.

    - -
    - 
    - alias: Minimote Button 1 Pressed
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 1
-
-- alias: Minimote Button 1 Held
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 2
-
-- alias: Minimote Button 2 Pressed
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 3
-
-- alias: Minimote Button 2 Held
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 4
-
-- alias: Minimote Button 3 Pressed
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 5
-
-- alias: Minimote Button 3 Held
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 6
-
-- alias: Minimote Button 4 Pressed
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 7
-
-- alias: Minimote Button 4 Held
-  trigger:
-    platform: event
-    event_type: zwave.scene_activated
-    event_data:
-      entity_id: aeon_labs_minimote_1
-      scene_id: 8
-
    -
    -
    - -
    Aeotec MultiSensor 6
    - -

    In order for Home Assistant to recognize well the motion sensor, you will need to change its configuration from Basic Set (default) to Binary Sensor report. Currently there’s no way to do this in Home Assistant but you can use ozwcp (OpenZWave control panel), Domoticz or similar to do it

    diff --git a/getting-started/android/index.html b/getting-started/android/index.html index ffc92d1d9d..d2d7a0addc 100644 --- a/getting-started/android/index.html +++ b/getting-started/android/index.html @@ -160,6 +160,14 @@
  • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-action/index.html b/getting-started/automation-action/index.html index 43d7a55c01..3e29cf9d4f 100644 --- a/getting-started/automation-action/index.html +++ b/getting-started/automation-action/index.html @@ -206,6 +206,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-condition/index.html b/getting-started/automation-condition/index.html index 3e85f6d028..fafc5bfd3c 100644 --- a/getting-started/automation-condition/index.html +++ b/getting-started/automation-condition/index.html @@ -182,6 +182,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-create-first/index.html b/getting-started/automation-create-first/index.html index 9bee2a8a0a..03b6a79c5f 100644 --- a/getting-started/automation-create-first/index.html +++ b/getting-started/automation-create-first/index.html @@ -254,6 +254,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-examples/index.html b/getting-started/automation-examples/index.html index 6e36f019fa..113e19c903 100644 --- a/getting-started/automation-examples/index.html +++ b/getting-started/automation-examples/index.html @@ -202,6 +202,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-templating/index.html b/getting-started/automation-templating/index.html index 6b539cb454..b7e7c2e474 100644 --- a/getting-started/automation-templating/index.html +++ b/getting-started/automation-templating/index.html @@ -396,6 +396,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-trigger/index.html b/getting-started/automation-trigger/index.html index 8c924affe8..165d12043d 100644 --- a/getting-started/automation-trigger/index.html +++ b/getting-started/automation-trigger/index.html @@ -292,6 +292,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation-troubleshooting/index.html b/getting-started/automation-troubleshooting/index.html index 7e25636694..92ade397ba 100644 --- a/getting-started/automation-troubleshooting/index.html +++ b/getting-started/automation-troubleshooting/index.html @@ -162,6 +162,14 @@ INFO [homeassistant.components.automation] Initialized rule Rain is over
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/automation/index.html b/getting-started/automation/index.html index 31d22a2179..6c4b08007c 100644 --- a/getting-started/automation/index.html +++ b/getting-started/automation/index.html @@ -211,6 +211,14 @@ The difference between a condition and a trigger can be confusing as they are ve
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/autostart-macos/index.html b/getting-started/autostart-macos/index.html index 9828d5b8b0..59d9fe813a 100644 --- a/getting-started/autostart-macos/index.html +++ b/getting-started/autostart-macos/index.html @@ -170,6 +170,14 @@ Home Assistant has been uninstalled.
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/autostart-synology/index.html b/getting-started/autostart-synology/index.html index d3ff840ca4..ad928ad521 100644 --- a/getting-started/autostart-synology/index.html +++ b/getting-started/autostart-synology/index.html @@ -193,6 +193,14 @@ exec /bin/sh /volume1/homeassistant/hass-daemon start
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/autostart-systemd/index.html b/getting-started/autostart-systemd/index.html index 6891309763..d2a4844576 100644 --- a/getting-started/autostart-systemd/index.html +++ b/getting-started/autostart-systemd/index.html @@ -218,6 +218,14 @@ $ sudo systemctl start home-assistant@[your user]
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/autostart-upstart/index.html b/getting-started/autostart-upstart/index.html index cac3531265..96ead81787 100644 --- a/getting-started/autostart-upstart/index.html +++ b/getting-started/autostart-upstart/index.html @@ -171,6 +171,14 @@ $ sudo service hass-daemon stop
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/autostart/index.html b/getting-started/autostart/index.html index a992d7e913..be01b82736 100644 --- a/getting-started/autostart/index.html +++ b/getting-started/autostart/index.html @@ -155,6 +155,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/basic/index.html b/getting-started/basic/index.html index 5481fc63f1..f557a57d3c 100644 --- a/getting-started/basic/index.html +++ b/getting-started/basic/index.html @@ -197,6 +197,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/browsers/index.html b/getting-started/browsers/index.html index 54659a8238..c8affc3680 100644 --- a/getting-started/browsers/index.html +++ b/getting-started/browsers/index.html @@ -342,6 +342,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/configuration/index.html b/getting-started/configuration/index.html index c0735a195f..fc3a4efc79 100644 --- a/getting-started/configuration/index.html +++ b/getting-started/configuration/index.html @@ -164,6 +164,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/customizing-devices/index.html b/getting-started/customizing-devices/index.html index 576d018ad1..04869df94d 100644 --- a/getting-started/customizing-devices/index.html +++ b/getting-started/customizing-devices/index.html @@ -182,6 +182,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/devices/index.html b/getting-started/devices/index.html index aba9346b75..3348a22e5c 100644 --- a/getting-started/devices/index.html +++ b/getting-started/devices/index.html @@ -216,6 +216,14 @@ Each group exists of a name and a list of entity IDs. Entity IDs can be retrieve
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/index.html b/getting-started/index.html index 19b36f1843..02b0610ce8 100644 --- a/getting-started/index.html +++ b/getting-started/index.html @@ -190,6 +190,14 @@ $ hass --open-ui
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/installation-docker/index.html b/getting-started/installation-docker/index.html index 6daa655d3c..1914d8312e 100644 --- a/getting-started/installation-docker/index.html +++ b/getting-started/installation-docker/index.html @@ -174,6 +174,14 @@ When using boot2docker on OS X you are unable to map the local time to your Dock
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/installation-raspberry-pi-all-in-one/index.html b/getting-started/installation-raspberry-pi-all-in-one/index.html index e283f2c8bd..5a36884499 100644 --- a/getting-started/installation-raspberry-pi-all-in-one/index.html +++ b/getting-started/installation-raspberry-pi-all-in-one/index.html @@ -211,6 +211,14 @@
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/installation-raspberry-pi/index.html b/getting-started/installation-raspberry-pi/index.html index 688d55b6d7..6527d320b1 100644 --- a/getting-started/installation-raspberry-pi/index.html +++ b/getting-started/installation-raspberry-pi/index.html @@ -186,6 +186,14 @@ $ hass
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/installation-synology/index.html b/getting-started/installation-synology/index.html index afb2e0d124..0586a3f48b 100644 --- a/getting-started/installation-synology/index.html +++ b/getting-started/installation-synology/index.html @@ -397,6 +397,14 @@ That’s it… you’re all set to go

    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/installation-vagrant/index.html b/getting-started/installation-vagrant/index.html index 08e68f635f..2e13a050e2 100644 --- a/getting-started/installation-vagrant/index.html +++ b/getting-started/installation-vagrant/index.html @@ -241,6 +241,14 @@ The following instructions will assume you changed your working directory to be
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/installation-virtualenv/index.html b/getting-started/installation-virtualenv/index.html index 1604b96e1f..02bc4a8a14 100644 --- a/getting-started/installation-virtualenv/index.html +++ b/getting-started/installation-virtualenv/index.html @@ -292,6 +292,14 @@ $ sudo chown hass /srv/hass
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/presence-detection/index.html b/getting-started/presence-detection/index.html index 7ef5e36d65..bdd4fa202b 100644 --- a/getting-started/presence-detection/index.html +++ b/getting-started/presence-detection/index.html @@ -183,6 +183,14 @@ OwnTracks communicates directly with your MQTT broker, no data will pass through
    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/scripts-conditions/index.html b/getting-started/scripts-conditions/index.html index 2f7d54fa8b..2aed966cda 100644 --- a/getting-started/scripts-conditions/index.html +++ b/getting-started/scripts-conditions/index.html @@ -319,6 +319,14 @@ This allows you to mix several AND and OR conditions together.

    • Conditions
    • +
  • + Z-Wave + +
  • Autostart
      diff --git a/getting-started/scripts-service-calls/index.html b/getting-started/scripts-service-calls/index.html index fa41884340..6840d17c5c 100644 --- a/getting-started/scripts-service-calls/index.html +++ b/getting-started/scripts-service-calls/index.html @@ -216,6 +216,14 @@ Use the - Z-Wave - Home Assistant + Z-Wave USB Controllers - Home Assistant - + - + - - + + - + @@ -79,13 +79,11 @@
      -
      Edit this page on GitHub
      -

      - Z-Wave + Z-Wave USB Controllers

      @@ -106,28 +104,24 @@ Upon first run, the z-wave component will take time to initialize entities and e Works on Linux Works on Windows Works on OSX - Comments Aeotec Z-Stick Series 2 - X -   + ✓     Aeotec Z-Stick Series 5 - X -   + ✓     Razberry GPIO Module - X -   + ✓     @@ -142,11 +136,6 @@ Upon first run, the z-wave component will take time to initialize entities and e
    • Vera
    -

    Modifying Zwave Device Settings

    -

    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.

    - -

    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.

    - @@ -154,6 +143,82 @@ Upon first run, the z-wave component will take time to initialize entities and e + + diff --git a/getting-started/z-wave-device-specific/index.html b/getting-started/z-wave-device-specific/index.html new file mode 100644 index 0000000000..e79d10586e --- /dev/null +++ b/getting-started/z-wave-device-specific/index.html @@ -0,0 +1,280 @@ + + + + + + + + + + Z-Wave Device Specific Settings - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Z-Wave Device Specific Settings +

    +
    +
    + + +
    Aeon Minimote
    + +

    Here’s a handy configuration for the Aeon Labs Minimote that defines all possible button presses. Put it into automation.yaml.

    + +
    + 
    - alias: Minimote Button 1 Pressed
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 1
+
+- alias: Minimote Button 1 Held
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 2
+
+- alias: Minimote Button 2 Pressed
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 3
+
+- alias: Minimote Button 2 Held
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 4
+
+- alias: Minimote Button 3 Pressed
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 5
+
+- alias: Minimote Button 3 Held
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 6
+
+- alias: Minimote Button 4 Pressed
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 7
+
+- alias: Minimote Button 4 Held
+  trigger:
+    platform: event
+    event_type: zwave.scene_activated
+    event_data:
+      entity_id: aeon_labs_minimote_1
+      scene_id: 8
+
    +
    +
    + +
    Aeotec MultiSensor 6
    + +

    In order for Home Assistant to recognize well the motion sensor, you will need to change its configuration from Basic Set (default) to Binary Sensor report. Currently there’s no way to do this in Home Assistant but you can use ozwcp (OpenZWave control panel), Domoticz or similar to do it

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/getting-started/z-wave-settings/index.html b/getting-started/z-wave-settings/index.html new file mode 100644 index 0000000000..9b124005a2 --- /dev/null +++ b/getting-started/z-wave-settings/index.html @@ -0,0 +1,208 @@ + + + + + + + + + + Z-Wave Settings - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Z-Wave Settings +

    +
    +
    + + +

    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.

    + +

    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.

    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/getting-started/z-wave/index.html b/getting-started/z-wave/index.html new file mode 100644 index 0000000000..fb0473ff88 --- /dev/null +++ b/getting-started/z-wave/index.html @@ -0,0 +1,381 @@ + + + + + + + + + + Z-Wave - Home Assistant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    +
    + +
    + + + Home Assistant + +
    + +
    + +
    + +
    +
    +
    + + + +
    +
    + +
    + + +
    + + + + +
    +

    + Z-Wave +

    +
    +
    + + +

    Z-Wave integration for Home Assistant allows you to observe and control connected Z-Wave devices. Z-Wave support requires a supported Z-Wave USB stick to be plugged into the host.

    + +

    There is currently support for switches, lights and sensors. All will be picked up automatically after configuring this platform.

    + +

    Installation

    + +

    To allow Home Assistant to talk to your Z-Wave USB stick you will have to compile the OpenZWave library and install the related python-OpenZWave package. This can be done as follows. (Note: The Home Assistant docker image has support for Z-Wave built-in)

    + +

    Make sure you have the correct dependencies installed before running the script:

    + +
    + 
    $ sudo apt-get install cython3 libudev-dev python3-sphinx python3-setuptools
+
    +
    +
    + +

    Make sure you have at least version 0.23 of cython.

    + +
    + 
    $ sudo pip3 install --upgrade cython
+
    +
    +
    + +

    Then get the OpenZWave files and switch to the python3 branch:

    +

    Do not use root to build python-openzwave as it will surely fail.

    +
    + 
    $ git clone https://github.com/OpenZWave/python-openzwave.git
+$ cd python-openzwave
+$ git checkout python3
+$ PYTHON_EXEC=$(which python3) make build
+$ sudo PYTHON_EXEC=$(which python3) make install
+
    +
    +
    +

    +Instead of make install, you can alternatively build your own python-openzwave package which can be easily uninstalled: + +$ sudo PYTHON_EXEC=$(which python3) checkinstall --pkgname python-openzwave --pkgversion 1.0 --provides python-openzwave + +

    + +

    With this installation, your config_path needed below will resemble:

    + +
    + 
    /usr/local/lib/python3.4/dist-packages/libopenzwave-0.3.0b8-py3.4-linux-x86_64.egg/config
+
    +
    +
    + +

    Configuration

    + +
    + 
    # Example configuration.yaml entry
+zwave:
+  usb_path: /dev/ttyUSB0
+  config_path: /usr/local/share/python-openzwave/config
+  polling_interval: 60000
+  customize:
+    sensor.greenwave_powernode_6_port_energy_10:
+        polling_intensity: 1
+
    +
    +
    + +

    Configuration variables:

    + +
      +
    • usb_path (Required): The port where your device is connected to your Home Assistant host.
      • +
    • config_path (Optional): The path to the Python Open Z-Wave configuration files.
      • +
    • autoheal (Optional): Allows disabling auto ZWave heal at midnight. Defaults to True.
      • +
    • polling_interval (Optional): The time period in milliseconds between polls of a nodes value. Be careful about using polling values below 30000 (30 seconds) as polling can flood the zwave network and cause problems.
      • +
    • customize (Optional): This attribute contains node-specific override values: +
        +
      • polling_intensity (Optional): Enables polling of a value and sets the frequency of polling (0=none, 1=every time through the list, 2-every other time, etc). If not specified then your device will not be polled.
        • +
      +
      • +
    + +

    To find the path of your Z-Wave stick, run:

    + +
    + 
    $ ls /dev/ttyUSB*
+
    +
    +
    + +

    Or, on some other systems (such as Raspberry Pi), use:

    + +
    + 
    $ ls /dev/ttyACM*
+
    +
    +
    + +

    +Depending on what’s plugged into your USB ports, the name found above may change. You can lock in a name, such as /dev/zwave, by following these instructions. +

    + +

    Events

    + +

    Some devices can also trigger scene activation events, which can be used in automation scripts (for example the press of a button on a wall switch):

    + +
    + 
    # Example configuration.yaml automation entry
+automation:
+  - alias: Turn on Desk light
+    trigger:
+      platform: event
+      event_type: zwave.scene_activated
+      event_data:
+        entity_id: zwaveme_zme_wallcs_secure_wall_controller_8
+        scene_id: 11
+
    +
    +
    + +

    The entity_id and scene_id of all triggered events can be seen in the console output.

    + +

    Services

    + +

    The Z-Wave component exposes four services to help maintain the network.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ServiceDescription
    add_nodePut the zwave controller in inclusion mode. Allows one to add a new device to the zwave network.
    remove_nodePut the zwave controller in exclusion mode. Allows one to remove a device from the zwave network.
    heal_networkTells the controller to “heal” the network. Bascially asks the nodes to tell the controller all of their neighbors so the controller can refigure out optimal routing.
    soft_resetTells the controller to do a “soft reset”. This is not supposed to lose any data, but different controllers can behave differently to a “soft reset” command.
    test_networkTells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked “presumed dead”.
    + +

    The soft_reset and heal_network commands can be used as part of an automation script
    +to help keep a zwave network running relliably. For example:

    + +
    + 
    # Example configuration.yaml automation entry
+automation:
+  - alias: soft reset at 2:30am
+    trigger:
+      platform: time
+      after: '2:30:00'
+    action:
+      service: zwave.soft_reset
+
+  - alias: heal at 2:31am
+    trigger:
+      platform: time
+      after: '2:31:00'
+    action:
+      service: zwave.heal_network
+
    +
    +
    + + +
    + + +
    + + + + +
    +
    + + + + + + \ No newline at end of file diff --git a/sitemap.xml b/sitemap.xml index 1740f128b8..1c4145e9da 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -458,6 +458,18 @@ https://home-assistant.io/getting-started/yaml/ + + https://home-assistant.io/getting-started/z-wave-controllers/ + + + https://home-assistant.io/getting-started/z-wave-device-specific/ + + + https://home-assistant.io/getting-started/z-wave-settings/ + + + https://home-assistant.io/getting-started/z-wave/ + https://home-assistant.io/blog/categories/website/ @@ -1547,9 +1559,6 @@ https://home-assistant.io/topics/state_object/ - - https://home-assistant.io/topics/z-wave/ - https://home-assistant.io/topics/splitting_configuration/ @@ -1750,26 +1759,26 @@ https://home-assistant.io/demo/frontend.html - 2016-06-08T15:56:39+00:00 + 2016-06-09T05:09:15+00:00 https://home-assistant.io/demo/index.html - 2016-06-08T15:56:39+00:00 + 2016-06-09T05:09:15+00:00 https://home-assistant.io/googlef4f3693c209fe788.html - 2016-06-08T15:56:39+00:00 + 2016-06-09T05:09:15+00:00 https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html - 2016-06-08T15:56:39+00:00 + 2016-06-09T05:09:15+00:00 https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html - 2016-06-08T15:56:39+00:00 + 2016-06-09T05:09:15+00:00 https://home-assistant.io/static/mdi-demo.html - 2016-06-08T15:56:39+00:00 + 2016-06-09T05:09:15+00:00 diff --git a/topics/index.html b/topics/index.html index de41660954..afc399752f 100644 --- a/topics/index.html +++ b/topics/index.html @@ -109,9 +109,6 @@

  • Templating

    • -
  • -

    Z-Wave

    -