[OBSOLETE] Lock Manager

This is a follow-up to my previous email. I deleted SLGA. When I lock my door using the lock button (a Kwikset lock, by the way), SmartThings reports that RCB locked the door. If I lock it from the inside, SmartThings reports it was locked manually. I do not get any notifications as to which user unlocked the lock.

I went into lockmanager.io and turned on notifications for all my users (after I deleted SLGA but before I did the above testing). I do not get any notifications on my phone that user x unlocked a door. Are the notifications in your app the kind that are sent as notifications on my phone? If not, I’ll need to adjust. Actually, I may not have to “read” a notification at all to do something because SharpTools can read the lock code without a notice on my phone, and turn on a switch, but I do like to see who’s coming and going and I can’t seem to do so with lockmanager.io and I could with SLGA.

Maybe SLGA doesn’t interfere at all? I still can’t get my cleaner code to be sent to any locks. I’ve deleted it now and I’m going to try to reload it to see if that helps.

Thanks!

So as an add’l update, I removed SLGA, deleted my cleaners member, and re-added cleaners as a member and set it to Always. It now works and it is still slot 7. I don’t know how it’s still slot 7, but I guess I didn’t move anything else around, so it stayed as 7. Thanks.

SmartThings on Android (Samsung A42)
Aeotec Smart Home Hub
Internet via Verizon Orbic MiFi
Kwikset 916 Zigbee lock

Lock works fine, I can lock it and unlock it via the phone app.

I’m having issues setting up user codes for the lock.
From the Samsung Smartthings app, when I try to set the user code via “Invite Guest” I get a “Something went wrong” message.

I tried setting up LockManager.io - went through all the instructions, got down to the entering keys, click save, then click next aaaaaand… nothing.

I noticed within the Smartthings developer workspace, there’s a message about "SmartThings is not able to verify the registration of the Webhook SmartApp. Please make sure your app is available and properly implemented and verify again. When I click the “Verify App Registration” link it says “Confirmation request sent to your SmartApp.” I’m guessing that means I should get a confirmation in the SmartThings on my Samsung A42, but no. Or maybe the LockManager.io website? Not there either.
I noticed there’s threads about a couple other lock managers out there, but they’re marked obsolete or deprecated.

Any help on getting the setting up user codes in the SmartThings app, or getting Lockmanager.io to work is much appreciated. My guess is that it’ll have to work within SmartThings first before it’ll work with LockManager.io

Thanks in advance!
Paul McKinley

I’m sure that’s very frustrating. :disappointed_relieved:

Lockmanager.io is a community-created smartapp that is still in the alpha stage, but that has very active support from the author, so I’ve moved your post to that thread so you can get the quickest support.

You originally posted in the “developer support” section of the forum, which is for people who are writing smartapps. They wouldn’t be able to help you with SLGA since that’s an existing official feature.

If you’d like to report a problem with SLGA, you need to do it through the official support channels. (This forum was set up several years ago so customers could help other customers, and is not monitored by smartthings support, except for that one developer section.)

To reach support, use one of the contact options on the bottom of the following page:

The first person you get will probably just be a Samsung employee working from a script, but if you hang in there and stay patient, your issue will eventually get escalated to smartthings technical staff.

2 Likes

Thanks, @JDRoberts ! I didn’t know where to post. Also thanks for the pointer to SmartThings support!
I don’t know what SGLA means…

1 Like

SLGA = Smart Lock Guest Access (also called smartthings lock guest access)

It’s the official lock management feature in the SmartThings app. (Not available in all regions, though.)

Ah. Yes, That’s what I was referring to that gets the “Something went wrong” error. I’ve contacted via the phone number you provided. They say:
#1 reboot the hub (will do that later when I’m on location
#2 reboot the network router (it’s a MiFi until I get real network on location)
#3 reboot phone (done, no joy)
#4 reinstall SmartThings app.

Ah. Could be the MiFi. You may have to have the phone and the hub on the same subnet in order for the installation to complete. :thinking:

