Check-in time error

If you get the error message "The check-in time is invalid. This could be caused by the check-in time being in the past or the date and time set in Windows is wrong." when creating a key, it's because the reservation’s check-in time is too far in the past This concept is similar to the Editable History Window in Mews, where the system does not allow for changes to be made for events/actions too far in the past.

 

 

If the same error appears multiple times in Device Commands Queue for different spaces, various reservations with different departure dates, and for different encoders, then it could be that the time zone set on your computer running the Mews Connector application is different from the time zone set in your door lock software and/or the computer running the door lock software server application.

 

 

To fix it, follow these steps:

 

1. Check if the reservation has an arrival or departure time in the past.
2. If the reservation’s arrival or departure time is within the lock software’s acceptable time window, check that the following devices have the same time zone:
   • Computer where the Mews Connector application is installed.
   • Computer where the lock software server application is installed.
   • The lock software/management system itself.

 

If the issue persists across different reservations, and the time zones are aligned across all systems and machines, contact your door lock software provider for further assistance.

 

 

Read more about what is sent in a key creation command and how the time zones get converted in How do key cutter integrations work.