Seam: Temporary Solution for Managing Lock Guest Codes (Jan 2023)

Hi ! Thanks for the reply. I’m using a Galaxy phone as 2FA indeed.

@Eduardo_Toro got it. 2FA via Samsung Galaxy is the one method we don’t currently support. I need to chat with the SmartThings folks on what it will take to support it. In the meantime, can you enable either the Google Authenticator or SMS 2FA option?


I got this set up and working with my Yale zwave lock through SmartThings, and while I was at it I connected my Yale Access account as well (I’m going to try their Airbnb integration once I get my new August wifi module for the lock). In anticipation of this, what will I be able to see and do through Seam with my Yale Access account?

1 Like

More or less the same things that can also be done with SmartThings (unlocking/locking the door, programming access codes, seeing entry events, etc…).

I think the main reason for non-API users to use Seam’s dashboard right now is that SmartThings’ deprecation of Groovy has taken away the UI everyone was dependent on for programming access codes. The replacement has issues…etc. Our API dashboard is really a stop-gap measure.

In my opinion, the same problem does not exist with Yale/August which provide an app for managing access codes. August even has a neat integration with Airbnb, although it can be a bit frustrating for guests to use, as they must create an August account first.

All that said, if you want true end-to-end automation with Airbnb for both SmartThings’ Z-Wave devices and Wi-Fi-connected Yale/August devices, you can use PMS apps like Hospitable, Enso, or HostAway, etc. They use our API behind the scenes and can automatically program time-bound access codes for your devices based on incoming reservations.


I’m currently an @RBoy user and they are not responding at all. I have an STR automation built that is booking platform agnostic for my client using Zapier and the RBOY Lock Automation API, however it’s broken and I have no idea what to do next.

The lock is talking to the Smarthings Hub fine so I just need an API service that I can send time based code schedules to the lock pre and post check-in. I’m not an expert in this space but built a very cool automation for my client and have owned multiple STRs in the past so I do know enough to be dangerous I guess. :slight_smile:

Anyway, would love to learn more about how your platform might be able to help me for a long term solution in case RBOY never gets their stuff together and/or never responds to me.

Thank in advance.


I was able to get my account connected using Google Authenticator. I see the lock, but I don’t see where to set access codes - only unlock or lock.
I’m using a Kwikset 916 Zigbee, and Aeotec Smart Home hub, firmware 46.00008

I should add that SLGA is NOT working for me. From the android app, it returns a “something went wrong”, while from the web app it sees the lock and can lock/unlock it, but SLGA doesn’t seem to see the lock at all - it presents a screen that says “Requires a smart lock” and that’s it.

Hey @Jon_Crosby , I believe one of my cofounder had made a Zapier<>Seam integration but it’s not launched yet. Can you ping us at We’ll take a quick look at the Zaps you’ve made and see if we can quickly support to help you out.

@pcmckinley I’m gonna reach out privately since you’ve created a seam account already. I want to dig into your issue to see if we can figure what’s going on. It’s possible that SmartThings no longer supports access codes for this model, but i don’t know for certain yet.

I had problems seeing/adding codes with SLGA after adding my second lock. I deleted SLGA and re-installed it and that fixed the issue. Worth a try I suppose.

@sybohy First, thanks for stepping up and supporting the community - great business approach and wish you and your team all the success!

Quick question, I’m going to be evaluating different solutions for our multiple rentals and would like to evaluate Seam and possible one of your partners. Will there be any problems if any my Smartthings, Yale, and Nuki accounts are connected to your platform both directly and through one of your partners or more than one of your partners? Just don’t want any surprises.


@Msweetmo you absolutely can! First, you can connect SmartThings, Yale, and Nuki locks in your Seam workspace. Second, you can also connect those devices separately via one of the PMSs that use our API. Behind the scenes, we ensure that a device connected to multiple workspace doesn’t result in conflicts and race conditions. Feel free to ping us at if you have any other question. Thanks!

1 Like

