Open Atemu opened 3 months ago
hello! I'm on a phone now, but I'm pretty sure the trace
log level is printing exactly the info you are looking for, could you give it a go?
Indeed it is. I mistakenly thought debug was the highest level.
For reference, it outputs a constat stream of logs of this pattern
[2024-05-22T13:48:56Z TRACE wluma::predictor::controller] Prediction: 627 (lux: normal, luma: 0)
[2024-05-22T13:48:56Z TRACE wluma::als::iio] ALS (iio): normal (8)
[2024-05-22T13:48:56Z TRACE wluma::als::iio] ALS (iio): normal (8)
[2024-05-22T13:48:56Z TRACE wluma::predictor::controller] Prediction: 627 (lux: normal, luma: 0)
[2024-05-22T13:48:56Z TRACE wluma::als::iio] ALS (iio): normal (8)
[2024-05-22T13:48:56Z TRACE wluma::als::iio] ALS (iio): normal (8)
[2024-05-22T13:48:56Z TRACE wluma::predictor::controller] Prediction: 627 (lux: normal, luma: 0)
[2024-05-22T13:48:56Z TRACE wluma::als::iio] ALS (iio): normal (8)
[2024-05-22T13:48:56Z TRACE wluma::als::iio] ALS (iio): normal (8)
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, Prediction: 627
is the action being taken, wluma is writing the value 627
into your brightness raw file (with some smooth transition though).
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: