is there anyone using Nuki dooropener

---

Hello to everyone,
since some weeks I use a nuki dooropener in my house. last week I mentioned thar there is a plugin in pimatic for nuki. immediate installed, but…
My nuki id is not numeric. It looks like hexadecimal, it starts with 1D… but the plugin expected a numeric value.
I find no update for the plugin. Is there anaybody with a good idea?

Thanks a lot
Manfred

Convert the hexadecimal to a decimal number.
After discovery change the nukiId to the converted value

@bertreb
thanks a lot, it works.
This plugin is only able to show the status? It is not possible to open or close the door in pimatic?

The device has no rules actions. You can use the state of the contact in rules condition part.
To add an open/close option the Nuki Api needs to support that and the plugin needs some extra code.
Did you already ask the builder of the plugin @mwittig ?

If you want I can make an update called pimatic-nuki-reloaded.
Let me know if you are interested.

Hi betreb,
you and i know that there is no real urgent reason to havd these features available in pimatic. The nuki app is on the same system and normaly I use the nuki ap. But I like to have all the switches etc. in one app.

So if you able to create a expanded version I think it will really nicefull.

Nevertheless, I am very glad that there is furthermore such a good and competent support for pimatic available.

Best regards Manfred

Hi, creating an expanded Nuki version is not a big project. Its a variation on plugins I already made. Yes its not urgent but always fun to make.
I’m not a Nuki user, so it would help me if you can give the requirements for the info your want to see in the gui and the actions you want to execute via rules.
Or you start with my interpretation and we update it if needed

I realized it with a shell script. It works fine, but nice to hear that you like to create a plugin

I also have a nuki. I’ve stopped using the pimatic plugin as it drained the battery of my nuki. I suppose that was caused by the continuous query of the lock state.

If @bertreb is implementing a new plugin version I will sure do some testing for that. Perhaps https://github.com/Mik13/nuki-bridge-api is also helpful to built on. As it supports events for status changes which could prevent to battery drain problem.

If you want to be a tester, you can install pimatic-nuki-reloaded version 0.9.4.
This version isn’t using polling and has actions.

That plugin was finished very fast

Setup work, discovery finds my nuki. When I try to save the device, I receive the following error:
Client error: Uncaught TypeError: Cannot read property ‘type’ of null

Thanks for testing, you are the first (I couldn’t because I don’t own a Nuki)

Is there more debug info?

No more debug output. Seems to come from the mobile-frontend, as the pimatic log shows:

I will add debug info in the next version

Some more test results with v0.9.8

1. The displayed status “locked/not locked” are not correct.
2. When I trigger the switch when the shown status is locked, my door opens . Status says unlocked then, which is now correct
3. Now status is unlocked, trigger again, nothing happens

Next test run, Nuki is locked on startup of pimatic
Log output from start up:

07:14:44.370 [pimatic-nuki-reloaded] Start constructor Nuki device
07:14:44.374 [pimatic-nuki-reloaded] Attribute battery and lock added
07:14:44.378 [pimatic-nuki-reloaded] Attributes state en lock initialized
07:14:44.382 [pimatic-nuki-reloaded] @nuki created
07:14:44.385 [pimatic-nuki-reloaded] Battery handler added
07:14:44.391 [pimatic-nuki-reloaded] requesting state of the lock
07:14:44.396 [pimatic-nuki-reloaded] Requesting update
07:14:44.400 [pimatic-nuki-reloaded] constructor finished
07:14:44.406 [pimatic] New device "Haustür"...
07:14:45.001 [pimatic-mobile-frontend] packing static assets
07:14:45.677 [pimatic-mobile-frontend] packing static assets finished
07:14:45.703 [pimatic-mobile-frontend] rendering html
07:14:55.448 [pimatic-mobile-frontend] rendering html finished
07:14:55.555 [pimatic] Listening for HTTP-request on port 10080...
07:14:57.237 [pimatic-nuki-reloaded] Error: { success: false }
07:14:58.282 [pimatic-nuki-reloaded] nuki.on created
07:14:58.641 [pimatic-nuki-reloaded] nuki.on callback url: http://localhost:12321/nuki-api-bridge
07:14:58.649 [pimatic-nuki-reloaded] nuki.on callback url: http://localhost:12321/nuki-api-bridge

1. The gui switch is “off”, no status shown
2. Trigger switch, nuki is unlocked. Status shows “locked” and switch is on.
3. Trigger again, door is opened , status shows “unlocked”, switch is off
   Log output:

07:18:08.134 [pimatic-nuki-reloaded] ActionHandler, action received: 2
07:18:08.837 [pimatic-nuki-reloaded] Nuki locked
07:19:02.079 [pimatic-nuki-reloaded] ActionHandler, action received: 1
07:19:09.015 [pimatic-nuki-reloaded] Nuki unlocked

Nice early morning debug.
It looks requesting the lockState failed. This is a simple function that results in doing a http request on the api.
Important are the right IP address, port number and key of the bridge, but that will be ok. It only possibility to debug the call to the Nuki bridge, when you add a line in a file of the used library.
Is that something you can do?

In file pimatic-app/node_modules/pimatic-nuki-reloaded/node_modules/nuki-bridge-api/lib/nuki.js , add in following on line 61

        console.log("Request: "+url);

After that you can see what’s the request looks like and even repeat/test that request in a browser

Hello together,
sorry that I’m late, but I had a lot of other things to do.

So today I installed the nuki reloaded 0.9.14.
I disabled the old nuki 0.9.1 But now I can’t find any nuki device when I am going to install it. I configured the reloaded plugin the same as the old one. I tried also a device recovery, no success.
Is there any other new thing to configure or do I need a special version of node (using 8.17). pimatic version 0.9.54
So if it will work on my system I would do also some testing. But actual nothing will work. (Except the 0.9.1 version)
Do you have any Idea?

Hi, Is the plugin loaded and active and did you delete or reused the ‘old’ Nuki devices?

Yes, loaded, activated and configured like so old one. The old one is just deactivated, should be enough? the device is deleted.

Sounds ok. If you switched the debug on, can you post the debug info?