Yes, but normally I am using Chrome only.
-
is there anyone using Nuki dooropener
-
I did a test on a rpi 3b with node 10.22.
Clean install of nuki-reloaded 0.9.25 and added 2 devices (i’m using a nuki emulator)
It works and could add the extra fields. This doesn’t solve your problem, but i can’t reproduce the issue.Is your Nuki bridge reachable or correct configured?
The device info in your post seems to be the default values -
I reinstalled the plugin but is still the same. Further when I operate it, I haven’t since the update I get this error:
Really strange!No debug gets written. I will downgrade to see what will happen. My script based integration still works fine. Even the JSON response is available as before, means the bridge is still available.
-
With that error the library ‘nuki-bridge-api’ seems not to be installed.
Can you try to delete node_modules in pimatic-nuki-reloaded and run the command npm install in THE SAME directory -
Will try it. The downgrade was successful :D
Will try a new update…
-
Back on 0.9.25 and run into the same as before.
Will see what I can do here…
-
npm: 6.9.0
node: 10.16.3 -
Really have no idea. Just some lines in has changed in following files
Only the package.json has huge amount of changes. But that should be okay.
What about the other users, does it work for you?
-
can you use the original package.json from github.
And if there a package-lock.json in the directory, please delete that also
And delete directory .js in pimatic-nuki-reloaded.
This is to cleanup, on start these files/directory will be created/compiled -
No luck. Would be nice when other user could check it. At the moment it seems to be local problem. As long as my script base nuki solution works all is fine, otherwise my wife would kill me…
-
I installed pimatic on my docker pi, using treban/pimatic docker (the multi-architecture version). After installing pimatic-nuki-reloaded 0.9.25 its still working.
Besides a complete new raspberry image, this is the cleanest (and easiest) way to test. -
@bertreb said in is there anyone using Nuki dooropener:
Are you use docker?
Nope. Pimatic ist installed on Ubuntu Server.
As I said. With 0.9.24 everything works fine. The differences to 25 are not that much. I will give it a try tomorrow once more. -
A few days later …
Actual my nuki does not work, dont know why.
The state is:
Pimatic:[pimatic] Starting pimatic version 0.9.54
Nuki : Loading plugin: “pimatic-nuki-reloaded” (0.9.25)
Raspbian:
Linux pimatic-test 5.10.11-v7+ #1399 SMP Thu Jan 28 12:06:05 GMT 2021 armv7l GNU/LinuxPlain system, no docker installed.
npm: :
pi@pimatic-test:~$ npm -v
6.14.6
pi@pimatic-test:~$ node -v
v10.22.1Following messages in logfile:
[pimatic-nuki-reloaded] Start constructor Nuki device
15:12:52.955
[pimatic] New device “Haustüre”…15:13:03.054 [pimatic-nuki-reloaded]> { 15:13:03.054 [pimatic-nuki-reloaded]> "id": 0, 15:13:03.054 [pimatic-nuki-reloaded]> "url": "http://192.168.178.104:51989/nuki-api-bridge" 15:13:03.054 [pimatic-nuki-reloaded]> }, 15:13:03.054 [pimatic-nuki-reloaded]> { 15:13:03.054 [pimatic-nuki-reloaded]> "id": 1, 15:13:03.054 [pimatic-nuki-reloaded]> "url": "http://192.168.178.100:12321/nuki-api-bridge" 15:13:03.054 [pimatic-nuki-reloaded]> } 15:13:03.054 [pimatic-nuki-reloaded]>] 15:13:03.063 [pimatic-nuki-reloaded] Adding callback 15:13:03.336 [pimatic-nuki-reloaded] Info initializing callback: HTTPError: Response code 400 (Bad Request )
Maybe a little bit helpful.
As I remember with the version 0.9.21 I got answer from my nuki.
Actual, if I trie to lock the “Haustüre” I got
100: Cannot read property ‘lockAction’ of undefinedPerhaps I should also go back to the older version?
-
Everytime I trie to change the status of nuki I get the same message:
[pimatic-nuki-reloaded] ActionHandler, action received: 2 15:14:24.165 [pimatic] Cannot read property 'lockAction' of undefined 15:14:30.700 [pimatic-nuki-reloaded] ActionHandler, action received: 2 15:14:30.740 [pimatic] Cannot read property 'lockAction' of undefined
-
The log suggests that you have 2 different pimatics running (see url’s)
There should be 1 callback url.
This info comes from the bridge, you could delete that on the bridge.The error 'Cannot read property ‘lockAction’, can be the result of the plugin not being installed the right way.
can you uninstall the plugin and install version 0.9.26?