Hi, maybe two weeks ago our Lock (v3) began acting weird.
We only use the unlatch function on the main screen of the app (configured on swipe in any direction), never/not the locking function or any other unnecessary smartness (lock&go or anything like that).
When the lock began it’s weirdness, it would first unlatch normally, opening the door in the process (it physically swings open a bit), but then for whatever reason, a few seconds later, turn the key for the bolt to fully extend, and stop there, preventing the door to be closed again.
Pressing the lock’s button would allow us to revert that, so we ignored it for a while, but now it’s become even more weird.
Today i recharged the battery(pack), and after inserting it, the lock went through its initial calibration it seems, but when it stopped it did so in the fully extended state while the app stated that the door was closed and unlocked (while it was physically open and the bolt fully extended).
I removed the batterypack a few times and let it do its thing again, but always with the same result.
What makes it so weird is that we do have a door sensor coupled with the lock, and it usually worked just fine, but for some reason even in combination with it, the lock’s state is completely wrong.
I’m not sure if it’s related, but our door has an unusual rest-position for the keys. The insertion/rest position is when the key is horizontal, not vertical as for most other doors (even though this wasn’t really an issue before, apart from the unlatching process seemingly using the least amount of motion possible which in rare occasions wasn’t enough to physically open the door, but so rare that it wasn’t really an issue).
It feels like a bug in the firmware, with the fully inverted state.
I hope this can be fixed.
