New openHAB2 Binding for Nuki Smart Locks

Add-ons Bindings
,
163

I don’t get the exact use case, that “unlatching == 7” should trigger the light, but this is not reported in the callback - by design from Nuki (see here: HTTP API callback and the unlatched state). So you have to work around that.

You can only combine it Nuki-only with LockStates which are permanent, as those are reported by the Nuki API. You could of course use other triggers like geofencing/motion detectors/… to trigger your light in combination with Nuki-LockStates - but not with “non-permanent” LockStates…

164

another way to goal would be to trigger a rule by an successful ring-to-open by the opener, which is also available. but also there it seems that there is no way to get the temporary state

165

Hey there! Do you guys know if it will be possible to use the Nuki 3.0 without a bridge (using either BT or Wifi from the Pro variant)?

166

I don’t see all the necessary information on nuki website right now, but my wild guess is:

  1. Nuki 3.0 without bridge and only Bluetooth won’t be accessible (as is right now - you definitely need a bridge)
  2. Nuki 3.0 Pro is basically a Nuki with a bridge in one, meaning you define a IP-address and then you can use the API like a Nuki with a bridge

see:

167

Thanks for your input. So basically it doesn’t make a difference price-wise to buy the regular variant + bridge or the Pro variant the way I see it, right?

168

Look here - Nuki 3.0 Pro - Questions - Nuki Developers . Seems like the wifi in pro version is for cloud connection only and won’t (at least at the beginning) provide local http api, so you would still need bridge.

1 Like
169

wow! ok… So, the page I linked was lying! :wink:

grafik
grafik717×326 13.7 KB

so, it is more than misleading, but anyways…

170

Can you please share your solution as I’ve got the same Problem? Thanks

171

The rules are in Python, would that help you ?

172

I have the new Nuki lock v3.0. That one has a new device ID, IDs 3 and 4. Thus it will not work properly with the current binding. But the binding just has to recognize these two new IDs, very easy to add.
Could someone please look into this?

173

I’ll look into it. In the meantime you could try adding the lock manually using its IP address instead of discovery, that should theoretically work fine (although /lock and /lockAction expect deviceType as a parameter, not sure what happens if it does not match).

174

I’ve created updated binding version with smart door/smartlock 3 support, you can get it here - https://github.com/janvyb/files/raw/main/org.openhab.binding.nuki-3.3.0-SNAPSHOT.jar. Uninstall current nuki binding and drop this into addos folder. I can’t test this properly myself since I don’t own smartlock 3.0, so let me know if it works and I’ll create new PR later.

1 Like
175

Will do, but takes a few days. Probably by end of next week.

176

@m0rgoth Works fine! Ready to go with Nuki v3.0

1 Like
177

Great, I’ve created new PR to add the smartlock 3.0 support - [nuki] Support for SmartLock 3.0 and SmartDoor by janvyb · Pull Request #12005 · openhab/openhab-addons · GitHub. There was also a small change in values of smartlockDoorState channel (just some new values for the new external sensor) so I updated the documentation.

178

Thanks so much!

179

Does This only work with the pro version?

180

No, to use nuki with openhab you need Nuki Bridge (which works with all Nuki versions). As far as I know the pro version does not provide local HTTP API like the bridge does.

181

So you need the simple Nuki 3.0 (149 €) and the Bridge (99 €) Right?

Because I want to order the nuki

182

Yep, that one, basically bridge and any nuki version.