We are experiencing an issue where our API system frequently returns the error “423 Locked” when our guests at the hotel use the smart lock (unlock/lock) via the API to MyTourist. While our guests see this as a general 500 error, internally, we trace it back to the “423 Locked” response. This does not happen every time, but it occurs frequently enough to cause inconvenience.
Do you know what’s going on and what can prevent this from happening? We want to ensure that our guests have a seamless experience with the smart locks.
Thank you in advance for your assistance, and I look forward to hearing from you!
The HTTP response “423 Locked” implies that the lock is busy carrying out an action, and hence cannot perform another action. It could be locking or unlocking when you are sending an API lock/unlock command. Could you please check the behaviour once - how are the guests locking? is it via the API? how many people are sending the command at once?
The link that guests use to lock or unlock their room door is created via API and webhooks through our system MyTourist. We have confirmed that only one guest at a time is sending the commands using this web-link, so there should not be multiple commands being sent simultaneously.
Do you have any recommendations on what could be causing this issue or any settings we should adjust to prevent this error?
I appreciate your assistance and look forward to your advice!
Please check if you perform any kind of operation before the lock/unlock action, and ensure some delay of few seconds before locking/unlocking. Since the commands are going through API, please check if the wifi connection/bridge connection is stable always i.e., the smart lock is online always and connection is stable.