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-19 15:26:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document Lutron RadioRA2 button events (#8164)

Browse Source 
* Add Lutron binary sensor

* Fix typo in date

* Buttons now fire events instead of showing up as binary sensors

* Fix grammar error

* Rename "event" attribute to "action"
This commit is contained in:
koreth 2019-01-20 12:23:22 -08:00 committed by Martin Hjelmare
parent a0ca2c1df5
commit 35e9dcc379
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
source/_components/lutron.markdown
View File

@ -50,3 +50,15 @@ password:
<p class='note'>
It is recommended to assign a static IP address to your main repeater. This ensures that it won't change IP addresses, so you won't have to change the `host` if it reboots and comes up with a different IP address.
</p>
## {% linkable_title Keypad buttons %}
Individual buttons on keypads are not represented as entities. Instead, they fire events called `lutron_event` whose payloads include `id` and `action` attributes.
The `id` attribute includes the name of the keypad and the name of the button, normalized the same way entity names are. For example, if the keypad is called "Kitchen Keypad" and the button is called "Dinner" the event's `id` will be `kitchen_keypad_dinner`.
The `action` attribute varies depending on the button type.
For raise/lower buttons (dimmer buttons, shade controls, etc.) there will be two values, `pressed` and `released`, fired when the button is pressed and when it's released, respectively.
For single-action buttons (scene selection, etc.), `action` will be `single`, and there will only be one event fired. This is a limitation of the Lutron controller which doesn't give Home Assistant any way of knowing when a single-action button is released.