Homey Community Forum

[APP] Nuki Direct

There are 2 apps for the nuki, this one witch is the community app and a athom app.

For both you need the bridge, as you could read in the openings post of thus topic and for the athom app on the app page in the app store.

So sadly for you… your thoughts are right you need the bridge.

Thanks Roy!

Gotta wait for another solution then as this one would become too expensive and nello is almost dead. Maybe I have to go for a buttonpusher. Would be great to find one without bridge.

Nuki Smart Lock and Homey presence

Homey presence helps Nuki devices to become even smarter.
For example: a standalone Smart Lock can be scheduled to lock the door every evening at 22.00. A Smart Lock driven by Homey can also lock the door every evening at 22.00 but only if all family members are at home.
Another example: A Smart Lock driven by Homey can automatically lock the door when the last family member left home.

But, can Nuki devices also help Homey presence perform better? Yes, if presence in Homey adopts the proximity approach. Proximity is when a personal device (which can be associated with a specific person) is detected in the neighborhood of Homey.
For example:

  1. Homey can detect a beacon. A beacon is a small wearable device that repeatedly transmits the same Bluetooth Low Energy (BLE) signal at regular intervals.
  2. Homey can detect a smartphone connected to home Wi-Fi through network pings or TCP connections.

The proximity must be verified 24x7 and every now and then it can happen that Homey skips a beat (i.e. Homey marks a person as away because it missed a BLE advertisement or a network ping).
Here come the Nuki door sensor. Homey may assume that a proximity device is no longer nearby but this must be confirmed by the Nuki Smart Lock door sensor: if the door hasn’t been opened or closed in the last few minutes, no one could have left home!
Take a look at this flow:

In this flow there is a new condition card that allows checking if the contact alarm (the Smart Lock door sensor) changed its state in the last n seconds. If this condition is met, we can safely assume that someone has really left home.
This flow card is available in the new version of Nuki Direct that will be deployed next week.


These are really good news! :+1:t3:

Bonjour à tous.

J’ai bien compris que la serrure Nuki ne pouvait pas se connecter directement à Homey mais devait passer obligatoirement par le bridge Nuki, quelque soit l’application utilisée (Nuki Direct ou Nuki Homey).

Mais alors, quel est l’intérêt de cette application (Nuki Direct) par rapport à l’application Nuki de chez Homey ?

Et pourquoi lui avoir donné un titre trompeur (Direct) alors qu’elle ne permet pas d’associer directement la serrure et Homey ?

Merci de votre réponse.


If you could please keep the conversation in English as much as possible, then more people will be able to participate and help you. If you would rather not or can’t communicate in English then please check out Non-English boards/catregories:

Hello @AlainMic,

You asked: What are the benefits of Nuki Direct over Nuki app by Athom?
In my opinion there are several small advantages. For instance: It is slightly faster; it is more secure (in the Nuki app a single wrong tap can open the door when you are miles away from home; in my app the original tap gesture has been replaced by a swipe gesture on a slider and the slider can even be hidden in the “Advanced Settings” of the device); it is more complete (it has commands, settings, capabilities and flow cards for the specific features provided by Nuki API); it is more accurate (for example: it reports when a device is unavailable; for the Nuki app the devices are always available, even when they are really offline).

You asked: why you called your app “Direct” even if it is not able to connect directly with Nuki devices?
“Direct” just emphasizes the direct communication between Homey and Nuki Bridge within the home network (while in the Nuki app by Athom the communication between Homey and the Nuki Bridge is relayed by the Nuki servers in the cloud).
There are two strong reasons why the Homey apps do not allow a direct association with Nuki Smart Locks and Openers:

  1. If you remove the hardware bridge, you have to rewrite a “software bridge” in the Nuki app. It is very challenging. To make a comparison with thermostats: there are several Homey apps that integrate with thermostats like Tadoo or Netatmo but there are no apps that implement a “software thermostat” basing upon a temperature sensor and a relay switch.
  2. Nuki devices are Bluetooth devices and you cannot choose their position (Smart Lock on a door; Opener next to an intercom); this means that Homey (as a software bridge) should be in the Bluetooth range with every Nuki Smart Lock and/or Opener and it is pretty much impossible to comply with.

Hello Caseda.
Sorry for my message in French. I thought that a translation of my message into English and eventually into another language (if someone wants to translate into German for example), might not be clear enough.
I won’t do it again :innocent:

Hello Piero_F.
Thank you for your answer which is very clear and very accurate. After hours and hours of searching the internet, I finally figured it out. :blush::+1:Congratulations!

Nuki Direct v3.0.6 released on GitHub and soon available on Homey Community Store .


Hello @Piero_F,
whenever I restart Homey, my Nuki Smartlock and the Opener are no longer available. Both devices show a red exclamation mark.
A restart of the Nuki Direct App does not solve the problem. Only a restart of my WLAN repeater solves the problem although Homey and the Nuki Bridge have a fixed IP address.
Homey FW v5.0.0-rc.38
Nuki Direct v3.0.6

Do you have an idea what the problem could be?

Hello @fantross,

It could be a problem related to what you asked two months ago (the network error EHOSTUNREACH).

When Nuki Direct 3.0.6 is started, it makes some sanity checks. The first check is the callback URL check: it checks whether the Nuki Bridge(s) has the correct callback URL in order to fire Nuki events to Homey.

The request is similar to the following:

http: ∕ ∕ ∕ callback ∕ list?token=XXXX (where IP address, port and token must be replaced by the actual values).

I guess that such request receives a negative response (or no response at all) and this causes Nuki Direct to mark the devices as unavailable.

A suggestion: When Homey is in the error condition (after a restart), you can try a pairing procedure. The pairing procedure causes Nuki Direct to send some HTTP requests to the selected Nuki Bridge and to print a detailed report about the received responses. This may help the analysis.

Where can I find the detailed report about the received responses?

In the pairing procedure I do expect a pairing failure similar to the following:

1 Like