My lock code manager has been flaky for years. Every time we have company I fight with it trying to add codes for temporary guests.
Trying to add a user/code and it's just sitting there showing pending jobs-2. It added it to one lock but not the other. Verbose logs show it getting codes from both locks then thats it.
To get by I manually added the new user/code in the slot it should be in. Even refreshing job status still shows pending jobs - 2.
usually this indicates a communication issue with the lock. Have you tried adding codes directly using the lock driver directly to verify the issue is or is not related to LCM?
Yeah, that's my usual work around when I can't get them to add. They add fine directly from the lock device page.
I have a rule set up to lock the door 30s after the collect sensor shows closed. My wife ends up using that regularly. Never noticed a lag or anything in the hub locking doors..
I have seen this problem as well with a Schlage deadbolt. I can't always get the code change via LCM but can always get it via the driver. Something flaky about LCM.
Hmm. Mine are schlage be469's..
I swear sometimes it seems like it works on the computer but when I try it from a web browser on my phone it just goes pending. Maybe that's just a coincidence..
Not sure. The locks are low power devices to prolong battery life. They use a feature called FLiRS where they are mostly offline but wake up periodically to see if there is a message for them. By doing this they can get months of battery life.
It seems FLiRS is more demanding of the mesh than always powered devices. You might want to check the locks Z-Wave routing and signal strength. Ideally a straight shot to the hub and a strong RSSI level. If not maybe you need a ZWave device or repeater inbetween the lock and the hub to improve reliability.
Weren’t Schlage locks removed from the list of compatible devices because of various forms of flaky behavior?
Spoilsport... 
Yup, AFAIK they are no longer on the compatible device list.
My BE469 also fails to add a lock code from LCM to my BE469.
My Yale Zigbee lock added the same code just fine from LCM.
Weird. I didn't know they've been removed. I've been using them almost as long as I have been using hubtat. With a zwave plus beaming repeater/switch near them they've been rock solid. The only quirk I've ever had is LCM not wanting to add codes to them LOL
Yeah there have been some issues reported over the years, and they appear they may be related to firmware versions on the locks.
Mine came over from SmartThings when I migrated from that platform to Hubitat, so I've had mine forever as well, and really haven't had any issues with the lock itself.
Same with them and smart things. I totally forgot all about ST 
Download the Hubitat app
