Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature/central scene documentation #3288

Merged
merged 7 commits into from Sep 1, 2017
Merged

Feature/central scene documentation #3288

Show file tree
Hide file tree
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
946e207
Updating scene_activated to include scene_data
AddoSolutions Aug 31, 2017
8f81594
Adding note about CentralScene
AddoSolutions Aug 31, 2017
06272f7
Adding note about zwcfg
AddoSolutions Aug 31, 2017
3d796db
Removing home seer notes and removing technical information
AddoSolutions Aug 31, 2017
4f78ac5
Adding HomeSeer specific notes.
AddoSolutions Aug 31, 2017
214a623
Going back to pre-k to learn punctuation
AddoSolutions Aug 31, 2017
b18412b
Removing level extension from the zwave item
AddoSolutions Aug 31, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
17 changes: 17 additions & 0 deletions source/_docs/z-wave.markdown
View file
Open in desktop
Expand Up @@ -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.diningroomcans_level
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leave off the "_level", as that's part of the value entity. The entity_id sent with the event would just be zwave.diningroomcans in this case.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are things I would have had to learn as I was actually implementing it. Thanks!

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.
Expand Down
26 changes: 26 additions & 0 deletions source/_docs/z-wave/device-specific.markdown
View file
Open in desktop
Expand Up @@ -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