From 0a9f4d63f899f30407c35fa5091782f8dfe71342 Mon Sep 17 00:00:00 2001 From: Nicko van Someren Date: Mon, 2 Aug 2021 06:44:23 -0600 Subject: [PATCH] Document change to Lutron button events for un-named buttons (#18650) --- source/_integrations/lutron.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/lutron.markdown b/source/_integrations/lutron.markdown index c9c4f87e8b7..9bda0f6c3ba 100644 --- a/source/_integrations/lutron.markdown +++ b/source/_integrations/lutron.markdown @@ -63,7 +63,7 @@ It is recommended to assign a static IP address to your main repeater. This ensu 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 `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`. If the button has not been assigned a name by the Lutron system installer then the button will have a name of "Unknown Button". In this case the `id` will be suffixed with the underlying Lutron button number and will be of the form `kitchen_keypad_unknown_button_1`. The `action` attribute varies depending on the button type.