Subject: C-7 to C-8 Pro migration – All Schlage BE469ZP locks fail with "lock() failed after 5 retries"
I migrated from a Hubitat C-7 to a C-8 Pro using Settings → Backup and Restore → Migrate.
Platform version: 2.5.0.159
Since the migration:
-
Three Schlage BE469ZP locks all fail only when Hubitat issues lock() or unlock().
-
Dashboard commands fail.
-
Device page commands fail.
-
Manual thumb-turn and keypad operation work perfectly.
-
Hubitat immediately receives and updates the physical lock/unlock status.
-
Battery reports are received normally.
-
Six Z-Wave repeaters are present.
-
Closest repeater is approximately 5 feet from the locks.
-
Same hub location, same antennas, same Ethernet connection as the previous C-7.
-
The locks worked flawlessly on the C-7 before migration.
Debug logs show repeated lock() attempts followed by:
Front Door Lock command "lock()" failed after 5 retries
Physical lock/unlock generates Alarm Reports and status updates correctly.
Could you please review whether this could be a migrated S0 secure pairing issue or a known issue with migrated Schlage locks on platform 2.5.0.159?
Following. I have Schlage locks also and I'm prepping for a C7 to C8P Migration
I think your best bet would be to try a general exclusion on the lock if you have another Z-Wave controller, then re-including it to your hub. (You may or may not need to reconfigure the lock itself, e.g., re-set codes.) If you don't, you could add a Virtual Lock with Codes device, swap out the "real" lock for that one, exclude the lock, re-include the lock, and swap/replace the virtual device with the real one again. The hub has tools when adding a device to make this easy (the "Replace" button right after you add the device), or you can use the Swap Device tool yourself.
A factory reset of the device and a re-include is a more extreme version of the above but probably isn't necessary -- though is certainly something you can also try.
Schlage locks themselves are a known issue. 
They aren't listed as officially compatible with any model of hub because there seem to be lots of hardware and firmware variations that cause various oddities for some, while working perfectly fine for others.
But many people are able to make them work, and if you could before, I'm sure you can again. I just think doing this bit of manual effort after the automatic migration might be the easiest path in this case!
@bennycakes For giggles can you post your z-wave table in it’s entirety? (use windows snip)
If confirmed working well, I would factory reset the new hub. Then I could do a database rebuild on the old hub then to a full power cycle on the old hub by shutting down then unplugging power for 1 minute then powering backup. Then re run the migration.
Thanks for the suggestion. Yes, it is a real pain to exclude, reset and include Schlage locks and with three of them,…may take forever. But I will consider doing a general exclusion on one of them.
I have attached my z-wave table which has 81 devices, including virtual ones. The screenshots at 70%. Let me know if you prefer 100%. Thanks for your support and help.
By the way, I am new in posting to the Hubitat community. So please let me know if there is a better to post and upload these screenshots. Thanks
Overall the table looks good. I’d redo the migration with the power cycle I described above then see how things run (also after the migration backup is made, shut down the old hub)
Good news! I tried @bertabcd1234 suggestion to create virtual locks, factory reset, exclusion, another factory reset, inclusion enabling S2 security and two of the Schlage locks are now working fine. Thank you Robert. You’re my hero!
Still working on the third lock, which is the older model. Thanks guys for the quick response. 
Forgot to mentioned that I did the power-cycle before and after the inclusions.
Resolved: Finally got the third Schlage lock to work, which is the old model BE469. Lesson learned...when removing the ghost node, first disconnect the battery on the Schlage lock (which is key), power cycle the hub and then, remove the ghost node. Thanks everyone for your suggestions and recommendations. 
