diff --git a/source/_components/lutron.markdown b/source/_components/lutron.markdown
index 66960face43..33f1e8f62fb 100644
--- a/source/_components/lutron.markdown
+++ b/source/_components/lutron.markdown
@@ -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.