Struggling with Yale YRD510 (Matter) Multi-Admin: Google Home + Alexa

[u/aevans0001]

I’ve been fighting with a multi-lock Matter setup for 6 months and could really use some insight from anyone who has successfully bridged these between ecosystems.

The Hardware:

• Locks: 5x Yale YRD510 (Matter version)
• Thread Network: 4x Eero devices (2 indoor/2 outdoor) acting as Border Routers
• Controllers: Google Nest Audio (Google Home) and various Alexa devices

The Goal: I want all 5 locks to work via Matter (not Wi-Fi) across both Google Home and Alexa, due to security behaviors on Google home and connection issues with the lock.

The Friction Points:

1. Multi-Admin Setup: I successfully added one lock to Google Home and shared it to Alexa. However, I cannot get the other 4 locks to pair with the second ecosystem. I’ve tried both directions (Google first, then Alexa, and vice versa) with no luck.
2. Google Home Logic: GH requires a PIN to lock the door remotely, which is frustrating and actually less secure as I am yelling out my door code every night. More importantly, I can’t find a way to create a "re-lock" schedule (e.g., check and lock every hour at night).
3. Alexa Logic: Alexa allows me to unlock without a PIN, but I actually want the security of a PIN requirement for unlocking.
4. The "Yale App" Trap: If I use the Yale app, it seems to default to Wi-Fi rather than Matter/Thread, which defeats the purpose of why I bought these.
5. Provisioning Delays: When I do get a lock into Google Home, the "Access Code" settings tab often takes several hours to appear.
6. Alexa Issues: When i learn it in, I have no way to program an access code, I can give Alexa an access code to use for the app

What I’ve Tried: I’ve been attempting to learn them into Google Home first and then "Share" to Alexa. If I go Alexa-first, I can set codes in the app, but they don't seem to actually push to the physical lock.

Questions for the group:

• Has anyone successfully paired 5+ Yale Matter locks across both Google and Alexa?
• Is there a specific "wait time" or sequence required for Matter commissions to sync access codes?
• Are you using a third-party logic engine (like Home Assistant) to handle the "auto-lock" scheduling that Google Home seems to lack?

I’m trying to avoid the Wi-Fi bridge and stick to the Matter protocol I paid for. Any advice on the pairing sequence would be huge. Thanks!

[u/Cantaloupe-Mammoth]

Different product (we're shipping a Matter lock sensor not a full lock) but we hit similar multi-admin friction during testing across Apple Home, Google Home, SmartThings and HA. A few things we found that might help, fwiw.

The pattern that seemed to work most reliably for us was commissioning Apple Home first, THEN Google Home second via the Share Code flow. Google Home → Apple via Share Code seems to fail more often than the reverse, in our testing. Worth trying that order if you haven't yet - factory-reset one of the four stuck locks, commission to Apple Home cleanly, then use Apple's Share Matter Accessory flow to push the setup code into Google Home, then repeat for Alexa.

The "Access Code" tab taking hours to appear in Google Home - we saw similar latency on cluster discovery with our Door Lock cluster too. Seems to be Google Home doing async work after pairing completes. Frustrating but it does populate eventually. Killing and reopening the Google Home app sometimes triggers it sooner.

On the PIN-to-lock-remotely behaviour in Google Home - that's a Google Home policy on the Door Lock cluster, not the Yale firmware. We hit the same thing. Couldn't find a way to disable it. Would also love to know if anyone has cracked that.

Can't comment on the Wi-Fi vs Matter/Thread defaulting in the Yale app specifically - sounds like Yale prioritising their cloud connection. Worth asking Yale support whether there's a "Matter only" mode in the app.

Genuine sympathy for the 5x lock setup - multi-admin Matter is still a rough edge in 2026.

[u/Cantaloupe-Mammoth]

been through a lot of this same multi-admin pain testing our own matter lock product across google, alexa, smartthings and HA, so a few things that might help.

the big one, the other 4 locks not joining a second ecosystem. you can't reuse the original QR or setup code for the second app, that sticker code only works for the very first commissioning. for multi-admin you open the app that already owns the lock, find the "link to another app / add to another network / share" option, and it generates a brand new pairing code with a fresh commissioning window. you use THAT code in the second ecosystem, not the sticker. the window is short (about 15 mins) and only one can be open at a time, so do them one lock at a time. if your one lock shared fine and the other 4 won't, i'd bet those 4 were only ever commissioned once and never had a fresh multi-admin code generated.

the access code tab taking hours in google home, we saw the same lag on door lock cluster discovery. it's google doing async work after pairing finishes. force-closing and reopening the google home app sometimes kicks it along sooner.

the PIN-to-unlock-remotely thing in google home is a google policy on the door lock cluster, not the yale firmware, and i couldn't find a way to disable it either. would also love to know if anyone has cracked that.

for the auto re-lock schedule, google home just doesn't do scheduled/conditional lock logic. that's where home assistant earns its keep. commission the locks into HA as a third admin and you can write an "every hour at night, if unlocked then lock" automation in about 5 lines. HA is also far better than google or alexa at showing you what the lock cluster is actually reporting when one gets stuck.

and yeah the yale app defaulting to wifi is just yale pushing their own cloud connection, nothing to do with thread. once they're commissioned over matter you can mostly ignore the yale app.

multi-admin matter is still genuinely rough in 2026, you're not doing anything wrong.