An update of our Nuki ESP32 BLE library caused some issues with users. We have been able to solve this but while troubleshooting we have been seeing strange behaviour for 1 user.
He has a Nuki Smart Lock V3, running fw version 3.4.10.
We are seeing a, to me unknown, UUID “01601cf5f0d430060001000102ed9b91” advertising from the Nuki Smart lock.
We are logging the following format:
time > BT address sending data | UUID we are expecting (the keyturner service UUID) | the UUID that is advertising
13:28:59.506 > 54:d2:72:c3:35:c5 | a92ee200-5501-11e4-916c-0800200c9a66 | 01601cf5f0d430060001000102ed9b91 13:29:00.530 > 54:d2:72:c3:35:c5 | a92ee200-5501-11e4-916c-0800200c9a66 | a92ee200550111e4916c0800200c9a66 13:29:00.540 > [D][NukiBle.cpp:225] onResult(): Nuki Advertising: Name: Nuki_33C335C5, Address: 54:d2:72:c3:35:c5, manufacturer data: 4c000215a92ee200550111e4916c0800200c9a6633c335c5c8 13:29:00.556 > [D][NukiBle.cpp:237] onResult(): iBeacon ID: 004C Major: 13251 Minor: 13765 UUID: a92ee200-5501-11e4-916c-0800200c9a66 Power: -56 13:29:00.567 >
The first line contains UUID “01601cf5f0d430060001000102ed9b91” which is unknown to me.
The second line is what is the “normal” keyturner service uuid
We have been unsuccessful in reproducing this (except for this one user).
User tried to eliminated the possibility that this is coming from other devices by turning off BT on laptop and phones and trying it on a different location but no result.
Do you recognize this UUID?
If yes is this new and what is the functionality?