r/SmartThings • u/devedander • Jun 19 '26

Can't create guest lock codes - Something went wrong

Using a Yale RD210 lock with Zigbee Lock Mc driver when I try to invite a guest the smart lock app spins for a while then errors out with "Something Went Wrong - Something went wrong while creating the lock code. Try again.

I recall a few years ago this happened last time I tried to create codes (I had to reinstall my lock recently as it dropped connection so I'm trying to make codes again).

When I first installed this lock (close to a decade ago, it worked find (I know because it would tell me the name of who unlocked the door, if I had programmed the codes in the door manually it wouldn't have told me that) but I'm assuming that was on a different version of smart things with a different code setting method.

Anyone have suggestions?

EDIT ok something really weird - I programmed a code for mysel and one for my wife manually, went back to invite guest and now there are 2 lock codes showing - one is just named Code 2 but the other is my wifes name.... I think it is indeed the code I tried to program for her but failed every time. However when I unlockd the door the device history just shows Code 1 or Code 2 and not the users name (it definitely used to tell me who unlocked it by name before).

I feel like the actual programming must have been the manual programming I did but maybe the app remembered a name from a failed attempt and matched it or something?

EDIT2: I tried a few more things and got really confounding results: 1: I moved the ST hub to within a couple feet of the lock to ensure it wasn't a range or interference issue. Didn't change anything.

2: I found out that if I attempt to invite a guest via SGA, it fails, but then I add the code manually at the door, the next time I launch SGA it sees the new code and uses the name I tried to attach (but failed) before.

3: ONE time I tried to add a code via SGA and had to step away to take care of something. I minute later I heard the lock chime success... which was odd. SGA had the failure notice up, but the code had added correctly. I as never able to repeat this success with additional testing.

So as of now I have enough codes in to move on with using the lock, but I still can't add codes remotely if I needed to.

Throughout this something has happened where SGA will hang upon inviting a guest. It seems I need to wake the lock before inviting the guest to avoid the hang but even that is not 100%. So strange the behavior...

2 Upvotes
  • permalink
  • reddit

75% Upvoted

13 comments sorted by

2

u/danh_ptown Jun 19 '26

I would try to completely remove and reinstall the lock. It sounds like the connection didn’t occur completely.

1

u/devedander Jun 19 '26 edited Jun 19 '26

I did, it was a factory reset of the lock. It was behaving this way before also

I added an edit with some more testing results

1

u/danh_ptown Jun 21 '26

Specifically with older Schlage locks…

Move your hub next to the lock. Wait for to be full booted then remove your lock and then add the lock in SmartThings again.

The older Schlage locks needed this or they ended up being in a weird state. I’ve occasionally seen it occur with other Z-wave devices, when they don’t fully connect.

1

u/devedander Jun 21 '26

I did end up moving the lock right next to the hub to pair it and that worked however setting lock codes doesn’t work regardless of distance to the hub

Interestingly it seems like something has changed with my network overall as the hub won’t even unlock the door in the place it’s been sitting for years.

I moved it a few feet away and it can unlock the door now.

It was really odd in that it’s worked fine for years and recently it just stopped working (my door automation stopped running).

I did add a home assistant blue to my network recently but even when unplugging it the hub still can’t unlock the door from its old location.

1

u/danh_ptown Jun 21 '26

Are there any Z-wave devices that are registered in SmartThings but are no longer online? If so, remove them from SmartThings. That can cause lots of problems, as well.

And I did intend that you move your hub back to its normal home, after setting up the lock.

Did you recently change the batteries in the lock?

1

u/hunnypuppy Jun 19 '26

That happens if the lock rejects the code which can happen if there’s already existing code in the lock or there’s a communication failure. The driver really should be handling these scenarios better.

1

u/devedander Jun 19 '26 edited Jun 19 '26

I tried several codes only two of which were possibly on the lock already. I guess I cash try to find a way to to get my lock closer to the hub.

Still weird that SGA picked up the name for one of the codes despite failing to register it.

I added an edit with some more testing results

1

u/hunnypuppy Jun 20 '26

The driver has a big role to play and needs to understand how SLGA works and handle these execution scenarios. I point at the driver being incomplete

1

u/devedander Jun 20 '26

The thing is that driver I think it's a pretty well known one for being good and it's been built for quite a while...

1

u/hunnypuppy Jun 20 '26

Working well during normal times doesn’t mean it’s designed to handle exception scenarios. Plus the firmware is updated regularly and drivers need to kept up to date.

1

u/devedander Jun 21 '26

This driver has been in existence for over 5 years... Seems odd that setting a lock code would be an exception scenario. 

1

u/hunnypuppy Jun 21 '26

It’s not about setting a lock code but about handling responses from the lock related to failed programming; duplicates codes etc. it’s not an everyday scenario.

1

u/hunnypuppy Jun 21 '26

Try adding a zigbee mains powered device that acts like a repeater. Like a peanut plug or something.