I’ve been testing the Lutron integration for the past couple of weeks an I can’t figure out how to get HA to stop this 50% dimming business. Whenever HA restarts, the next turn-on for any Lutron dimmer via any dashboard is 50%. It’s driving me crazy. As soon as I dim it up to 100%, then HA will toggle between 0% and 100%…until the next restart. If I use a Lutron scene to turn the light on, then it’s always at 100% (because all my Lutron scenes are programmed that way) and from that time onward HA will use 100% during a toggle.
Big thing #1: I know that Lutron switches are set to a default dim level; I am a Lutron integrator (in the loosest sense) and programmed in the default dim levels of all my dimmers when I first installed them 8yrs ago, and those levels persist power outages and stuff because 100% of Lutron programming is set to dim to 100% on toggle. This is literally an issue only with HA in the last 2 weeks of testing.
Big thing #2: I’ve looked around a ton and there are options I see for “setting default dim in programming”. I have like 5 dozen switches and definitely do not want to set a default level for each one; somewhere there is a global default in HA and that is what I’m trying to find. That is where the problem lies.
Thanks for picking this up on git. Managing github feature requests is not a tool in my toolbox right now. I still think that creating a configurable option as opposed to the hardcoded 50% level is still the most straightforward method which should be quite future-proof. The store-retrieve options are good as well although they seem much more complicated when the simple configurable default would suffice. The “if no value stored then just send a button press instead of level” would also work, I suppose, and would avoid the issue of level storage/retrieval.
Fwiw, while we’re figuring things out in the github pull request, I just edit the file to set the level to 255 instead of 255/2. I have to re-edit when there’s an update but it works for now
