Seems the Zigbee Lock Driver no longer has these issues, Kwikset locks have been running good now fo the last 2 or 3 days. No more renaming of lock codes to code 1, code2 Etc. No more annoying messages about updating lock codes constantly.
2 Likes
Hello,
The SmartThings development team would like to provide an update on the incident from Wednesday, Feb 15.
- Summary: On Wednesday Feb 15, users reported complaints about excess notifications, events in the history tab, and also SmartLock Guest Access lock code names being deleted. Devices that were joined to the Z-Wave Lock DTH and being migrated to the Z-Wave Driver would have been affected.
- Later on Wednesday Feb 15, SmartThings released a driver change to prevent the excess notifications and event reporting in the History tab on the SmartThings App.
- User Action Needed: A limited group of users, only in North America had the lock code names deleted from Smart Lock Guest Access. In order to repair the lock code names users need to re-add them to the SmartLock Guest Access. Please note, we do not believe that actual lock codes were deleted, just the names of these lock codes. We apologize for the inconvenience.
Thank you for your patience.
2 Likes
Thanks @alissa.dornbos Does this also mean all z-wave locks have been migrated to Edge? Mine is still on the standard DTH.
1 Like
Excellent question. We stopped the migration so some Z-Wave Locks migrated on Wednesday, others did not. We still have many more devices connected to Z-Wave Lock remaining on DTHs. I dont yet have an ETA on when these will be migrated to the Edge Driver, but can let you know more later.
2 Likes
@alissa.dornbos If I already have my Schlage Z-Wave locks using the SmartThings Beta edge driver that I connected to manually, will they be migrated to a production driver?
Hello 
@allanp. Your device will remain on the Driver in the “Production Beta Channel”, unless you unenroll from that channel and rejoin your device. If you were to rejoin and unenroll from that channel, then your device will join to the Production Default Channel. We will not be migrating customers devices from the “Production Beta Channel” to the “Production Default Channel”.
To share a little bit, we call both those channels “production” because they are intended for external customer use. The “Production Beta Channel” gets the driver updates one week faster than the “Production Default Channel”.
Thank you for your interest and support, we greatly appreciate it.
Thanks for the reply. I will try that next week when I get the chance. When I tried that over a month ago, it did not want to load an edge Z-Wave lock driver. Perhaps the production channel didn’t have the fingerprints for my lock yet. I understand from another thread that it does now.
1 Like
I also stopped receiving push notifications from the app on Feb 15 as well. All of the settings are still set to allow push notifications but I’m not receiving them anymore, is there a solution for this?
This just happened to me today (July 6) as smart things reported finishing some rollout. Like a previous response, one of three locks now isn’t functioning (all codes renamed code 1, … Etc. Those codes can be deleted, but new ones not created.) Did you ever find a solution? Thanks.
The codes themselves should not be affected, just the code slot names which are maintained by the lock Edge driver. You should be able to simply change the code names using SLGA or via the nameSlot command in the new ST Web App Advanced. You can also see the code slot names in the capabilities section of the Web App located in lock codes.lockCodes.
I surmise this problem occurred because of a change in the underlying lock handler to fix the problem with lock code names being reset to “Code X” regularly.
Thanks for your time - the concerning bit is that I can no longer set new codes on this lock (as happened to Sam above). Is there a simple trick to get new codes back up and running?
If the code slot names did not revert to “Code X” for one or more of the codes for a lock, you will not be able to change the existing codes and possibly not be able to create new ones. Once I forced all my lock code names back to the default of “Code X”, I was able to change them using both SLGA and the nameSlot command for the locks in the new ST Web App Advanced. You can check the state of your lock code names using the Web App by looking at the lockCodes.lockCodes capability seen here:
If one or more of your lock code names is not listed, then you will need to force reset it by using the requestCode command below the Attributes of the lock. This will force reset it to “Code X” and you will be able to change it as I described above. You can force all of them by using the reloadAllCodes command, but I did it one by one so that I was able to keep track of which ones I’d changed.
As said in a earlier post, the actual codes on your lock should not have been affected, only the code slot to code slot name relationship should have been affected.
Also, could you please tell us what lock brand and model and what Edge driver you are running for your locks?
All the code slot names for the lock in question reverted to “Code X” form.
I am able to:
- Rename the lock codes using SLGA
- Delete lock codes
- Lock and unlock the lock from SLGA
I am not able to:
- Add new lock codes
The lock I have is the ULTRALOQ U-Bolt Pro Z-Wave (ASIN B09Q5QTSQS)
The driver is “Z-Wave Lock” version 2023-06-13T18:57:31.372336323 ID 0f206d13-508e-4342-9cbb-937e02489141
Thank you very much for the assistance, we are away from the house now and this is going to cause us some problems.
Did you check your lock codes in the Web App Advanced? Also, try adding a code there using the setCode command. That will tell us if it’s SLGA or something with the driver or handler.
I did check my lock codes, but when I run the command requestCode, I don’t recieve any feedback from the web app (is there a way to request the code itself from the web app?). I do get a notification that the code was updated via the SmartThings phone app.
When I try to setCode from the Web App Advanced, nothing happens, no updates to lockcodes.lockcodes.
I did just discover something odd. After trying to set a new code in the phone app, which fails, if I go to requestCode and request an index not yet reflected in lockcodes.lockcodes, the label I just submitted via the phone app pops up under lockcodes.lockcodes. I have not yet been able to test if that new code actually works.
requestCode will only show you the code name and cause SLGA to say the code was updated. You can’t actually see the code in the code slot.
After you use setCode, you have to refresh the data for the lock to see updated lockCodes.
Thanks for the clarifications.
After submitting a setCode followed by a refresh command, the new code does not take.
As I pointed out above, I found a strange way to get a new code “added” by submitting a failed attempt from the android app, then requesting the next id to be issued from requestCode.
Hmm…I just tested both locks and was able to add new codes using SLGA. Were all your previous lock names changed to “Code X” and did you get them changed back? Your symptoms sound like there is a lock code in a slot but there is no lock code name in the lockCodes data structure. You might try a reloadAllCodes command to see if any additional code slot->code names get populated in lockCodes.
I hope samsung is fixing this… its ridiculous that a billion dollar company screws up something like this… actuality its very very poor they screwed this up. Its amazing that software is the only defective product that can be sold.