home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.14k stars 29.81k forks source link

Lutron using default dim for all dimmers after HA reboot #122805

Open HobbiestGuy opened 1 month ago

HobbiestGuy commented 1 month ago

The Question:

Lutron integration turns on any dimmer to 49.80%. light.turn_on, homeassistant.turn_on produce same result. Confirmed it is from the integration. 2024-07-29 12:47:18.149 DEBUG (SyncWorker_17) [pylutron] Sending: #OUTPUT,75,1,49.80

Would you please add an item to the Options of the integration to set the variable for the initial dim level?

What version of Home Assistant Core has the issue?

2024.7.1

What was the last working version of Home Assistant Core?

2024.7.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Lutron

Link to integration documentation on our website

https://www.home-assistant.io/integrations/lutron/

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

home-assistant[bot] commented 1 month ago

Hey there @cdheiser, @wilburcforce, mind taking a look at this issue as it has been labeled with an integration (lutron) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `lutron` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign lutron` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


lutron documentation lutron source (message by IssueLinks)

wilburCforce commented 1 month ago

@HobbiestGuy this is by design. The Lutron integration protocol does not expose an ability to read the default level for a dimmer. The XML database does not contain the information either. So there is no way to see what the default level should be. As a result, a static value is provided that covers the masses. This should not come up that often. As you noted, it is only after a restart of HA and also only if you chose to use the on command in HA directly. Just change any automations to go to a specific dim level instead. The occasion to manually turn on a light via HA without a known dim level could be minimized.

HobbiestGuy commented 1 month ago

Thank you for the explanation, you have done a great job with this integration. Have you considered making that value a variable set in the integration options? I suspect a manual edit on my end isn't feasible, nor would I want to risk breaking something.

Very best regards, Tyson

On Mon, Jul 29, 2024, 4:34 PM wilburCforce @.***> wrote:

@HobbiestGuy https://github.com/HobbiestGuy this is by design. The Lutron integration protocol does not expose an ability to read the default level for a dimmer. The XML database does not contain the information either. So there is no way to see what the default level should be. As a result, a static value is provided that covers the masses. This should not come up that often. As you noted, it is only after a restart of HA and also only if you chose to use the on command in HA directly. Just change any automations to go to a specific dim level instead. The occasion to manually turn on a light via HA without a known dim level could be minimized.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/122805#issuecomment-2257184061, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJQBHKFMPP56JNYGQ4EETZ3ZO3GP3AVCNFSM6AAAAABLU6JQESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGE4DIMBWGE . You are receiving this because you were mentioned.Message ID: @.***>

wilburCforce commented 1 month ago

@HobbiestGuy I guess we could. Would you mind editing this original post to change it to that request? I can take it up next time I'm tinkering with this. It isn't a big change.

HobbiestGuy commented 1 month ago

You got it - thanks!

On Wed, Jul 31, 2024 at 4:06 PM wilburCforce @.***> wrote:

@HobbiestGuy https://github.com/HobbiestGuy I guess we could. Would you mind editing this original post to change it to that request? I can take it up next time I'm tinkering with this. It isn't a big change.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/122805#issuecomment-2261634469, or unsubscribe https://github.com/notifications/unsubscribe-auth/BJQBHKCVSP6M5KRKHQ4AKLDZPFUYTAVCNFSM6AAAAABLU6JQESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRRGYZTINBWHE . You are receiving this because you were mentioned.Message ID: @.***>