jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-16 22:06:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Feature/central scene documentation (#3288)

Browse Source 
* Updating scene_activated to include scene_data

* Adding note about CentralScene

* Adding note about zwcfg

* Removing home seer notes and removing technical information

* Adding HomeSeer specific notes.

* Going back to pre-k to learn punctuation

Also tweaking a few bit of the examples and a few other silly mistakes

* Removing level extension from the zwave item
This commit is contained in:
Addo Solutions 2017-09-01 15:41:46 -04:00 committed by Pascal Vizeli
parent 4e6d53e331
commit b6e145f3cf
2 changed files with 43 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
source/_docs/z-wave.markdown
View File

@ -180,8 +180,25 @@ automation:
scene_id: 11
```
Some devices (like the HomeSeer wall switches) allow you to do things like double, and triple click the up and down buttons and fire an event. These devices will also send `scene_data` to differentiate the events. This is an example of double clicking the on/up button:
```yaml
# Example configuration.yaml automation entry
automation
- alias: 'Dining room dimmer - double tap up'
trigger:
- event_type: zwave.scene_activated
platform: event
event_data:
entity_id: zwave.dining_room_cans
scene_id: 1
scene_data: 3
```
The *object_id* and *scene_id* of all triggered events can be seen in the console output.
For more information on HomeSeer devices and similar devices, please see the [device specific page](https://home-assistant.io/docs/z-wave/device-specific/#homeseer-switches).
### {% linkable_title Services %}
The `zwave` component exposes multiple services to help maintain the network.

26
source/_docs/z-wave/device-specific.markdown
View File

@ -115,3 +115,29 @@ Here's a handy configuration for the Aeon Labs Minimote that defines all possibl
entity_id: zwave.aeon_labs_minimote_1
scene_id: 8
```
##### {% linkable_title HomeSeer Switches %}
For the HomeSeer devices specifically, you may need to update the `COMMAND_CLASS_CENTRAL_SCENE` for each node in your `zwcfg` file with the following:
```xml
<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="4" innif="true" scenecount="0">
<Instance index="1" />
<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="2" />
<Value type="int" genre="user" instance="1" index="1" label="Top Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
<Value type="int" genre="user" instance="1" index="2" label="Bottom Button Scene" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
</CommandClass>
```
Below is a table of the action/scenes for the HomeSeer devices (as a reference for other similar devices):
**Action**|**scene\_id**|**scene\_data**
:-----:|:-----:|:-----:
Single tap on|1|0
Single tap off|2|0
Double tap on|1|3
Double tap off|2|3
Triple tap on|1|4
Triple tap off|2|4
Tap and hold on|1|2