Local Bridge HTTP API Unreachable – Timeout Issue

Nuki APIs Bridge
,
1

Our Goal:

We are operating a practice room booking system.
Our goal is to automatically create time-restricted PINs for customers who have booked a room.

  • We generate a 6-digit PIN.
  • The PIN should become valid 15 minutes before the booking start time.
  • The PIN should expire immediately after the booking end time.
  • We send this PIN to the customer by email.

To do this:

  • We use the Nuki Bridge HTTP API (on local network, port 8080).
  • We are sending requests directly to the Bridge to create type: 13 authorizations (keypad PINs).

Current Issue:

  • Bridge at 192.168.0.95 is not responding on port 8080 (timeout)
  • We suspect the Bridge’s IP address has changed or it has disconnected from Wi-Fi
  • We do not need remote access via Nuki Web — this is a local-only integration

Setup Summary:

  • We are using a Nuki Bridge to create and manage PINs for Keypad 2 via the local HTTP API (port 8080 on LAN).
  • Our backend server communicates directly with the Bridge using its local IP and token:
curl "http://192.168.0.95:8080/info?token=167392"
  • This setup was working previously, but now consistently times out with:
curl: (28) Failed to connect to 192.168.0.95 port 8080: Connection timed out
  • We are using Docker with network_mode: host and have confirmed the timeout occurs even outside Docker.
2

The Bridge API does not offer any command to create authorizations.
See API documentation at Bridge HTTP-API for a list of available commands.

To create authorizations you can use the Bluetooth API or the Nuki Web API.

I assume you have already been using the Nuki Web API as “type 13” for Keypad codes is used at the /smartlock/auth endpoint there.

3

Thank you for getting back to me.
We’re facing another issue:

4

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.