-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
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.
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
Lutron Diva doesn't generate lutron_caseta_button_event #84338
Comments
Hey there @cdheiser, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) lutron documentation |
Tjis is filed under the wrong component. lutron supports RadioRA2 (and Homeworks to some degree). This belongs in the lutron_caseta integration. |
@home-assistant unassign lutron |
Hey there @swails, @bdraco, @danaues, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) lutron_caseta documentation |
New to home assistant community, please LMK if this isn't kosher. Could I put a bounty on this fix? |
Thank you for reaching out. We use GitHub for tracking issues, not for tracking feature requests. If you want to suggest a feature, you should try our Community Forum: Feature Requests. If you have additional questions, feel free to join our Discord chat server. Thanks! 👍 |
The problem
It seems like this event should trigger for any lutron device? I can listen to it and see events from caseta pico remotes, but not diva dimmers.
What version of Home Assistant Core has the issue?
Home Assistant 2022.11.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Lutron
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: