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

[h0ckeysk8er (Bruce Pinsky)]

@buster

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.