Thanks @sybohy I’ve responded to you via email.

Hi, Bruce @h0ckeysk8er,
SmartThings support has had me do this several times - no joy.
Kwikset says they support it, but have no control, blame it on the hub Aeotec. Aeotec says they don’t control their own firmware (that seems quite odd).
So far Samsung/Smartthings hasn’t passed the buck, but they haven’t gotten past repeatedly asking me to deinstall/reinstall the app and/or SLGA plugin.
Interestingly the SLGA plugin for the web app behaves differently - the webapp sees the lock, but SLGA in the webapp doesn’t.

A few things we are seeing:

Removed and Added a Schlage BE469.

Upon Adding it automatically picked up the " [Universal Z-Wave Lock With Alarms]" Device Handler (not EDGE driver).

When installing codes with Schlage BE469 and using the RBOY DTH we see the following:

Lock Codes Install and the “Name” sent from Seam is visible in SLGA.

When changing the Z-wave Device Type to “Z-wave Lock with Codes”

Lock Codes get added however in SLGA the name is “Code X” and not the name installed with Seam.

This is sub-ideal as we have no way to know what each code is.

General question, what DTH are you using for Schlage BE469 and BE599 and are you seeing names come across to SLGA with pushing codes via Seam Dashboard?

It is very helpful for us to see the name inside SLGA or to have another tool that pulls the name. We also put the code in the name i.e. S-Test User 1234 (S- means programmed by Seam). Test User is the name, 1234 is the code.

We understand the RBOY [Universal Z-Wave Lock With Alarms] DTH will go away, so would prefer to start using the longterm solution for DTH or (Edge).

If you have a custom DTH installed in the IDE, it will be selected over an Edge driver. You must delete the custom DTH (since you can no longer edit them to remove matching fingerprints) in order to pick up an Edge driver.

I first installed the [ST EDGE] Z-Wave Lock PH - Devices & Integrations / Community Created Device Types - SmartThings Community from @philh30, but when using that driver, lock code names were getting reset periodically to their defaults, similar to the stock Edge driver. With a lot of research by @philh30 and @bthrock, we’ve come to the conclusion there are bugs in the default device handlers associated with locks in the ST code library. @philh30 has a beta version of his original driver that 1) reports the code name you’ve set for the code id properly; 2) displays the code name of the code used to unlock in the device panel in the ST app; and 3) seems to prevent the periodic resetting of the lock code names to the defaults. One note, any time you change the driver, the code names will be reset because they are managed by the driver itself, not stored in the lock or the hub.

So, my recommendation is to install the Z-Wave Lock PH BETA found in the same channel that is listed in the thread I cited above.

1 Like

@sybohy thank for the quick reply and great to hear I can use the system in parallel.

One more thing… I saw the Seam Gateway on your site and it says that it supports Wiegand - does that mean that if I have a dumb (not connected) Wiegand Keypad the gateway will allow me to program access codes on it remotely? As well as read the current codes programmed? You should tell the community about the additional features your company has…

So for anyone else that stumbles on this thread, to confirm: if you still have the universal Rboy device driver, that’s running your locks, trying to manage them with the Seam workaround here is not going to go well?

I’ve been testing and I had a lot of luck with a fresh out of box Integration with Seam and the default device drivers against the Schlage FE599 lock have on a separate test Samsung account, but certainly don’t want to knock off my production hubs/locks, which are located hundreds of miles away and drivers not easily manually removed and re-added.

@clifster correct. Seam won’t touch the codes created by RBoy. However, we’ve seen multiple instances where the codes created by Seam immediately get deleted by RBoy. This leads to an interesting arms race between our servers and RBoy :slight_smile:

We generally advise to turn off RBoy first, then you can start creating codes with Seam.

Anyone managed to get seam working? The authentication just hangs for me after the 2fa code.

1 Like

@mbuk we fixed a bug earlier this afternoon. If you email us at, i’ll take a look to see if that’s the bug that impacted your session.

1 Like