Nuki not working

[weeman1337]

Operating a nuki smart lock device isn't working.

I followed the guide from the documentation.
When pressing to "open" button that should connect the device I always get "Device is not in paring mode.".

• Installed the latest version from F-Droid
• On an Android 9 device.

If I can provide any other information that helps debugging just let me know.

[mwarning]

Have you paired with the Nuki before?

• Once on the Bluetooth level
• Once for registering your device with the Nuki

[mwarning]

btw. has it been working before for you?

[weeman1337]

Have you paired with the Nuki before?

Yes, I paired the phone with the lock.

btw. has it been working before for you?

No.

It works using the proprietary app.

[mwarning]

hm, this is hard to debug, since it was working for me recently.

[mwarning]

You do not happen to be in Berlin? :P

[mwarning]

Do you know the version of the Nuki Smartlock firmware and what version of the Nuki SmartLock this is?

[weeman1337]

hm, this is hard to debug, since it was working for me recently.

I can poke around in the code if you want and try things or write more debug output.

You do not happen to be in Berlin? :P

Nope. But if you visit Frankfurt in the next time… ;)

Do you know the version of the Nuki Smartlock firmware and what version of the Nuki SmartLock this is?

It is a Smart Lock 2.0 running firmware 2.11.8

[mwarning]

hm, this is hard to debug, since it was working for me recently.

I can poke around in the code if you want and try things or write more debug output.

Yes please. Anything that helps us with figuring out the problem.

You do not happen to be in Berlin? :P

Nope. But if you visit Frankfurt in the next time… ;)

hehe, ok.

Do you know the version of the Nuki Smartlock firmware and what version of the Nuki SmartLock this is?

It is a Smart Lock 2.0 running firmware 2.11.8

hm, should work..

[weeman1337]

Here are the adb logs when trying to connect

11-02 18:59:25.114 10011 10910 D BluetoothGatt: connect() - device: xx:xx:xx:xx:xx:xx, auto: false
11-02 18:59:25.114 10011 10910 D BluetoothGatt: registerApp()
11-02 18:59:25.114 10011 10910 D BluetoothGatt: registerApp() - UUID=yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
11-02 18:59:25.116  8675  8722 I bt_stack: [INFO:gatt_api.cc(948)] GATT_Register dddddddd-dddd-dddd-dddd-ddddddddddd
11-02 18:59:25.116  8675  8722 I bt_stack: [INFO:gatt_api.cc(968)] allocated gatt_if=5
11-02 18:59:25.117 10011 10858 D BluetoothGatt: onClientRegistered() - status=0 clientIf=5
11-02 18:59:25.121  8675  8697 D bt_btif_config: btif_get_address_type: Device [xx:xx:xx:xx:xx:xx] address type 0
11-02 18:59:25.121  8675  8697 D bt_btif_config: btif_get_device_type: Device [xx:xx:xx:xx:xx:xx] type 2
11-02 18:59:25.123  8675  8722 I bt_stack: [INFO:gatt_api.cc(1109)] GATT_Connectgatt_if=5 xx:xx:xx:xx:xx:xx
11-02 18:59:25.124   532   532 D vendor.qti.bluetooth@1.0-ibs_handler: SerialClockVote: vote for UART CLK ON
11-02 18:59:25.128   532   532 D vendor.qti.bluetooth@1.0-wake_lock: Acquire wakelock is acquired 
11-02 18:59:25.128   532   532 I vendor.qti.bluetooth@1.0-ibs_handler: DeviceWakeUp: Writing IBS_WAKE_IND
11-02 18:59:25.131   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_ACK: 0xFC
11-02 18:59:25.132   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:25.133   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:25.173   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:25.745   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:25.745   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:25.748  8675  8722 I bt_btm_ble: btm_ble_conn_complete unable to match and resolve random address
11-02 18:59:25.776  8675  8722 W bt_smp  : smp_br_connect_callback is called on unexpected transport 2
11-02 18:59:25.777  8675  8722 E bt_stack: [ERROR:gatt_sr.cc(752)] MTU request PDU with MTU size 247
11-02 18:59:25.777  8675  8722 E bt_btm  : BTM_SetBleDataLength failed, peer does not support request
11-02 18:59:25.778  8675  8722 W bt_stack: [WARNING:gatt_utils.cc(710)] Call back not found for application conn_id=3
11-02 18:59:25.778  8675  8722 W bt_stack: [WARNING:gatt_utils.cc(710)] Call back not found for application conn_id=4
11-02 18:59:25.778  8675  8722 W bt_stack: [WARNING:gatt_utils.cc(710)] Call back not found for application conn_id=5
11-02 18:59:25.778  8675  8722 W bt_btif : bta_dm_acl_change info: 0x0
11-02 18:59:25.779  8675  8722 I bt_stack: [INFO:bta_gattc_cache.cc(915)] bta_gattc_rebuild_cache 81
11-02 18:59:25.780  8675  8697 D bt_btif_dm: remote version info [xx:xx:xx:xx:xx:xx]: 0, 0, 0
11-02 18:59:25.789  8675  8722 E bt_btm  : No key available to encrypt the link
11-02 18:59:25.789 10011 10858 D BluetoothGatt: onClientConnectionState() - status=0 clientIf=5 device=xx:xx:xx:xx:xx:xx
11-02 18:59:25.789 10011 10858 D BluetoothGatt: discoverServices() - device: xx:xx:xx:xx:xx:xx
11-02 18:59:25.796  8675  8697 E bt_btif_gattc: btif_gattc_upstreams_evt: Unhandled event (7)!
11-02 18:59:25.797  8675  8697 I chatty  : uid=1002(bluetooth) BT Service Call identical 8 lines
11-02 18:59:25.797  8675  8697 E bt_btif_gattc: btif_gattc_upstreams_evt: Unhandled event (7)!
11-02 18:59:25.801  8675  8697 D bt_bta_gattc: bta_gattc_get_gatt_db
11-02 18:59:25.810 10011 10858 D BluetoothGatt: onSearchComplete() = Device=xx:xx:xx:xx:xx:xx Status=0
11-02 18:59:25.810 10011 10858 D BluetoothGatt: setCharacteristicNotification() - uuid: tttttttt-tttt-tttt-tttt-tttttttttttt enable: true
11-02 18:59:25.858   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:25.864   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:25.864   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:25.906   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:25.954   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:25.955   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:25.964  8675  8722 I bt_stack: [INFO:hearing_aid.cc(1430)] GetDeviceCount: Not initialized yet
11-02 18:59:26.039   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:26.044   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:26.044   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:26.086   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:26.089   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:26.089   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:26.100 10011 10858 D BluetoothGatt: close()
11-02 18:59:26.101 10011 10858 D BluetoothGatt: unregisterApp() - mClientIf=5
11-02 18:59:26.109  8675  8722 I bt_stack: [INFO:gatt_api.cc(1212)] GATT_Disconnect conn_id=5
11-02 18:59:26.115  8675  8697 E BtGatt.ContextMap: Context not found for ID 5
11-02 18:59:26.130   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:26.133   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:26.133   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:26.168   924  5509 W NotificationService: Toast already killed. pkg=com.example.trigger callback=android.app.ITransientNotification$Stub$Proxy@941bc6c
11-02 18:59:26.174   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:26.185   580   615 D SurfaceFlinger: duplicate layer name: changing Toast to Toast#1
11-02 18:59:26.358   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:26.358   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:26.399   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:27.097   532  8725 I vendor.qti.bluetooth@1.0-ibs_handler: DeviceSleep: TX Awake, Sending SLEEP_IND
11-02 18:59:27.098   532  8725 D vendor.qti.bluetooth@1.0-ibs_handler: SerialClockVote: vote for UART CLK OFF
11-02 18:59:27.113   532   532 D vendor.qti.bluetooth@1.0-ibs_handler: SerialClockVote: vote for UART CLK ON
11-02 18:59:27.114   532   532 I vendor.qti.bluetooth@1.0-ibs_handler: DeviceWakeUp: Writing IBS_WAKE_IND
11-02 18:59:27.119   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_ACK: 0xFC
11-02 18:59:27.120   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_WAKE_IND: 0xFD
11-02 18:59:27.120   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Writing IBS_WAKE_ACK
11-02 18:59:27.134  8675  8722 W bt_stack: [WARNING:bta_gattc_act.cc(1040)] bta_gattc_conn_cback: cif=3 connected=0 conn_id=0x0003 reason=0x0016
11-02 18:59:27.135  8675  8722 W bt_stack: [WARNING:bta_gattc_act.cc(1040)] bta_gattc_conn_cback: cif=4 connected=0 conn_id=0x0004 reason=0x0016
11-02 18:59:27.135  8675  8722 I bt_btm_sec: btm_sec_disconnected clearing pending flag handle:11 reason:22
11-02 18:59:27.137  8675  8697 I btif_av : btif_av_acl_disconnected: Peer xx:xx:xx:xx:xx:xx : ACL Disconnected
11-02 18:59:27.137  8675  8722 I btif_av : BtifAvPeer *BtifAvSource::FindOrCreatePeer(const RawAddress &, tBTA_AV_HNDL): Create peer: peer_address=xx:xx:xx:xx:xx:xx bta_handle=0x41 peer_id=0
11-02 18:59:27.138  8675  8722 W bt_btif : btif_av_get_peer_sep: No active peer found
11-02 18:59:27.138  8675  8722 I bt_btif_a2dp: btif_a2dp_on_idle: ## ON A2DP IDLE ## peer_sep = 1
11-02 18:59:27.138  8675  8722 W bt_btif : btif_av_get_peer_sep: No active peer found
11-02 18:59:27.138  8675  8722 I bt_btif_a2dp_source: btif_a2dp_source_on_idle: state=STATE_OFF
11-02 18:59:27.138  8675  8722 W bt_btif : btif_av_get_peer_sep: No active peer found
11-02 18:59:27.139  8675  8722 I bt_btif_a2dp: btif_a2dp_on_idle: ## ON A2DP IDLE ## peer_sep = 1
11-02 18:59:27.139  8675  8722 W bt_btif : btif_av_get_peer_sep: No active peer found
11-02 18:59:27.139  8675  8722 I bt_btif_a2dp_source: btif_a2dp_source_on_idle: state=STATE_OFF
11-02 18:59:27.139  8675  8722 I btif_av : DeleteIdlePeers: Deleting idle peer: xx:xx:xx:xx:xx:xx bta_handle=0x41
11-02 18:59:27.158  8675  8675 D BluetoothMapService: onReceive: android.bluetooth.device.action.ACL_DISCONNECTED
11-02 18:59:27.170   532  8719 I vendor.qti.bluetooth@1.0-ibs_handler: ProcessIbsCmd: Received IBS_SLEEP_IND: 0xFE
11-02 18:59:28.120   532  8725 I vendor.qti.bluetooth@1.0-ibs_handler: DeviceSleep: TX Awake, Sending SLEEP_IND
11-02 18:59:28.120   532  8725 D vendor.qti.bluetooth@1.0-ibs_handler: SerialClockVote: vote for UART CLK OFF
11-02 18:59:28.149   924  5509 W NotificationService: Toast already killed. pkg=com.example.trigger callback=android.app.ITransientNotification$Stub$Proxy@807f522
11-02 18:59:28.271   532  8711 D vendor.qti.bluetooth@1.0-wake_lock: Release wakelock is released 
11-02 18:59:28.651   924  1058 W WindowManager: Unable to start animation, surface is null or no children.

Maybe that helps you already 🤷‍♂️

[mwarning]

That does not look very helpful.
Anyway, what Android version do you use?

[vmario89]

I have similar problem with Nuki not working, but i am not able to pair. The question is: does Trigger work with Nuki Smartlock, if the Smartlock is already paired with the Nuki Web Bridge?

[mwarning]

Actually, I do not know.

Best thing would be if I can debug the situation. I can try to update the firmware on my nuki and see if that breaks anything :D

EDIT: if you can use the Nuki Web Bridge in parallel with the Nuki App (via Bluetooth), then it should also work with Trigger

[mwarning]

btw., is that a Nuki Smartlock 3? What firmware version do you use? I just saw that it came out.

[vmario89]

Hey,
not its a Nuki Smartlock with first revision ever available on the market (about 3 years old). I have no idea to get some logs out of this on my Smartphone yet. I have a Huawei phone. Just my some documentation for myself right now:

the errors while trying to pair (while nuki ring is lighting constantly white) are: failed to pair or "just look in the app"

[mwarning]

Ok, without having a Smartlock of that version to debug the issue, it will be very hard to debug/fix this. Maybe there is some documentation available for the Nuki 1...