bcutter
bcutter
Only if HA provides a service to start and stop debug logging (for single targets/integrations). Next to this there seems to be nothing which could get this going: https://community.home-assistant.io/t/add-services-to-start-stop-debug-logging-of-integrations/527021
> Oops. Just wanted to reply that there is a service to change debug logging for an integration without reloading. Which one? Where's more information on that service?
Perfect. That will solve the log leak for at least one important other issue I'm taking care of - and maybe even this one here in the next winter time....
Empty = device's auto mode should be replaced with a corresponding value (0-255). As simple as that. Screen brightness always has a value, it never is "nothing" so no need...
Open
I described everything in the OP. `unknown` is a magic state (like `unavailable`) out of the category "problematic". Using the device in screen brightness auto mode is not a problematic...
Only the fact the current implementation is documented does not mean it is a good implementation. Repeating myself again: UNKNOWN is a problematic state. System controlled screen brightness could be...
https://github.com/home-assistant/core/issues/84154#issuecomment-1674399988
https://github.com/home-assistant/core/issues/84154#issuecomment-1674399988
No one ever took a look at this in 3 months. So let's keep this open and wait another 3 months. Thanks bot.