Federico Di Pierro

Thank you very much!

Can you share clightd output with the patch?

Moreover, can you share output of ``` udevadm info --all /dev/iio:device0 ``` ?

Can you add the "--all" flag to the udevadm command? Thanks!

> can this be the on you want ? Exactly, thanks! > ATTR{in_illuminance_input}=="0" > ATTR{in_illuminance_raw}=="0" These ones are the 2 udev ATTRibutes that Clightd uses; they are both 0 :/...

Well, it seems like iio-sensor-proxy actually uses similar logic as Clightd: * Checks "in_illuminance_{input,raw}": https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/blob/master/src/drv-iio-poll-light.c#L68 * Matching sensor type is `iio-poll-als` (that is the one you are using, given your...

Oh it seems like iio-sensor-proxy gives higher priority to iio-buffer-als devices than iio-poll-devices. Given that your als device exposes both, it surely uses iio-buffer-als and that is not supported by...

Ehy everyone, in https://github.com/FedeDP/Clightd/pull/102 i implemented support for iio buffer ALS sensor read. Can you test it? I unfortunately haven't got any ALS device :/

Hi! Thank you very much for testing! Yes, can you share clightd log and output of Sensor.Capture dbus method call?

What about: ``` busctl call org.clightd.clightd /org/clightd/clightd/Sensor/Als org.clightd.clightd.Sensor Capture "sis" "" 5 "" ``` ?