Android app compatibility

[filipnavara]

The simulated lock is not compatible with the Nuki Android app, which doesn't see it at all.

The first problem is that the Android application expects the BLE advertising data in an exact format, which differs from what SimNuki sends. The difference is the length of the advertising data, which seems to be 0x15 for a real Nuki, but only 0x11 for a simulated one. Seems relatively easy to workaround by modifying main.js line 87 from

var advDataBuf = Buffer.concat([typeBuf, uuidReverseBuf]);

to

var nullBuf = new Buffer([0, 0, 0, 0]);
var advDataBuf = Buffer.concat([typeBuf, uuidReverseBuf, nullBuf]);

I am not exactly sure what real Nuki sends in these additional four bytes, but the Android application doesn't seem to care about it.

The second problem is that the authorization gets abruptly terminated after step 19. I've tried to examine the communication by hand and I didn't see anything out of the ordinary when comparing it to the official specification.

[filipnavara]

Seems like the abrupt termination after step 19 is a problem with the underlying Bluetooth connection, possibly caused by Android, some application, and a combination of bleno settings. I have replicated the entire pairing process with my own code on RedBear Duo and it doesn't suffer from the same problem.

The Nuki Smart Lock Bluetooth API has been updated to version 1.10 in November/December 2017 and includes new APIs that are used by the Android application. Notably, the "Request Advanced Config" API call is sent during the initial pairing sequence.

[tfischer4765]

I can confirm this issue exists, and also that the fix proposed above is effective to some extent. I couldn't complete the pairing process, because I ran into #4.