KAS Web Console
Error “236 Internal Interface timeout”
This means that the lock has not been initialized to the cloud console mode at the time of setup, you will need to reset the lock and re-setup the lock to with the KAS Web Console app.
Error “Something went wrong. Code: 400-Invalid token”
If you are receiving this error message, please try the following.
- Force close the app.
- Reopen the app.
- If the message still appears please try restarting your phone.
- Open the app.
Error “242 Internal interface timeout”
This error means there may be a connection issue between the Gateway, online node or Lock/ACR.
To resolve this issue, please try the following steps
- Check the connections of all 3.
- Power cycle the gateway.
- Power cycle the lock/ACR, make sure you set the clock of the lock/ACR after.
- Open a ticket with us for further troubleshooting if you are still experiencing this issue.
KASaccess
With KASaccess, if a key isn’t working with a lock, check the ‘Queue Table.’ Here, you’ll find the sequence of events when adding a key, along with any errors. To identify errors, observe the color of the squares next to the key. Green indicates a successful addition, yellow means it’s pending, and red signals an error.
If there has been an error:
Hover your cursor over the red error square and read the displayed text, which typically provides instructions on the issue and the necessary steps to resolve it. If the error lacks instructions, please contact us by opening a ticket. After following the instructions, be sure to click the ‘Retry’ button. A successful retry will be indicated by a green square at the end of the sequence.
If there is no error:
This issue is likely related to the clock settings. To resolve it, ensure that your property settings have the correct time zone selected, and if applicable, check whether daylight savings is enabled. If your location has daylight savings, remember to toggle it on and off accordingly when transitioning in and out of daylight savings periods. Once completed sync the clock on your lock by clicking the “Sync Time Now” button.
KAS Web Console
Key is added to the lock but the lock wont respond to the RFID/PIN:
This is most likely a clock related issue, make sure that the clock settings match your time zone and then set the clock.
Error “236 Internal Interface timeout”
This means that the lock has not been initialized to the cloud console mode at the time of setup, you will need to reset the lock and re-setup the lock to with the KAS Web Console app.
Error “242 Internal interface timeout”
This error means there may be a connection issue between the Gateway, online node or Lock/ACR.
To resolve this issue, please try the following steps
- Check the connections of all 3.
- Power cycle the gateway.
- Power cycle the lock/ACR, make sure you set the clock of the lock/ACR after.
- Open a ticket with us for further troubleshooting if you are still experiencing this issue.
Lock-S, LMS & ADEL
Check that the check in and check out time is correct when issuing a card to a guest.
Set the clock on the lock by creating and then swiping a clock card directly to the door or by using your Lock-S PDA.
Check that the batteries are working and that there is no corrosion in the battery compartment.
Neo Cloud Lock
This lock can be over tightened and as a result the lock can get jammed, this will prevent the door from being opened. To fix this loosen all the screws that keeps the lock to the door until the handle unbinds.
Neo Cloud ACR
The Neo Access ACR connects to a electric strike or mag lock, most likely it can be a fault of the ACR or a wiring issue, if this occurs please open a ticket.
Low battery can cause this as well as a faulty motor, try replacing the batteries, if you are still having the same issue please open a ticket.
KASaccess
With KASaccess, if a key has failed to add to the lock, check the ‘Queue Table.’ Here, you’ll find the sequence of events when adding a key, along with any errors. To identify errors, observe the color of the squares next to the key. Green indicates a successful addition, yellow means it’s pending, and red signals an error. Hover your cursor over the red error square and read the displayed text, which typically provides instructions on the issue and the necessary steps to resolve it. If the error lacks instructions, please contact us by opening a ticket. After following the instructions, be sure to click the ‘Retry’ button. A successful retry will be indicated by a green square at the end of the sequence.
Kas Web Console
Error “236 Internal Interface timeout”
This means that the lock has not been initialized to the cloud console mode at the time of setup, you will need to reset the lock and re-setup the lock to with the KAS Web Console app.
Error “242 Internal interface timeout”
This error means there may be a connection issue between the Gateway, online node or Lock/ACR.
To resolve this issue, please try the following steps
- Check the connections of all 3.
- Power cycle the gateway.
- Power cycle the lock/ACR, make sure you set the clock of the lock/ACR after.
- Open a ticket with us for further troubleshooting if you are still experiencing this issue.
Lock-S
Make sure the gateway is online and connected to your network, the gateway should show a green LED and a green indicator within the Lock-S software itself.