I’ve been using smart locks for a while now, and I must say, they’ve completely transformed how I manage access to my home. However, I recently stumbled upon an interesting challenge while setting up my newer lock. I have two Yale locks—one older and one newer, both with different communication protocols. The older one uses Zigbee, while the newer one is on Z-Wave. I’ve always managed the older lock manually without any issues, but when I switched to the newer lock, I noticed some quirks with the Lock Code Manager (LCM) app.
Initially, I wasn’t using LCM with the older lock, relying instead on the device page to add, delete, or retrieve codes. When I upgraded to the newer lock, I decided to give LCM a try. However, I encountered some unexpected behavior. Manually adding codes didn’t work as smoothly as I hoped, and I realized it was because LCM was interfering. I noticed that the older lock would fail to set codes properly, and the device log would repeatedly show ‘setCode X’. Removing LCM temporarily allowed me to manually add codes, but it required waking the lock up by locking and unlocking it a few times. Reinstalling LCM brought the issue back, which was frustrating.
After some experimentation, I found a workaround: manually adding codes with the same names on both locks and then re-adding LCM. This seems to keep everything running smoothly for now. However, I’m still curious about what benefits LCM truly offers, especially for managing the older lock in the future. Interestingly, the newer lock works flawlessly with LCM, so I’m hopeful that the older one can be managed more seamlessly with some tweaking.
If anyone has encountered similar issues or has tips on optimizing LCM for multiple locks, I’d love to hear about your experiences! It’s amazing how these smart devices can sometimes throw curveballs, but with a little patience and problem-solving, they become even more reliable and convenient.