ronengr
ronengr
You don't know what device you have? It should be written on the package, in the instructions, in the invoice you got, etc.
I've never tested this with a built-in lock, and never with a 1.0 version. So it makes sense there are some issues. It seems that the bt char is different....
@polcape not sure i can. I don't have such lock and i didn't see it in the documentation. If you can find the documentation, or if you research the lock...
you probably need some BLE scanner. there are plenty of apps. depending if you want to run it on linux/windows/android etc.
while googling it, i found the following thread on stack overflow. maybe it will help you: https://stackoverflow.com/questions/48638870/how-can-read-all-characteristics-value-of-my-ble-device
It seems that not only the char is different but the protocol might be also a bit different. I couldn't find any documentation about the API for this lock (for...
@polcape @testos77 @MartinKlingeling The latest version (0.0.19) added support for latest Nuki API to handle gen5 locks. Could you test to see if it fixes the issue with your lock?