I have Z-Wave Schlage BE469 locks - 4 total (2x on each of 2 hubs). I got the same messages.
I tested all my devices after the weird messages. 3 of my locks work fine. On one of them is busted. I seem to be able to delete codes, but when I try to add them I get an error “Something went wrong while creating the lock code. Try again.” I tried old codes and new codes - nothing works.
I tried rebooting the hub, repairing the z-wave network, uninstalling/reinstalling Smart Lock Guest Access, and uninstalling/reinstalling the app. Nothing works to be able to program this last lock.
I was on a plane and these notifications started popping in. Wife was at work and started freaking out thinking someone was hacking the locks. She is just a user and knows little about all the happenings. I talked her down when I landed.
Smartthings: If security related, please be cautious!
You can also learn a lot about what is happening from the driver logging in the ST CLI. You can also use the CLI to send commands to the lock to see if you can cause the problem. When I was investigating this issue previously, it seemed like the reloadAllCodes and requestCode commands would trigger the driver to reset the lock code names and trigger the constant refreshing with accompanying messages.
I noticed this happened whenever I opened SLGA and went into lock codes. Things got crazy and I would get around 20 notifications about lock codes being updated and renamed and so on. Sometime this would also happen if someone unlocked the door with one of the codes.
My guess is that is because SLGA issues a reloadAllCodes command so that it has the latest and greatest lock codes and lock code names from the driver. In fact, if you issue a reloadAllCodes from the CLI, SLGA will send you a notification for each lock code you have configured indicating that it has been updated (also happens if you use requestCode to get a single slot’s info).
I have turned off all SLGA notifications and I’m recreating much better functionality in Sharptools and then I’m just going to remove SLGA altogether. I have opened a slew of issues with ST support over the years and they have asked me their standard open the support access and so on and to date they have never got back to me or fixed a single one. I have a ticket open for Stelpro thermostats for a month and a half and when I asked them for an update they replied with there waiting to assign a developer. Really LOL. Over the years I have learned you just have to improvise and figure out work around’s yourself. ST is not going to help!!
Sharptoos, I’m building it now. You can make a Dashboard and enter and delete the codes. You can even delete them at certain time or only allow certain days during certain times. Sharptools is very easy to use you just have to build the rules.
I have all Kwikset locks. Setup a free account and you can check the capabilities of the lock and also see if the lock returns the lock codeId and method. You can also create a test rule and pick the lock you want to test and see what options you have in actions such as code slot, code and description.