Problems with the http lockactions at SmartLock 3.0 / Bridge environment

Hi there!

I just installed the new 3.0 with a bridge at our Entrydoor. For the first look, everthing works fine in the “Nuki Environment” (App to Bridge to SmartLock and back, also from the WAN).

Yesterday I started to integrate the Nuki via http to my Loxone system.
And now the problem:

  • / list infos work without any problems in the visualization of Loxone
  • but /lockAction do not reach the SmartLock

Here is the log for that:

0
timestamp 2021-12-02T08:41:14+00:00
type HTTP-Log
1
timestamp 2021-12-02T08:41:09+00:00
type HTTP-List
2
timestamp 2021-12-02T08:40:59+00:00
type HTTP-List
3
timestamp 2021-12-02T08:40:59+00:00
type HTTP-Log
4
timestamp 2021-12-02T08:40:49+00:00
type HTTP-List
5
timestamp 2021-12-02T08:40:39+00:00
type HTTP-List
6
timestamp 2021-12-02T08:40:39+00:00
nukiId 2BF2B57C
type BLE-Disconnected
pairIndex 0
bleHandle 0001
7
timestamp 2021-12-02T08:40:39+00:00
nukiId 2BF2B57C
type BLE-Disconnect
pairIndex 0
bleHandle 0001
8
timestamp 2021-12-02T08:40:39+00:00
nukiId 2BF2B57C
type BLE-ConnectionTimeout
9
timestamp 2021-12-02T08:40:34+00:00
nukiId 2BF2B57C
type BLE-CommandComplete
pairIndex 0
10
timestamp 2021-12-02T08:40:34+00:00
nukiId 2BF2B57C
type SSE-KeyturnerResponse
pairIndex 0
bytes 238
11
timestamp 2021-12-02T08:40:34+00:00
nukiId 2BF2B57C
type BLE-SendingSSE
pairIndex 0
bytes 56
12
timestamp 2021-12-02T08:40:34+00:00
nukiId 2BF2B57C
type BLE-TurnOnNotific
pairIndex 0
13
timestamp 2021-12-02T08:40:34+00:00
nukiId 2BF2B57C
type BLE-Connected
pairIndex 0
bleHandle 0001
14
timestamp 2021-12-02T08:40:33+00:00
type BLE-Connect
macAddr 54D272F2B57C
15
timestamp 2021-12-02T08:40:33+00:00
nukiId 2BF2B57C
type BLE-Connect
pairIndex 0
16
timestamp 2021-12-02T08:40:33+00:00
nukiId 2BF2B57C
type SSE-KeyturnerRequest
pairIndex 0
bytes 56
17
timestamp 2021-12-02T08:40:29+00:00
type HTTP-List
18
timestamp 2021-12-02T08:40:22+00:00
type HTTP-Log
19
timestamp 2021-12-02T08:40:18+00:00
type HTTP-List
20
timestamp 2021-12-02T08:40:12+00:00
type HTTP-ClearLog

The SmartLock is doing nothing…
Any ideas??

Cheers
Alex

Is your bridge running on the latest firmware?

You can check this with the /info command and force an update with /fwupdate

Its 2.10.4, and this could be the problem….
But im Not abel to force the upgrade…
Is there any Trick? Can you give me a detailed upgrade procedure Info?

Cheers
Alex

Does it fail for you with /fwupgrade (see also Nuki Developers)?
What error do you get or does it just not upgrade? (Make sure to leave the Bridge alone for some minutes after sending the request for the update to run.)

This is the latest release version. You can not update any further.

So than the firmware is not the problem…. :blush:

And no, there is no error with the update, ist gives „success“

Ah, sorry, I missed that it was already the latest version.
Than it may be the same reason I assumed in this topic:

And thats it!

I had to send also the deviceType command in the string!

Thanks guys for your input! :slight_smile:

1 Like

Quick update here:

With the latest FW update (see Nuki Bridge Firmware Release notes (public releases)) we have improved the handling to automatically fallback to known IDs for missing deviceTypes to ensure automatic general compatibility.

Cool! Good for future implementations!