Good morning fellow Nuki Fans
I have meanwhile 4 Nuki smart locks in rental buildings, it has been a life saver for me to manage airbnb arrrivals with Nuki and it’s automated code creation for Airbnb bookings is also the reason why i invested so much money in buying this system and not another more compact device.
Unfortunately ever since the Nuki web interface has been updated , there have been issues with the Nuki - Airbnb Integration.
I have been receiving and reporting complaints from my guests (people being locked out their accommodation, people entering when other guests were still enjoying their stay :-((, people receiving emails their acces codes had been deactivated days before departure, the manual setting overriding not working so i had to create new codes and communicate several codes to my guests during their stay etc etc all of this impacting my reputation on Airbnb as loosing my superhost status and receiving guest complaints, apart from my continuous worry that something would go wrong and they would call me at night being angry for being locked out or in the morning meeting the next guests in their bathroom while their booking has not finished yet …)
After several reports about it I received a mail from Airbnb they would be working on the issues with Nuki and that we would have to create codes manually for the time being.
Up to today i have not received any mail confirming from Airbnb nor Nuki the issues were solved or partly solved.
However it seems the automated code generation is now operational again, it is still setting wrong times activation and deactivation times.
Since they are activating new codes at 00.00 the night of the day of arrival instead of 15.00 pm , the Nuki system is already granting access to new arrival guests while my current booking is still ongoing…
For my guests and thus for me this is a major security and privacy issue, it is impacting safety of my guests and impacting my reputation and income as a host. I’ve been reporting this to both Nuki and Airbnb for several months and posting dozens of tickets now :: Airbnb telling me they can do nothing about it since the issue is with Nuki and Nuki not replying to the ticket or saying the issue is with Airbnb, or each time another support agent asking me top repost the whole story, or saying I have to do it manually as they cannot solve it. So why did I invest in these locks if now I have to do it manually anyway? And how is it possible that until today nobody has taken this matter seriously or at least given a decent answer or timing for solution? Even simply ignoring the customer?
In my eyes the SOLUTION could be simple.
Since Nuki is not taking the checkin/out times from Airbnb (mine are set to 15.00 - 11.00) anyway but setting fixed values 00.00 - 11.00 (how Nuki sets it), why do they not create “2 fields” under settings for the short term rentals lock allowing the host to “specify specific de:activation” times for that lock?
It cannot be that hard to create 2 fields in the existing web form sending time data to the 2 cells in the database that are now filled in with fixed values?
Anyone else experiencing these issues? Anyone having a solution for this? Anybody else has been reporting this and receiving the same ‘ingnore it’-treatment? Anyone that can help me with a workaround?
