I've been using an Aqara U400 lock with the Matter Advanced Bridge without any problems. I usually just walk up to the lock with my phone and it automatically opens with UWB for the perfect hands free experience. Today, it didn't open with UWB and I opened the lock with a fingerprint scan. Since this occurred, the Hubitat is not showing any locked / unlocked status updates though it shows the lock as online and I can send commands to lock and unlock it.
UWB is working fine again after the one glitch but the feedback problem continues even after rebooting the Hubitat. I also tried doing a Refresh and running a Re Subscribe on the device page but that didn't help. Apple Home still gets feedback from the lock so this is just something on the Hubitat side of things.
Any ideas on how to get feedback working again would be greatly appreciated.
Please check first the status of your HE hub Matter interface. Go to Settings -> Matter Details.
Does the Aqara U400 have a green checkmark in the list?
In the example below, we see the ALPSTUGA device being offline, and the next two devices with a green checkmark and filled-in IDs and IPv6 addresses:
On the MAB parent device web page - click on the Ping() button. Observe the rtt (Round-Trip Time) attribute - does it show a nimber (time in milliseconds) or a 'timeout' error?
@jbasen I've been using my Aqara U400 with MAB for a few months now and have never run into the issue you describe. You've got something out of sync somehow.
I'm sure @kkossev will help get everything sorted.
There was a checkbox next to the Aqara Lock in the list of Matter devices
I disabled and re-enabled Matter 1.5. This didn't change anything related to the Aqara lock but it did fix one other Matter device whose status was a red X.
Ping worked fine
networkStatus is Online
I can still lock/unlock the U400 using the buttons on the device page or physically lock/unlock the U400 but the lock's status on the device page stays "closed".
My last resort is to remove and re-add the device. However, this is a last resort for me. The lock is linked to a third-party system through the MakerAPI and re-adding it will change its ID. That will require changing the third-party system's code. This is something I can't do remotely so if, for example, I'm traveling and my wife is home then I can't fix the problem for her. For this reason, I'm trying to find an alternative solution.
Thanks @jkudave . I'm on firmware 3.1.1.0 and, unfortunately, pulling the battery didn't help. I didn't think this would work, but was certainly willing to try, because status updates to Apple Home work perfectly. It is just the Hubitat that has the problem.
The successful ping and online network status show that Hubitat can still reach the U400 lock. Since lock and unlock commands work, the command path is also fine. Apple Home receiving the correct status narrows this down to the state-reporting path for the U400 endpoint in Matter Advanced Bridge, rather than the lock firmware, battery, or general Matter connectivity.
Please run _ DiscoverAll() again from the Matter Advanced Bridge parent device. It will refresh the endpoint information and subscriptions while reusing the existing lock child device, so its Hubitat device ID will not change.
Then enable debug logging on the parent device, press Refresh, and operate the lock. In the debug logs, look for an incoming Door Lock cluster 0101 LockState attribute 0000 report for the lock endpoint, followed by it being forwarded to the lock child device. The parent<>child device structure makes the debugging a bit more complicated...
Removing and re-adding the device should remain the real last resort.
Thanks again for your help. I do have a follow-up question. I'm just wondering if there is a way to automate the process of fixing this kind of issue so the system would be self-repairing. I didn't see any errors so I'm not sure there is anything that can be done but I thought I would ask.
Thanks.
It remains unclear what caused this issue. I can think of two possible reasons: either accidentally clicking “Load All Defaults” or clicking “DiscoverAll” while the device was temporarily offline. The latter issue is already fixed in beta version 1.9.1. The discovery process will first ping the Matter device to ensure it is online before zeroing the device counts and subscriptions.
You can either manually update the package to the latest MAB version by performing a “Repair” from HPM, or stay on the current version if it has been working well for you.
