Hi BlueID Team,
Currently, within the current solution we need to adjust the time regularly on devices due to time drift. The time drifts both forwards and backwards, depending on the hardware manufacturer.
At the moment, when we realize the time is not correct, we request a admin token for the user's mobile device and the time is adjusted. The token that was "not yet" or "no longer" valid is then represented and the user can open the door.
What would be the best practice in accounting for time drift under the Next Gen solution?
Cheers
Hello Daniel,
We are considering implementing different solutions like router gateway that can provide many functionalities like OTA etc but it can also be used to adjust time and reduce time drifting.
Could you please share bit more details about how currently you handle this situation? Mainly please explain about "The token that was "not yet" or "no longer" valid is then represented and the user can open the door." so I can better present you idea to overcome it.
Thanks
Hi Waqas,
currently, we have two valid mobile access tickets, 1 ticket for today and 1 ticket for tomorrow.
IF the time is drifted forward into the next day and we present the ticket for today. We get a denial with the message "your ticket is no longer valid".
We recognize the ticket is, in fact, valid and that the time must have drifted into the future.
In this case we get the necessary permission to adjust the time of the device.
We do the same exact process if the is the reverse case is true: Where the time on the device is in the past and we get the message "your ticket is not YET valid"
Hello Daniel,
It is possible time can drift with a few milliseconds but not in hours or days. If the time has drifted it is mainly due to the lock having restarted or empty battery.
Usually, this happens after the battery has been replaced or is completely dead. Could you please repeat these steps and when get the error so capture the screenshot and gather the logs using the Lock Admin app and share them with us?
Thanks,
Waqas