Hi,
I’m not a developer myself but I rent a flat with the team MyGuesRelation in Nice who has over 100 properties in Nice, and use SuperHote (a French CMS) to manage bookings mostly on Airbnb and Booking.com.
The problem is the following.
I’ve purchased the complete Nuki solution for my flat which includes SmartLock Go, Opener, and Keypad.
It works beautifully on a stand alone mode.
We used the Nuki API on SuperHote and this were the problem begin as a beta tester of the solution.
- First (This is SuperHote problem) you can insert only one key on their system and not one key per property… A real dumb integration at the start.
- It does work. But this is what it does:
- Once a reservation is created it “spams” again and again the customer with multiple invitation to download the app and register with a virtual key.
This is where we can’t figure out where the problem is… SuperHote? Nuki?
- we can’t specify the date and time of activation of the Nuki system… Which means that the key seems to be valid un definitely. Since we know when the customer arrives/leaves it does make sense to be able to limit the validity of the period. Easy too to specify as a standard value that the time would be from 2pm on date of arrival to 11am on date of check out.
Last but not the least… Nor Nuki nor SuperHote technical support are much willing to do any efforts to find out / solve the problem. This makes me wonder if we just should abandoned the solution for another one, and if so, which? We’re talking a potential 100 properties…