I have tried an Opener also in use with the Nuki Binding. No success until yet. Maybe the Owner of the Binding can extend this. If help is needed or debugging help I will try to support.
I also very interested that the opener will be integrated in a short while. Not sure if possible to create a nuki lock thing and modify the settings in the json database. But for my opinion it doesn’ work because the difference it the device type (opener = 2) smartlock = 0, the rest lock very simular.
do you have any experience in using the nuki api? If it’s just this small change, I could work something out. However, I guess the commands are different too, right?
I have read the docs but have nothing coded with the API yet.
And I have tried it via the link in the browser and it is working if I add the “deviceType=2”.
Would be awesome if you can add Nuki Opener support.
I add only in a item file the objects which I needed for the opener - all other are defind by the NUKI Binding settings. You can with this syntax all api request for devicetype=2.
ttttt = NUKI Tocken
xxx.yyy = part of the IP of the openhab platform
NUKIID = Nuki ID
Hopem this helps - it’s not a integrated solution but it works based on it.
But you don’t see the actual state of the Nuki Opener for “Ring to open” or “Dauermodus”?
Anyway a great workaround until someone can add the native support to the binding.
What isn’t possible : to get the ring action - here I use another way : HM-Sen-DB-PCB
It’s a little bit double doing but until opener doesn’t support it (I don’t know why it isn’t) I use this and it works really good. If someone rings Alexa says that there is someone who rings Nice gimmick.
Thanks for this! I fiddled around a little and I think the open command works even better this way: Switch Housedoor_Lock "Türöffner betätigen" <frontdoor> (gNuki) { http=">[ON:GET:http://192.168.17x.yyy:8080/lockaction?token=tttttt&nukiid=NUKIID&deviceType=2&action=3]", autoupdate="false" }
(action=0 seems to be invalid)
And everyones who’s also searching for the Nuki ID… These are not the numbers which the base is handing out in the nukiId field… It’s the last part in the name-property of the opener (name: Nuki_Opener_THISHERE). You get these by calling your nuki base with http://192.168.17x.yyy:8080/info?token=tttttt