Well, that’d be pretty useless if I had to be on the same subnet as the hub. The point is to be able to set up user codes for a short term rental - remotely. Real internet lead time is 4 months so the MiFi is just an interim solution. Even so, everything is working, including remote lock/unlock. Just not setting the User codes. I’m not seeing why MiFi would be any different than any other plain jane WiFi router. I’m headed over there in a few to reboot the MiFi & hub.

I noticed @jkp had tagged @ethayer, is this the lockmanager.io owner?

I only meant when setting up SLGA for the very first time, that is downloading that service onto your hub. Not using it after it was setup, which, as you point out, you definitely want to have remote access for. Sorry if I wasn’t clear.

So just locking and unlocking the device isn’t done through SLGA. That’s a special add-on for managing lock codes. (And I have no idea why managing lock codes isn’t part of the base app features, but it isn’t.)

And, yes, ethayer is the lockmanager.io author, this is his author thread, and he will get a notification every time a new post is added to this thread. :sunglasses:

@JDRoberts
Ugh, I’ll have to try ripping out SGLA and reinstalling it when I’m onsite. I’m with you - why wouldn’t it be a base feature. To quote from “Meet the Robinsons” “I’m beginning to wonder how well this plan was thought out.”
I’ll wait semi-patiently for ethayer to respond to the lockmanager issues.

1 Like

BTW, I don’t know if this is related at all or not, I don’t really know how SGLA fits into the architecture, but there are platform problems today for people downloading new edge drivers. :thinking: but I think your problem started earlier than those.

Unable to join channels (25 Jan 2023)

@ethayer
Erik, I’ve tried ripping out the smartthings developer setup - to the extend of closing the account and reopening it.
The App Credentials wants to verify the app registration, but that doesn’t work. I realized just now I needed to reset the client id, etc on the lockmanager.io site too, which I just did. Same thing - I save the keys, click next and nothing happens.
The confirmation request says it was sent to my SmartApp, but I don’t get any notice in SmartThings on my android or the my.smartthings.com web app, so I’m not sure if there’s something broken or if I’m looking the wrong place.
Thanks in advance!

A quick check of the API Browser shows that SLGA is a webhook application. From my understanding, a piece of code gets installed on the hub which handles the communication with a backend somewhere else on the Internet (in this case the ST Cloud). So I suppose there could be some relationship with the other issues we’re seeing with Edge driver installs. But my gut tells me the Edge driver install issue is related to the back end that manages the channel and driver subscriptions.

1 Like

@h0ckeysk8er Bruce thanks for chiming in!
I had to install SLGA on my SmartThings app on my phone, on my wife’s phone, and the my.smartthings.com app. So, I’m guessing it’s an app thing, not a hub thing.
Samsung recommended reboot hub, router, phone, and reinstall SmartThings app. I’ve done all those, although not necessarily in that order to no effect.

@JDRoberts I tried ripping out and reinstalling ST on-site. On reinstall it had to reinstall SGLA. No joy. When I reinstalled ST, it already had my login information and connected to the account even though I’d gone to settings/app to try to completely remove the app data.

One thing I haven’t done that I wonder if is necessary is to set a user code on the lock first. It’s a brand new lock; no user codes have been set even manually. I’ll try that tomorrow - I need at least a few user codes set even if locally.

@michelp Michael:
Ha! The post was deleted, but I’d already gotten it via email! Thanks for chiming in BTW, the comment seemed pertinent to me and is appreciated.

The setup is new last week. Yes, fw is 46.00008. I think I updated firmware when I installed the hub, but I slept since then so not sure. I’ll see if I can check for fw update again.

Ah, for the days when companies actually did QA on software updates…

Just remember that this thread is the author thread for Lock manager and posts here should be about that.

You can start a new topic about SLGA if you have more questions/comments about it. That would go in the following section of the forum:

SmartApps & Automations - SmartThings Community

How were you able to verify? This is where I’m stuck…

I think I ended up created a new client ID and secret after the first attempt and then it worked.

@DigitalDan

Did you ever get an answer for this question?