diff --git a/atom.xml b/atom.xml index 131e421022..cb9555f406 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
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 or module to be plugged into the host.
-There is currently support for climate, covers, lights, locks, sensors, switches and thermostats. All will be picked up automatically after configuring this platform.
+There is currently support for climate, covers, lights, locks, sensors, switches, and thermostats. All will be picked up automatically after configuring this platform.
As of version 0.45, Home Assistant automatically installs python-openzwave from PyPI as needed.
There is one dependency you will need to have installed ahead of time:
@@ -92,7 +92,7 @@Configuration variables:
"0x01,0x02..."
used in order to connect securely to compatible devices."0x01,0x02..."
used in order to connect securely to compatible devices.$ ls /dev/ttyUSB*
Or, if there is no result try to find detailed USB connection info with:
+Or, if there is no result, try to find detailed USB connection info with:
$ dmesg | grep USB
To add a Z-Wave device to your system, go to the Z-Wave panel in the Home Assistant frontend and click the Add Node button in the Z-Wave Network Management card. This will place the controller in inclusion mode, after which you should activate your device to be included by following the instructions provided with the device.
-Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devices to the network using their own contol buttons. This method should be avoided as it is prone to errors. Devices added to the Z-Wave network using this method may not function well. +Some Z-Wave controllers, like Aeotec ZW090 Z-Stick Gen5, have ability to add devices to the network using their own contol buttons. This method should be avoided as it is prone to errors. Devices added to the Z-Wave network using this method may not function well.
Security Z-Wave devices require a network key before being added to the network using the Add Secure Node button in the Z-Wave Network Management card. You must set the network_key configuration variable to use a network key before adding these devices.
@@ -147,7 +147,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devicHome Assistant will trigger a event when the Z-Wave network is complete. Meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery powered devices on the network.
+Home Assistant will trigger an event when the Z-Wave network is complete, meaning all of the nodes on the network have been queried. This can take quite some time, depending on wakeup intervals on the battery-powered devices on the network.
- alias: Z-Wave network is complete
trigger:
platform: event
@@ -155,7 +155,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
Home Assistant will trigger a event when the Z-Wave network is ready for use. Between zwave.network_start
and zwave.network_ready
Home Assistant will feel sluggish when trying to send commands to Z-Wave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered all awake nodes have been queried and sleeping nodes will be queried when they awake.
Home Assistant will trigger an event when the Z-Wave network is ready for use. Between zwave.network_start
and zwave.network_ready
Home Assistant will feel sluggish when trying to send commands to Z-Wave nodes. This is because the controller is requesting information from all of the nodes on the network. When this is triggered, all awake nodes have been queried and sleeping nodes will be queried when they awake.
- alias: Z-Wave network is ready
trigger:
platform: event
@@ -163,7 +163,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
Home Assistant will trigger a event when the Z-Wave network is set up to be started.
+Home Assistant will trigger an event when the Z-Wave network is set up to be started.
- alias: Z-Wave network is starting
trigger:
platform: event
@@ -171,7 +171,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
Home Assistant will trigger a event when the Z-Wave network stopping.
+Home Assistant will trigger an event when the Z-Wave network is stopping.
- alias: Z-Wave network is stopping
trigger:
platform: event
@@ -179,7 +179,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
Home Assistant will trigger a event when command_class_basic changes value on a node. This can be virtually anything, so tests have to be made to determine what value equals what. You can use this for automations.
+Home Assistant will trigger an event when command_class_basic changes value on a node. This can be virtually anything, so tests have to be made to determine what value equals what. You can use this for automations.
Example:
- alias: Minimote Button Pressed
trigger:
@@ -192,7 +192,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
The object_id and basic_level of all triggered events can be seen in the console output.
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):
+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
@@ -225,7 +225,7 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
cancel_command
- Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decides you are not going to do it, then this must be used to stop the inclusion/exclusion command.
+ Cancels a running Z-Wave command. If you have started a add_node or remove_node command, and decide you are not going to do it, then this must be used to stop the inclusion/exclusion command.
change_association
@@ -265,11 +265,11 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
remove_failed_node
- Remove a failed node from the network. The Node should be on the Controllers Failed Node List, otherwise this command will fail.
+ Remove a failed node from the network. The Node should be on the controller’s Failed Node List, otherwise this command will fail.
replace_failed_node
- Replace a failed device with another. If the node is not in the controller’s failed nodes list, or the node responds, this command will fail.
+ Replace a failed device with another. If the node is not in the controller’s Failed Node List, or the node responds, this command will fail.
reset_node_meters
@@ -277,11 +277,11 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
set_config_parameter
- Let’s the user set a config parameter to a node. NOTE: Use string for list values. For all others use integer.
+ Lets the user set a config parameter to a node. NOTE: Use string for list values. For all others use integer.
soft_reset
- Tells 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.
+ Tells 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.
start_network
@@ -293,11 +293,11 @@ Some Z-Wave controllers like Aeotec ZW090 Z-Stick Gen5 have ability to add devic
test_network
- Tells 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”.
+ Tells 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 Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a heal_network
at midnight. This is a configuration option for the zwave
component, the option defaults to true
but can be disabled by setting autoheal
to false. Using the soft_reset
function with some Z-Wave controllers can cause the Z-Wave network to hang. If you’re having issues with your Z-Wave network try disabling this automation.
+The soft_reset
and heal_network
commands can be used as part of an automation script to help keep a Z-Wave network running reliably as shown in the example below. By default, Home Assistant will run a heal_network
at midnight. This is a configuration option for the zwave
component. The option defaults to true
but can be disabled by setting autoheal
to false. Using the soft_reset
function with some Z-Wave controllers can cause the Z-Wave network to hang. If you’re having issues with your Z-Wave network, try disabling this automation.
# Example configuration.yaml automation entry
automation:
- alias: soft reset at 2:30am
diff --git a/sitemap.xml b/sitemap.xml
index 243d8a245a..07bebf5d48 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -3823,62 +3823,62 @@
https://home-assistant.io/demo/frontend.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/index.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-event.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-info.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-service.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-state.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-dev-template.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-history.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-iframe.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-logbook.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/demo/panels/ha-panel-map.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/googlef4f3693c209fe788.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:30+00:00
https://home-assistant.io/static/fonts/roboto/DESCRIPTION.en_us.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:31+00:00
https://home-assistant.io/static/fonts/robotomono/DESCRIPTION.en_us.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:31+00:00
https://home-assistant.io/static/mdi-demo.html
-2017-08-04T06:36:47+00:00
+2017-08-04T15:05:31+00:00