Smoobu integration

I was testing Smoobu integration last two days. In order to see bookings on nuki web I have to manually update it on web. After bookings appear, invitations are being send automatically. Should it not be automatically? Or it works like that? I tired to re-connect but same behaviour.

And additional questions. I have connected AirBnb and Smoobu, and off course I handle AirBnb with Smoobu. If somebody would book AirBnb how shall a guest get invitation codes? Over AirBnB plugin or Smoobo, or maybe both? Do I need to disconnect AirBnB from Nuki then?

Hello Stephan,
in the settings i have set that invitations will only be sent to me. If I deactivate an account by hand, the guest receives the deactivation email via Nuki> Smoobu>
Is that the intention? Will there be a possibility in the future to get more control over the function or to connect to Smoobu using api instead?
Regards, Hans-Jörg

i can confirm this behaviour.
I have to manually press “refresh” in nuki web for updating the new bookings/cancellations/rebookings.
I even could activate/deactive canceled bookings from smoobu in nuki web.
Seems the update routine is not working as expected.

stil not working no reservations show up
even the airbnb connection seems now broken

please do only beta tests with end useres, not alpha. airbnb and smoobu customers earn their money with it.

We still have an issue with Airbnb-bookings coming through Smoobu due to an error in the API-documentation. We are currently testing the fix internally before we roll it out.
General connection issue should be fixed after reconnecting once (keeping in mind the remaining one described above).

@gramels: What issues do you have with the Airbnb-integration (which should not be affected from the Smoobu-problem)? The connection issues we had there had a different cause (changes on their API which have not been handled correctly automatically).

I do not see any bookings, neither via smoobu nor via airbnb direct connection.

deleted all connections reinstalled, stil no bookings (eg airbnb guests coming tomorrow)

the deletion of the connection is not well documented, it is quite confusingt that using the add butten one could also disconnect

further the beta site colides with the normal NUKI side, I alway have to re log in which is very annoyng using 2fa

it continiously gives me this

Error code: 400
API endpoint:
HTTP method: GET
Nuki Web Account: l*******@*****************.ch
Occured: 2020-05-20T06:04:52.316Z UTC

{“detailMessage”:“The supplied value ‘1611205594’ for parameter ‘addressId’ is not valid"¸"stackTrace”:[]¸"suppressedExceptions":[]}

Hi Stephan,

Keep up the good work; things seem to have become more and more stable recently!
One thing i noticed is that in the beginning of the beta, my codes seemed to be valid from 0:00 on arrival date until 23:59 on departure date. I found that very comfortable, knowing that my guests would always be able to enter and leave.

I understand this is not always wished for behaviour, and it seems that nuki now looks at the check-in and check-out times listed in smoobu, correct? Unfortunately, these times are not always accurate, because they are based on information passed on by channels connected to Smoobu. But OK; not Nuki’s problem :slight_smile:

My request would be to enable a ‘grace period’-setting where we can define an amount of hours of margin before checkin time and after checkout time for people to use the code.

If checkin-time is 14:00, i would set it to 2 hours for example for the code to work from 12:00 onwards. Checkout-time 11:00 would work until 13:00 in that case.

Any chance something like this would be possible?


Thanks. We are still working on further improvements!

We had this discussion already; the main problem is that some hosts don’t want to have any “grace period” at all; so the only way would be to have another setting - making things more complicated as to when the settings has to be done and how to handle changes of the booking afterwards etc.

On the other hand: Could the bookings details be changed in Smoobu to reflect the real “allowed time to enter” for guests?

Hi Stephan,

The additional setting is indeed what I would see as the best solution so that it fits every host with different requirements; it could be included in the ‘settings’-panel that is already there, that is now used to determine, for instance, the nuki opener timings and whether to send a keycode and appcode or just keycode. The setting should be general; for all bookings for that accomodation, so should not complicate the current process of managing changed bookings.

I don’t think it is possible to handle this in Smoobu, as the ‘check-in’-time parameter is often filled by third parties such as and Expedia etc and is symantically something different then the ‘allowed to enter’ time. If the general setting is available, it would just be an addition and substraction on your side for every booking, for every generated code :wink:

Same as Igorr and Michael, i found the same issue: The update is not done automatically, i have to click the refresh button in order for the key to be sent and bookings updated.

“I was testing Smoobu integration last two days. In order to see bookings on nuki web I have to manually update it on web. After bookings appear, invitations are being send automatically. Should it not be automatically? Or it works like that? I tired to re-connect but same behaviour.”

One more thing that i forgot to mention…

It’s not clear when the entrance code is generated wether is active starting from 3 days before the client arrives or only on the arrival date.

What should happen:

  • Booking should automatically shown for the upcoming 7 days
  • Sync is done in intervals so this is not real time
  • Authorizations are created x days before arrival day, based on you settings (Default: 3)
  • You can manually trigger this earlier, as soon as you see it listed
  • You can also manually delete authorizations, but in general everything should work automatically
  • All authorizations are valid from arrival day to departure day (from check-in time to check-out time, if those are set)

It is unclear to me from your description at which point it differs from that list in your experience.

Hello Stephan, another final email in “Du” form by Nuki was sent directly to guests, asking them to remove the Smartlock from the app. But I have in the settings:

  • Confirmation email only to me
  • Use keypad only
    Everything else works perfectly for me, I copy the generated key into my own mail template in the smoobu platform.
    I am happy if there is an api-solution for handing it over to Smoobu. I would very much like to have control over the sending of emails.
    Keep up the excellent work, regards, Hans-Jörg

This mail is sent to my guests after checkout:

Nuki Zugang abgelaufen für Smoobu Buchung 5224568

Hallo #########!
Deine Nuki Zutrittsberechtigung für die folgende Unterkunft ist
Öffne diese E-Mail auf deinem Smartphone und klicke auf den Button, um
das Nuki Smart Lock aus deiner Nuki App zu entfernen:
Smart Lock Name
Hochwartblick — Jetzt entfernen
Eingang — Jetzt entfernen
Beste Grüße,
dein Nuki-Team
Copyright © 2020 Nuki Home Solutions GmbH
Unsere Adresse:
Münzgrabenstraße 92/4
8010 Graz
Impressum AGB Datenschutz


overall I like the NNUKI smoobu integration. Some flaws:

*2h later locking after chekout or configurable
*no confusing standard NUKI mail sent to guests.
*alse let me set the good by mail address not only the welcome address
*mails send through smoobu and not by NUKI
*key codes and login url sent to smoobo via api I so I can configure mails to guests in smoobu
*robustness tests of the API
*keycodes seems empty, even one was set by NUKI and send in email

keep up the good work but test hard. Do not confuse my guests with strange emails, this is huge effort for hosts.


It seems we´re lost and left alone here :unamused:

We are working on improving that flow together with Smoobu.

This is already in testing and should be available soon for Smoobu. Im am not sure though what you mean by “login url”

In general:
Our default emails are being reviewed, but they are “default”, so something that tries to fit for all users. So we agree that the best way to go is to handle the communication within your PMs.

key codes are sent now to smoobu via api, thank you very much

1 Like