Moritz Warning

I have asked a related question in the nuki forum: https://developer.nuki.io/t/bluetooth-api-for-nuki-1-0-2-0-3-0-compatibility/13722

@vmario89 anyway, if you are not able to pair, then it does not have anything to do with Trigger.

I am not certain, but I think I used the API specs V2.1 from 16.03.2020. The last time I was testing with my Nuki Smart Lock (2.0), it was working...

HI @Thorbijoern, I just tried with my Nuki Smart Lock 2.0. It was working without problems with Trigger 3.4.4. The error message comes from here: https://github.com/mwarning/trigger/blob/7b674bf6e680a5617ac488762a3673271b852a0c/app/src/main/java/app/trigger/nuki/NukiRequestHandler.java#L361 I suspect the logic...

Hi, you only need a debug build. The log out is already there and will be printed to logcat. So adb might be fine. Adnroid Studio makes it easier to...

Here you can set the `Active Build Variant` and to create a debug build:  You can use the logcat filter to only seee messages from the trigger process (I...

Half a minute is rather long. For my Nuki 2 it is a matter of 3 seconds. The log output does not contain anything sensitive (no keys).

I really wonder why the pairing takes that long, but maybe they changes something with the Nuki3.

Something like this should work for the status: `HTTP method`: `GET` `Status URL`: `http://192.168.0.1:8000/door.json` `Reply Pattern (locked)`: `"locked":true` `Reply Pattern (unlocked)`: `"locked":false` The `Open URL` could be something like `http://192.168.0.1:8000/door.json&action=open`....

Yes, this is a limitation, I will change it in the future. When I find a good way to make in configurable without an overload of options.