Keyturner States (0x000C) Trigger always 0x00 on Nuki Lock 4

Nuki APIs Bluetooth API
1

Hello Nuki Team,

I’m new to Nuki and the BLE API. I’ve played around with NukiBleEsp32. But I always receive a 0x00 for Keyturner States Trigger. So I can use the button, manual lock or the Keypad 2.0. It will never change.

I just update to the 4.2.0 beta to check if it is fixed, but it is still not working as I would expect.

Here some examples:

keyturnerStates: 02 01 00 e8 07 03 05 14 30 06 00 00 c8 1a 00 02 01 00 00 00 01 03 00 00 f0 00 00
keyturnerStates: 02 03 00 e8 07 03 05 14 30 13 00 00 c8 1a 00 01 01 00 00 00 01 03 00 00 f0 00 00
keyturnerStates: 02 03 00 e8 07 03 05 14 31 33 00 00 c8 1a 00 03 00 02 00 00 01 03 00 00 f0 00 00
keyturnerStates: 02 03 00 e8 07 03 05 14 33 3b 00 00 c8 1a 00 03 00 02 00 00 01 03 00 00 f0 00 00
keyturnerStates: 02 01 00 e8 07 03 05 14 38 39 00 00 c8 1b 00 02 01 00 00 00 01 03 00 00 f0 00 00
keyturnerStates: 02 03 00 e8 07 03 05 15 0e 1f 00 00 c8 1f 00 01 02 00 00 00 01 03 00 00 f0 00 00 
keyturnerStates: 02 01 00 e8 07 03 05 15 11 32 00 00 c8 1f 00 02 02 00 00 00 01 03 00 00 f0 00 00
3

Hi @cso ,

thanks for pointing this out, apparently the trigger is not correctly set internally. We will take a closer look into this.

4

Great, Thank you. But the current 4.x is a bit broken for the BLE API. The Log and Authorization is also not working properly. At the moment I’m on 4.2.4. In 4.2.3 Log and Authorization was working. But I’ll move with my topic to the Beta thread.