Hi there,
has anybody one of the actual Smart Lock Ultra, Pro or Go running / tested with Nuki Binding?
The Nuki Binding is design to work with the Nuki bridges, what was necessary in the past to control one or multiple smart lock via WiFi.
The actual productline doesn’t need that bridge anymore, they provide builtin WiFi & Matter, as also Bluetooth. So, I hesitate a little that binding’s design still fits for that lineup …
Regards
Frank
I have integrated my Nuki Ultra with Keypad 2 via MQTT without a bridge. Works perfectly well.
Thanks for the feedback. I don’t run any device with MQTT actually, so I won’t start now for just that lock.
I might rather consider to integrated with Matter, due available AppleTV(s). But need to understand that concept, foremost is that bi-directional Matter bridge <=> openHAB …
Have ordered a Nuki Smart Lock Pro since we have already a secure cylinder, able still to open the door manually with already existing keys. With the Ultra I would need to purchase some of those special keys additionally …
I was contemplating as well which one to buy. But the ultra is by far the prettiest device, and changing the cylinder was pretty easy. And with regards to the key it does not really matter that it’s a new one, as I have not used a key again since I installed the ultra, as it just works.
For matter devices, you may use the matter binding without the Nuki bridge.
If the Lock supports matter over WiFi, no need for a border router such as an Apple TV.
If the Lock requires matter over Thread, then a border router (i.e. Apple TV) is required.
Matter really is a protocol over ipv6. A border router is a device that routes ipv6 to a wireless Thread mesh network. If your lock supports Matter over Thread, then your lock’s batteries will last MUCH longer than if your lock is connected via WiFi.
I have an Apple 4k with which I’m happy… BUT I have no Matter thread devices, I have several Matter devices connected to my OH via Wifi, none of them are battery powered.
Yes, exactly I was thinking about that, rather then MQTT. Down the line it seems to be kind of the future in home automation.
Thanks for brief introduction. That lock’s accumulator does run up to month’s even with WiFi enabled, according to what I read from other users and is capable of that:
Need to find out if it can do Matter over WiFi also, or just Thread. And foremost I need to find out if the lock on Thread without WiFi is still reachable from remote, so basically cloud access.
But Thread sounds sexy to me, foremost if the fully charged accumulator might have longer reach just running on Thread. I actually use my AppleTV 4k as Home(kit) central device, proposing many device from OH into Apple Home.
So, is it possible to use old fashioned Home(kit) integration with Matter/Thread parallel? When I book that lock as first Thread device into AppleTV 4k central device, how does it get back into OH? With what capabilities?
And is it advisable to exchange Homekit binding with Matter binding in OH? Can I still propose none Matter devices into Apple Home like with Homekit binding?
I know many questions, sorry …
Device got delivered, installation was speedy, just 10min, ok, was kind of prepared.
Activated just WiFi on first step, to test functionality for me and my wife. Awesome smart lock, speed and power, wow. Just a little noisy, what has some advantage, no secure unlocking 
… we get used to.
On second step I activated Matter into Apple Home. That does disable lock’s WiFi connection immediately. So, either classic WiFi or “Matter over Thread” … nothing in between. Using AppleTV as Thread border router, the lock keeps remote (cloud) accessibility, very cool.
But that “Matter over Thread” integration of the Nuki Smart Lock also disabled all my OH proposed devices using Homekit binding into Apple Home. I just see all devices inactive, no connection, only active device is the Nuki Smart Lock in the defined room … ouch 
short answer, yes it can for both Apple Home and OH. Long answer is very long.
ok… complex question
short answer for Matter devices. No need. Both Apple Home and OH can directly communicate with the device and both receive updates when the other changes the state of the device. The thing to plan is which matter controller you want to connect to first. That affects how you connect the second matter controller. After you connect the second, the second controller does not need the first controller for anything.
short answer for OH only devices
yes you can, but the Matter binding offers equivalent functionality (Matter Bridge). You can gradually migrate devices from the HomeKit binding to the Matter binding. Both HomeKit and Matter bindings use OH metadata in the same way. I’m VERY SLOWLY migrating as my HomeKit binding setup is working perfectly fine right now.
non-answer for HomeKit only devices, I have not tried. This applies to HomeKit supported devices that ARE NOT Matter devices. The Matter binding documentation suggests that the Matter specification DOES allow this and the OH Matter binding supports this.
I no longer have any HomeKit only devices. I used to have HomeKit only Schlage Sense Door locks. When I moved about 4 years ago I bought Yale Assure SL locks with the Zigbee Smart Module because I wanted a lock natively supported in OH. My plan was to switch to the Matter Smart Module when it became available. 
When the Matter Smart Module was released, it was only sold in a bundle with a new lock.
No HomeKit binding needed. You generate a new code in the Apple Home app and use that code to bind OH to the lock.
I don’t get your point?
After I added the Nuki lock to Apple Home with “Matter over Thread”, all my Homekit devices from OH are shown disabled in Apple Home … ?
So, looks like I need to do a fast migration Homekit to Matter … ?
I do not have any “Matter over Thread” devices. Only Matter over WiFi devices.
The Matter devices I have are directly bound to both Apple Home and OH. I have no issues with my existing OH HomeKit binding devices showing up in Apple home.
Provisioning a Thread device on the Apple TV breaking your OH HomeKit config seems odd to me. Provisioning a Thread device on the Apple TV technically has nothing to do with either HomeKit or Thread. Thread is a transport that Matter runs on top of. How the provisioning of a Thread device on the Apple TV, which you are required to do here, would effect your existing OH HomeKit config would require some inspection of the HomeKit binding debug logs
TL:DR
Use Ethernet from your home router to your Apple TV for fewer POTENTIAL HomeKit issues with Thread.
If you notice intermittent HomeKit “bridge not responding” issues after adding Thread devices, restart both the Apple TV and OpenHAB — it re-announces mDNS and re-establishes the HomeKit session.
My Apple TV is Ethernet connected
Yepp, came to same idea on first step. Rebooted one after the other to identify what finally helped. It was the openHABian reboot. The openHAB provided Homekit devices are back online in Apple Home, so no need to rush into Matter migration.
Nevertheless Matter binding is also enabled meanwhile, but doesn’t start telling:
[INFO ] [.matter.internal.bridge.MatterBridge] - No devices found to register with bridge, not starting bridge
[INFO ] [.matter.internal.bridge.MatterBridge] - Matter Bridge State: Stopped : No items found with matter metadata
Started to read documentation, what I need to provide minimal for bi-directional Matter operations per .things file, to get it started properly.
On item level then, for non Matter devices it looks overall similar to Homekit integration.
Looks like what I might need has just recently merged into Matter binding:
Apple Home itself does just know bolt & unbolt, but not unlatching, what I see here …
Ok, looks like I have it running somehow, albeit OpenHAB GUI still doesn’t show any QR code in “Settings / Add-on configuration / Matter Bridge Configuration”.
First created a things file for the bridge /etc/openhab/things/controller_matter.things, using defaults from examples:
Thing matter:controller:main "openHAB Matter" @ "FlurOG" [ nodeId="1" ]
Then create a pairing code in Apple Home for the Nuki Smart Lock item, hold press tile, settings, start pairing, note down the code. In openHAB Settings / Things / “openHAB Matter” / Pair a Matter device. Enter above noted code and Execute Action.
After that there’s a device in inbox, select and “Copy Thing File Definition”. Create a file /etc/openhab/things/matter.thingsto paste into:
Thing matter:node:main:8699603707079210385 "Nuki Smart Lock Pro (Gen. 5)" (matter:controller:main) @ "Windfang" [nodeId="8699603707079210385"]
The thing gets online:
But doesn’t show any channels … 
… so, no items to create from here …
Another finding is how openHAB shows up in Apple Home:
“Matter Test” … ?
Ok, played a little forth and back, disabled things files and “matter” from addon.cfg … added stuff thru gui, eradicated that and enabled everything from files again. Then I could see channels all over sudden … maybe I have been too impatient …
So, I know now how to get native Thread devices from Apple Home into openHAB.
For the other way around I guess, I need to pair “openHAB Matter” to Apple Home, similar to Homekit binding, right?
in order to get a cert, the developer or company needs to submit to the Matter standards body for certification ($$$)
So OH is using a Test certificate
Yes… kind of.
READ THE DOCS of the Matter binding, maybe even the Github ReadMe! There you can find all the gory details
Take your time, your existing HomeKit binding still works 
Well, does work 
Used one item of a dual channel EnOcean actuator to modify integration meta data from homekit=“Lighting” to matter=“OnOffLight”. Matter Bridge came up properly directly, showing QR code, manual key etc.
So, one channel is mapped with Homekit, the other channel of same actuator mapped thru Matter 
Just binding with Apple Home worked after another OH restart:
