U100 Lock beta issues

Aqara Products
,
1

Firmware version: 3.0.0_0031
Hub version: 4.3.6_0029.0013
Door Status Sensing is on

On the 29th of June, I updated both the lock and hub. I have the lock bound to HomeKit. Since then I’ve observed a few issues:

  • A couple of times, when placing my phone or watch at the lock, the lock fails to unlock. NFC works, and the phone shows the home key card and the tick for success, but the lock doesn’t actually unlock. I end up having to unlock with a code, which does work.

  • HomeKit shows the wrong status. It says the door is unlocked, when it’s actually locked. This is alarming when I’m not at home. If I toggle it to “lock” again, nothing happens. If I then unlock it, the door does unlock, and I am able to lock it again. But it’s not great that the wrong status shows up to begin with.

  • The door status in the “Aqara” app shows up as “Unknown”. When it’s in this state, I cannot tell what state the door is in, I cannot lock it, I cannot unlock it except by code

I didn’t have any of these issues in the previous version. I upgraded in the hopes the door status sensing would be better than the previous version, but instead it is worse, and has other bugs to go with it. Is it possible to revert beta versions?

1 Like
2

You can try to do the calibration again, see if the issue still persist

3

You can try to do the calibration again, see if it would work

4

I’ve tried that. It keeps happening. I think it gets into this state when it thinks the door has been closed and auto locks while it’s actually still open (sometimes holding the door open, or slightly closing it and reopening it causes this to happen). I then manually unlock and close the door. Once this is done, it’s confused about whether the door is open or not, and things don’t work quite right. But this did not happen with earlier firmware versions.