Hi everyone, I’m reaching out to seek some assistance with a challenge I’m facing while working with the Nuki 1.0 smart lock. I’ve successfully paired my device with the Nuki 2.0 model using a specific codebase, but when attempting to do the same with the Nuki 1.0, I’m encountering some unexpected issues.
To provide some context, I’ve developed a system using an ESP32 microcontroller that connects to the Nuki locks. The process involves scanning for the pairing service, connecting to the device, registering for notifications, enabling indications, and then sending the necessary commands to create a user. This approach works flawlessly with the Nuki 2.0, but when I tried it with the Nuki 1.0 (firmware version 1.8.1), I ran into a snag.
After successfully receiving the shared key from the lock, I noticed that the corresponding indication was received, but shortly after, the connection was lost. I’ve retraced my steps multiple times, ensuring that all commands are sent correctly and in the right sequence, as per the API documentation for the Nuki 2.0. Despite this, the issue persists.
I’m wondering if there might be differences in the firmware or protocol handling between the Nuki 1.0 and 2.0 models that I’m not accounting for. Could there be specific commands or parameters required for the Nuki 1.0 that aren’t necessary for the 2.0? I’m also curious if others in the community have encountered similar issues and if there are known workarounds or solutions.
Any insights or suggestions would be greatly appreciated. I’m eager to resolve this and would be happy to provide additional details if needed. Thanks in advance for your help!