2 Smartlocks with 2 Bridges, Callback not working properly

Nuki APIs Bridge HTTP-API
#1

Hi,

I got two sets of a SmartLock and Bridge.

Set 1:
Bridge:
“firmwareVersion”: “1.13.1”,
“wifiFirmwareVersion”: “1.2.0”

SmartLock HardwareVersion 2.0

Set 2:
Bridge:
“firmwareVersion”: “2.2.13”,
“wifiFirmwareVersion”: “2.0.0”
SmartLock HardwareVersion 2.0

For the first set I added a callback to the bridge and it works fine.

I also added a callback for the second set, but callback is not working and also the led at the bridge is not blinking in the way of the other bridge.

Also the same set on an other location / customer has the same behavior.

Any idea? Or Firmware bug?

Uli

#2

push

some additional information:

NUKI Bridge 1 Devices:

Blockquote
[
{
“deviceType”: 0,
“nukiId”: 123456789,
“name”: “Nuki Smart Lock”,
“firmwareVersion”: “2.5.4”,
“lastKnownState”: {
“mode”: 2,
“state”: 1,
“stateName”: “locked”,
“batteryCritical”: false,
“timestamp”: “2019-09-30T19:59:43+00:00”
}
},
{
“deviceType”: 2,
“nukiId”: 234567890,
“name”: “Nuki Opener”,
“firmwareVersion”: “1.1.10”,
“lastKnownState”: {
“mode”: 2,
“state”: 1,
“stateName”: “online”,
“batteryCritical”: false,
“timestamp”: “2019-09-29T19:48:26+00:00”
}
}
]

NUKI Bridge 1 Callback:

Blockquote
{
“callbacks”: [
{
“id”: 0,
“url”: “http://192.168.1.100:8081”
}
]
}

NUKI Bridge 2 Devices:

Blockquote
[
{
“deviceType”: 0,
“nukiId”: 3456789012,
“name”: “SmartLock 2”,
“lastKnownState”: {
“mode”: 2,
“state”: 1,
“stateName”: “locked”,
“batteryCritical”: false,
“timestamp”: “2019-10-01T01:02:32+00:00”
}
}
]

NUKI Bridge 2 Callback:

Blockquote
{
“callbacks”: [
{
“id”: 0,
“url”: “http://192.168.1.100:8081”
}
]
}

Any idea?

#3

Sorry for the late reply (and thanks for the additional details).

I see no reason for the callback failing with the data you provided. :thinking:
Are you able to try another callback URL?

#4

Hi Stephan,

thanks for your reply.

First I deleted all callbacks from Bridge 1 and Bridge 2.

Then I tried only to use a callback for Bridge 2, it failed.

So I decided to do a factory reset for Bridge 2 and Smart Lock 2 and reinstalled and paired them together again.

After that I added the callback for the first Bridge.

Now everything works fine. I am wondering why at another installation / place the same behavior exists!?!?!

So for this moment the problem is solved.

Uli

#5

Sorry, I was too fast. After adding the second callback, the first call back from Bridge 2 is not working anymore.

Also different server sockets for both Bridges won’t help.

So what can I do more!?!?!

Uli

#6

Could you send me /callback/list for the 2 callbacks you now have on Bridge 2 (not working).
I want to reproduce your exact setup here with me as close as possible.

#7

Stephan,

I did a deeper investigation right now and tested more scenarios.

First of all I use IP-Symcon (https://www.symcon.de/) as the server socket.

Bridge 1 with Firmware 1.13.1 is working perfectly.

But the issue is on Bridge 2 with Firmware 2.2.13, that is reproducible now.

Once I start the server socket on IP-Symcon the first callback of Bridge 2 is coming in. But then it seems to be that the bridge get stuck for the next callbacks.

I already informed the developer of IP-Symcon to investigate also this issue. But as I told you, Bridge 1 is working perfectly under the same scenario.

Should I send you the output of /list as a PN ? Do you need the reel Nuki IDs? Or can I anonymous the data?

Uli

#8

Yes, a PN with the data would help, but I don’t need real Nuki IDs.

#9

Send you a PN!

I would like to clearfy that I have two bridges but each bridge has only one callback. So in total two callbacks, one from Bridge number 1 and the other from bridge number 2.

Uli