-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
[Feature request]: print more debug info #108
Comments
hello! I'm on a phone now, but I'm pretty sure the |
Indeed it is. I mistakenly thought debug was the highest level. For reference, it outputs a constat stream of logs of this pattern
While trace does print the brightness wluma gets from the sensors, it does not print the actions taken. This would still be useful to have. |
Hi again, sorry I forgot to reply, |
Please describe your feature request
In the debug log (
RUST_LOG=debug
) it currently only prints the initial config and new data points (lux class, content(?) luma, brightness) which I find a bit lacking.For debugging, it'd be really useful to also see:
I had the case of GNOME's auto-brightness feature suddenly appearing and accidentally running two instances of wluma where brightness would change erratically. This would have been a lot easier to debug if the wluma instance I was looking at printed a line of debug info every time it actually took an action.
When setting up wluma, it's not obvious how to set up the lux "classes" (dim, normal, bright etc.) because you don't have a reference. You could start reading the device's output manually in addition to the debug log but this isn't necessarily trivially possible with webcam sources and even with iio sources it'd be really convenient to just have that info at that point in time.
The text was updated successfully, but these errors were encountered: