I have a u50 Smart lock if you ask Alexa the status it tells me there’s a problem
Quick question before anything else: do you have an Aqara Hub bound to this lock? Manual’s explicit on this one — Alexa and Google specifically need a hub in the mix. The Aqara Home app and HomeKit can talk to the U50 directly without one, so it’s real easy to get the lock fully working in the Aqara app, assume you’re done, and then have Alexa fail because it’s routing through a hub connection that was never set up.
If you don’t have a hub, that’s almost certainly it. If you do have one bound, tell me exactly what Alexa says when it reports the problem — “problem” is vague, and there’s a difference between “device unresponsive,” “low battery,” and a generic error. Screenshot if you can.
hi Outburstin,
the lock is bound to a m3 hub The name of the device in alexa is Front door lock
so if i say Alexa is the front door locked it will say Checking hang on something’s wrong with the front door lock so I’m not sure if it’s locked
but if you ask it to lock it or unlock it it will do it and it looks fine and all the apps and all the firmware is updated everywhere that the firmware could be updated And all my software for Alexa is also up to date And this problem just started over the weekend
Good info, that helps. The fact that lock/unlock commands work fine but the status check specifically fails tells me this isn’t a hub or lock problem — it’s probably the state-reporting side of the Alexa connection, not the command side. Those run through different channels even though they look like the same “talking to Alexa” thing.
Since this only started over the weekend and everything’s already updated, my first guess is a stale Alexa skill session rather than anything with the lock or the M3 itself. Couple things to try:
- In the Alexa app, go to the device page for “Front door lock” and see if there’s a “Troubleshoot” or “Forget device” prompt — Alexa sometimes surfaces the actual error there instead of the vague voice response.
- Unlink and re-link the Aqara skill in the Alexa app. This forces a fresh session/token, and stale tokens are a really common cause of “commands work, status doesn’t” specifically.
- Reboot the M3 hub itself — not the lock, the hub. That resets the connection to Alexa’s cloud without imacting your Aqara setup or data.
- Did you have any router, alexa, ISP outage, or anything like that over the weekend? Any of those could cause the stale Alexa session state issue.
hi I have tried everything that I can on my end as far as restarting everything or repairing the matters the matter devices and no matter what I do when you when you check the status with voice command the status is not coming back correctly but it looks fine everywhere else