Aqara Illuminance Sensor T1 - lux not updating

Hi everyone,

I am trying to get my new Aqara Illuminance Sensor T1 running.
I’m currently using the Zigbee Illuminance Sensor (2024-10-10T18), but the LUX is not changing at all, no matter how close I am holding it to a light. Detection frequency is set to 5 sec. Shall I use another driver (which one)? :thinking:

Device Profile / Name:
battery-illuminance-aqara

Model:
lumi.sen_ill.agl01

I was also trying to search the Smartthings Forum, but only found old articles (like this one) which didn’t help.

Thanks in advance!

Hi, mine is working fine since then, using same driver than you, as you read already in the old post i had the same issue, it was resolved by connecting the Light Sensor to an Aqara hub, then deleted and paired with smartthings hub again.

1 Like

Thanks for sharing! But I don’t have a friend with Aqara hub nearby. :wink:
Is there any other solution like buying an Aqara hub?

Have you tried pulling the battery out and putting it back in? How about removing and rejoining the sensor?

I have two of the older versions of this sensor, and I’ve had to rejoin them before, but I am using my own Edge driver though.

Yes, tried it with a new battery’s, too, @johncostantelo. Removed it from ST and added it - no difference.
Maybe any alternative driver available?

Hi @Frank_n_stein ,

You’re more than welcome to try my Edge driver here:

https://bestow-regional.api.smartthings.com/invite/oxl4AXxvwj13

It doesn’t have battery reporting, and there’s no adjustment for reporting interval, but i can honestly say that I’m well past year 2 on the original batteries and working great.

My version is an exact copy of ST’s from a while back, with the only change being to address fingerprints.

Thanks @johnconstantelo ! I’ll try it out!

1 Like

Not sure if this is related, but three of my Homeseer sensors intermittently stop reporting lux. Changing the driver to the default Z wave one and back on each sensor usually solves the issue. Neither Homeseer nor ST has provided any suggestions except to re pair the sensor, which only worked for a few months. The fact that the timing for their loss of connectivity make me suspect their is a systematic issue, but so far no luck chasing it down.

Somehow my issue got solved when I removed and added the Sensor again. :white_check_mark:
Thanks for your help anyways!

1 Like