I translated the text using deep.com:
In the days of Nuki SmartLock 1.0 (which was not yet HomeKit compatible) I used the plugin from Benzman81.
Then I switched to Danalock because they had native HomeKit support. But I was never really satisfied with the Auto-Unlock.
So after the release of the Nuki SmartLock 2 I switched back to Nuki but integrated it via native HomeKit.
Then came the nello era and I started writing plugins for homebridge myself. The nello itself was very cool, but I was always bothered by the fact that notifications had to be routed in a complicated way via a webhook relay server.
When Nuki leaked the first information about the opener, my fingers itched and I wrote a plugin for the bridge API to control the opener for the launch (for now locally on my PC). As you might know nello went bankrupt and the server communication has become unreliable or even impossible. So I decided to switch to Nuki on the “productive system” and check the plugin into GitHub. Since it’s not complicated, I added the SmartLock support. Personally I still use native HomeKit for the SmartLock, Homebridge only for the opener.
I don’t think there is much difference in functionality between the plugins. The only difference in the architecture of the plugin is that in the plugin of Benzman81 the callbacks of actions are only called after successful completion, my plugin uses the Fire-and-Forget approach. You will notice this, for example, when you press the lock tile in the Apple Home app to close/open. With Benzman81 you can see a loading spinner during the (open)-close action, with my plugin the status of the tile is changed directly. This is true, isn’t it Benzman81?
Historically, my plugin was practically the first one for the Nuki. When the opener came, lukas.roegner created a plugin with opener and and closed and I added the opener. So both want the same thing and differ in the details. Besides the difference mentioned by lukas.roegner, that I wait for the answer of an action before I give feedback to Home, there is another difference in error handling. I am a bit more restrictive and repeat actions only for certain errors and not for all kinds of errors. I also don’t implement features that I think Nuki should implement by itself or that are security leaks. If you have two locks, you can also assign a priority and decide which lock should be unlocked first. All in all, both plugins have their right to exist and their own advantages and disadvantages, I think.
Translated with www.DeepL.com/Translator (free version)