is there anyone using Nuki dooropener
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?
Installed Version 09.26
Now its working again. Great job, thank you again.
Pimatic would be dad if there are not guys like you.
It’s strange
[pimatic-nuki-reloaded] Current callbacks: [
16:37:16.941 [pimatic-nuki-reloaded]> {
16:37:16.941 [pimatic-nuki-reloaded]> "id": 0,
16:37:16.941 [pimatic-nuki-reloaded]> "url": "http://192.168.178.104:51989/nuki-api-bridge"
16:37:16.941 [pimatic-nuki-reloaded]> },
16:37:16.941 [pimatic-nuki-reloaded]> {
16:37:16.941 [pimatic-nuki-reloaded]> "id": 1,
16:37:16.941 [pimatic-nuki-reloaded]> "url": "http://192.168.178.100:12321/nuki-api-bridge"
16:37:16.941 [pimatic-nuki-reloaded]> }
16:37:16.941 [pimatic-nuki-reloaded]>]
I do not have any device with 192.168.178.104.
Have to look for it
That could be an old ip address, if your pimatic system is using/getting dynamic ip addresses.
The Nuki bridge is saving max 3 different callback ip’s
some weeks ago I had a raspi with iobroker running. This was the ip 104. But actual there is no device on it.
You can remove the … 104 callback via the Nuki app
what exact do I have to do?
in a browser http://<ip nuki bridge>:<port nuki bridge>/callback/remove?id=0&token=<your token>
This remove the api callback 0
@ortin said in is there anyone using Nuki dooropener:
I found the update to 0.9.25. In my case with this version the states of
StateNameanddoorsensorStateNameare not shown anymore in my English test environment?
With 0.9.26 my problem is gone. Works now. Thanks for the update. Can you say what was wrong?
I guest changing the engine in package.json to the most used versions, did the trick, but still i don’t know why (yet:))
