invalid Nuki command

[Ulli2k]

Hi,
I tried your pyBridge for my Nuki Lock, but it did not work.
I got the following output:

Starting BLE adapter...
Init Nuki BLE connection...
Nuki BLE connection established
Nuki Pairing UUID handle created: 001f
Requesting Nuki Public Key using command: Nuki_REQ
    Payload: Nuki_PUBLIC_KEY
Nuki Public key requested
command = 0003, payload = a3fb656951aaaa171df1513293519334, crc = 5d06
Public key received: a3fb656951aaaa171df1513293519334
Pushing Public Key using command: Nuki_PUBLIC_KEY
    Key: 40164d2bdbd684136f14d68a2e7d2ed3bb352526036bdde204c0f6d548ecc71b
Public key pushed
Error while pushing public key: 70ae7d56c6c11b19fe66640bb15c23a604007ec8c43141d4913402d8a09415991206e63d does not seem to be a valid Nuki command

I would appreciate your support.
Thanks a lot in advance.
Ulli

[jandebeule]

Hi Ulli,

Strange issue you having there. The thing is that the message you get back from the Nuki lock when pushing your public key to it seems to be an encrypted one and that is unexpected because during these first steps of the authentication process we communicate over the unencrypted channel.
I asked the guys of Nuki (on Slack) to look into it and they requested that you performed the same thing another couple of times to see if the message that you get back is always the same. Could you do that and post the logs here?

Thanks!
Jan

[Ulli2k]

hi Jan, I already asked the Nuki Team but it looks like they did not look deep into the issue because they told my to send that issue to the developer of the nukiPyBridge.... ;( I tried it several times and I always get the same error. Is it maybe because of an firmware update from Nuki? Have you already tried the PyBridge with the current available firmware? Thanks a lot for your support! Regards, Ulli Am 09.01.2017 8:55 vorm. schrieb "jandebeule" <notifications@github.com>:

…

Hi Ulli, Strange issue you having there. The thing is that the message you get back from the Nuki lock when pushing your public key to it seems to be an encrypted one and that is unexpected because during these first steps of the authentication process we communicate over the unencrypted channel. I asked the guys of Nuki (on Slack) to look into it and they requested that you performed the same thing another couple of times to see if the message that you get back is always the same. Could you do that and post the logs here? Thanks! Jan — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANfJ_ebpsJi93QQEpIRFy_iYLl0KpS95ks5rQef3gaJpZM4Lczoh> .

[jandebeule]

I should check if there is a firmware update available, but normally I should be on the latest (beta) firmware. When you say you always get the same error, does it mean you always get the same message (0x70ae...) back?

[Ulli2k]

I will check that today evening... Am 09.01.2017 1:28 nachm. schrieb "jandebeule" <notifications@github.com>:

…

I should check if there is a firmware update available, but normally I should be on the latest (beta) firmware. When you say you always get the same error, does it mean you always get the same message (0x70ae...) back? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANfJ_TM6typ31ZBNY70J8abBf4SyOMk3ks5rQif_gaJpZM4Lczoh> .

[Ulli2k]

No I just wanted to say that it is always the same kind of error. I did some more tries which you can find in the following: ulli@ThinkPad:~/Downloads/nukiPyBridge$ python authenticate.py Starting BLE adapter... Init Nuki BLE connection... Nuki BLE connection established Nuki Pairing UUID handle created: 001f Requesting Nuki Public Key using command: Nuki_REQ Payload: Nuki_PUBLIC_KEY Nuki Public key requested command = 0003, payload = a58f3b211f34ccd1c301b9761df915f0, crc = e58e Public key received: a58f3b211f34ccd1c301b9761df915f0 Pushing Public Key using command: Nuki_PUBLIC_KEY Key: 2ebc9aeb1fe3ce478b1d4cf9fc2a4e94c217db808c6b0e3bd344251dfd39a701 Public key pushed Error while pushing public key: 1b596f8f5fee1b9b0a8ff1cff62b6efc04007f46b409e388a1347e1fdfb8b8e0545818e1 does not seem to be a valid Nuki command ulli@ThinkPad:~/Downloads/nukiPyBridge$ python authenticate.py Starting BLE adapter... Init Nuki BLE connection... Nuki BLE connection established Nuki Pairing UUID handle created: 001f Requesting Nuki Public Key using command: Nuki_REQ Payload: Nuki_PUBLIC_KEY Nuki Public key requested command = 0003, payload = 4000b4c9be0b6c2441671d6cc8ccc439, crc = 472f Public key received: 4000b4c9be0b6c2441671d6cc8ccc439 Pushing Public Key using command: Nuki_PUBLIC_KEY Key: 4b2cd64b5d25480c4ed3c26733d426dff4f29f41f2d2e028de1093cd889a312f Public key pushed Error while pushing public key: dd79c7bd1b080fb258d149e24b67781d04005521f34096dcc703c97ed1a7150247c1987a does not seem to be a valid Nuki command ulli@ThinkPad:~/Downloads/nukiPyBridge$ python authenticate.py Starting BLE adapter... Init Nuki BLE connection... Nuki BLE connection established Nuki Pairing UUID handle created: 001f Requesting Nuki Public Key using command: Nuki_REQ Payload: Nuki_PUBLIC_KEY Nuki Public key requested command = 0003, payload = 0d89f50fbcd9b02d5c7939cef722d565, crc = 618e Public key received: 0d89f50fbcd9b02d5c7939cef722d565 Pushing Public Key using command: Nuki_PUBLIC_KEY Key: b27d592ecdf8a4ec38f4a3bf2c23b0f34ff30e02916bd47511fc6cd40f951b55 Public key pushed Error while pushing public key: f26a1d66de24dd4b2d163840db5cd08a040043f2a1d7633ccd9e032fc2d4ea7847758751 does not seem to be a valid Nuki command Am 09.01.2017 um 13:28 schrieb jandebeule:

…

I should check if there is a firmware update available, but normally I should be on the latest (beta) firmware. When you say you always get the same error, does it mean you always get the same message (0x70ae...) back? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANfJ_TM6typ31ZBNY70J8abBf4SyOMk3ks5rQif_gaJpZM4Lczoh>.

[Ulli2k]

Did you already get an answer from the nuki team or did you check if you are using the last firmware?

[jandebeule]

I did get response back from the nuki team but they can also not explain the response you are getting back when pushing your public key. The only explanation I can come up with is that you are not getting the full response (and thus my library is misinterpreting the message as it is only a part of the real message sent by the lock). I think the gatttool may be involved (which I did not write myself, but had to alter slightly to get reliable responses back from the Nuki lock). I altered that library and it was a bit trial and error to get it good on my raspberry pi. If I'm not mistaken you are using a different device to talk with the Nuki lock so maybe that's the reason. However, currently I don't have much time to investigate it further. Sorry about that.

[Ulli2k]

:(

[kraeki]

I had the same issue but I forgot to execute step 5 as described in the README. After copying gatttool.py it worked.

Also I would probably mention in the wiki that the device needs to be calibrated once (maybe using a cell phone) before it can be controlled with this python code.

If I find some time I will send you a pull-request.