We are manufacturer for a visualization app for the KNX system. We have now created an interface for other systems.
Now, we have developed a NUKI plug-in for our app knXpresso based on the nuki bridge api. This plug-in allows to control the smart lock via KNX and to write the status of the smart lock on the KNX bus.
Now we have detected several problems:
If the user set one turn (360 degrees) in the Nuki App, it is still possible over the bridge to send the command id 2 (lock) two times. After that, the lock turns two times (720 degrees). In our opinion this should be stopped internally in the lock
What happens if the bluetooth reconnects? Does the bridge expect a response (lock state) after sending a command? Will the command be repeated?
When our app knXpresso starts, we set the command remove callback three times. We have to make sure that the callback id 0 is not used. Unfortunately, we have to do this three times because you can not specifically delete a callback (id). If you have ever set a different callback, this works fine.
This doesn’t work if you have just installed the nuki bridge app new from the playstore. Incidentally, knXpresso and nuki bridge are run on the same android device.
The response times of the actions are sometimes very different. The distance between the android device Samsung Galaxy Tab A and the smart lock is about 1 meter. The energy options on the android device are disabled.