Lutron is an American lighting control company. They have several lines of home automation devices that manage light switches/dimmers, occupancy sensors, HVAC controls, etc. The
lutron integration in Home Assistant is responsible for communicating with the main hub for these systems.
Presently, there’s only support for communicating with the RadioRA 2 Main Repeater and only handle light switches, dimmers, and seeTouch keypad scenes.
When configured, the
lutron integration will automatically discover the rooms and their associated switches/dimmers as configured by the RadioRA 2 software from Lutron. Each room will be treated as a separate group.
To use Lutron RadioRA 2 devices in your installation, add the following to your
configuration.yaml file using the IP address of your RadioRA 2 main repeater:
# Example configuration.yaml entry lutron: host: IP_ADDRESS username: lutron password: integration
The IP address of the Main Repeater.
The login name of the user. The user
lutronalways exists, but other users can be added via RadioRA 2 software.
The password for the user specified above.
integrationis the password for the always-present
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.
Individual buttons on keypads are not represented as entities. Instead, they fire events called
lutron_event whose payloads include
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
action attribute varies depending on the button type.
For raise/lower buttons (dimmer buttons, shade controls, etc.) there will be two values,
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.
Each full-width button on a Lutron SeeTouch, Hybrid SeeTouch, and Tabletop SeeTouch Keypad has an LED that can be controlled by Home Assistant. A service call of switch.turn_off or switch.turn_on against the appropriate LED entity will control the keypad LED.
Keep in mind that the Lutron system will also control the LED state independent of Home Assistant, according to the programming of the RadioRA2 system. This also means you can query LED states to determine if a certain scene is active, since the LED will have been illuminated by the RadioRA2 repeaters. This includes the “phantom” LEDs of Main Repeater Keypad buttons; even though there is no physical button or LED, the RadioRA2 system tracks the scenes and will “light” the LED that can be queried.
If a button is not programmed to control any lights or other devices in the RadioRA2 system but is given a name in the programming software, it will be available to fire events in Home Assistant. However, since there is no way to have a scene “active” on a button with no devices associated, the Main Repeater will automatically extinguish the keypad LED a few seconds after the button press. If you wish to have Home Assistant light the keypad LED after a button press, you will need to delay your service call to light the LED for several seconds, so it arrives after the Main Repeater has sent the command to turn it off.
This integration uses keypad programming to identify scenes. Currently, it works with seeTouch, hybrid seeTouch, main repeater, homeowner, Pico, and seeTouch RF tabletop keypads. The Lutron scene platform allows you to control scenes programmed into your SeeTouch keypads.
After setup, scenes will appear in Home Assistant using the area, keypad and button name.
Any configured Powr Savr occupancy sensors will be added as occupancy binary sensors. Lutron reports occupancy for an area, rather than reporting individual sensors. Sensitivity and timeouts are controlled on the sensors themselves, not in software.
- alias: "keypad button pressed notification" trigger: - platform: event event_type: lutron_event event_data: id: office_pico_on action: single action: - service: notify.telegram data: message: "pico just turned on!"