Codes Are Stuck Updating
Sometimes a lock reports itself online, but a code sits half-applied — accepted by the lock manufacturer’s service and never confirmed as programmed. GuestsKey flags this when a code has been mid-update for more than about fifteen minutes, or mid-removal for more than thirty.
This is almost always a delay inside the lock manufacturer’s cloud, not a problem with your lock, your Wi-Fi, or your GuestsKey setup.
Don’t factory reset the lock
This is the important part. The temptation is to reset the lock or remove and re-add it, and doing that while an update is queued usually makes things worse — you can end up with codes on the physical lock that nothing knows about, and a lock that has to be re-paired from scratch.
Wait it out instead. These usually clear on their own.
What GuestsKey is doing meanwhile
GuestsKey checks the code’s status every few minutes and marks it applied as soon as the manufacturer confirms it. To be precise about what that is: it’s watching for the update to land, not resubmitting it repeatedly. There’s nothing being forced through, and there’s nothing you can press to force it.
You’ll get one notification per incident rather than a repeat every few minutes.
If a guest is arriving soon
If someone is checking in before this clears, don’t wait for it:
- Send the guest a code you know already works on that lock.
- Use your backup entry method for the property.
- A battery pull and re-seat on the lock sometimes shakes a wedged update loose. It’s worth trying when you’re out of time, though it isn’t guaranteed.
When to escalate
If a lock has codes stuck for several hours, or the same lock wedges repeatedly across different bookings, that’s worth reporting rather than waiting out again — repeated wedges on one lock usually point at that specific device or account rather than a passing cloud delay. Email [email protected] with the property and lock name.