Thinking something similar in the past, I removed the LCM and reinstalled. That did not seem to make any difference. After re-installing LCM, the same users and codes were displayed. Stuff was not wiped. Makes me think you are referring to some other procedure.
Did I miss a recipe, support note, or something to guide the effort?
I did not have to do that with my Schlage lock. So it's not a requirement or anything.
I just had to remove the lock codes and put them back again. I had migrated with encryption enabled which is not recommended evidently, which was causing me problems with editing or updating codes. However all the codes worked fine after migration, It was just adding and updating that was messed up.
See this post above for how to remove the codes from the devices. The codes are stored on the devices, and visible in the device pages. LCM just brings it all together in one place.
What is that all about? Position 251 when "maxCodes: 250"? Does that make sense? And, 251 can't be deleted in the device screen. LCM agrees and generates a lot of "debug" entries and a bunch of retries when I try to use it to delete 251.
A few of the retries showing in the log. There are several more. Don't know why but the .png of the log will not load into this message. Will create a separate message with the log.
Now need to add the codes back into the locks. First try will be with lock manager.
On Schlage locks (is this a Schlage?) IIRC there was something funny about the first code on the lock being different than the rest. Don't remember the details...wonder if it could be that...
Guess I got my info mixed up, it is the Yale that has 250 slots, the Schlage only have 30.
It seems like that slot 251 code is what is breaking everything.
Here is what I would do now at this point.
Either delete the LCM app or delete the failed jobs
The Lock :: Apartment switch the driver to "Device"
Use the two command buttons up top to clear the states
Switch back to the normal driver
Make sure debug is on and then click Configure.
I am not totally sure if that will do a full code fetch, if it does not then once the configure is done click Get Codes
If that code is still in the lock, hopefully this will put it in the correct slot in the code list on the device page. Lets see what Current States looks like after that.
You could also Test out LCM by ONLY selecting the "Front Door" lock which was fully cleared out. See if it will work correctly for only that door first before adding the other door to the users.
Hey @rlithgow1 , yeah, I deleted all entries using the Device page for both of the 2 locks. Tried to delete position 251 from Apartment with no joy. Rather interesting that there was no clue that the operation executed, succeeded, failed, or decided to take a vacation. Nothing displayed. Nothing in the log. The net net was I couldn't delete the 251 code. Check out the 3 screen captures from a couple posts ago. (We now measure time in "posts"? )
Yeah, I kinda suspect that 251 thing may be at least an indicator or side effect of the root problem. What is that? No clue and that's why this thread is so damned valuable and apprecited. Thanks
Will get back here later today and work those steps to see what we get from the effort.
Just for reference ..... here is today's LCM view of the world. All names are on the Front Door lock.
The "Type" dropdown on the device page.
Make note of the current type (aka Driver). Switch it to "Device" and save.
Then you will see the two command buttons I am taking about up top.
Once done switch back to the original driver and save.
The follow the rest of the steps I listed above.
Clearing the lock seemed to work properly. I'll add a couple captures to make this thread useful for future readers.
Changed the driver to "Device" using the "Type" dropdown. These buttons were displayed. I used "Delete All Current States", "Delete All Scheduled Jobs", and "Delete All States".