Perfect for me 👌
-
is there anyone using Nuki dooropener
-
Works for me, too. Well done and great work @bertreb, thanks!
-
Hello again,
now the nuki reloaded version 0.9.20 is installed. I think the reason was the old version of node, updated to 10.14.Now I am able to install a device, but there no real connection.
I got messages in log files,I would send them to you but - I do not know how I can implement such a black window with the informations inside. Sorry, but I’m a newbie.
Ifyou can explain it I will send my log immediately. -
14:08:38.603 [pimatic-nuki-reloaded] debug: Error initializing callbackRequestError: connect ECONNREFUSED 192.168 .178.84:8080 14:08:44.433 [pimatic-nuki-reloaded] error: Error _requestUpdate: ECONNREFUSED 14:08:59.732 [pimatic-nuki-reloaded] debug: ActionHandler, action received: 2 14:09:04.723 [pimatic-nuki-reloaded] debug: Error locking 'hausture': { 14:09:04.723 [pimatic-nuki-reloaded] debug:> "name": "RequestError", 14:09:04.723 [pimatic-nuki-reloaded] debug:> "code": "ECONNREFUSED", 14:09:04.723 [pimatic-nuki-reloaded] debug:> "timings": { 14:09:04.723 [pimatic-nuki-reloaded] debug:> "start": 1612962543990, 14:09:04.723 [pimatic-nuki-reloaded] debug:> "socket": 1612962543991, 14:09:04.723 [pimatic-nuki-reloaded] debug:> "error": 1612962544717, 14:09:04.723 [pimatic-nuki-reloaded] debug:> "phases": { 14:09:04.723 [pimatic-nuki-reloaded] debug:> "wait": 1, 14:09:04.723 [pimatic-nuki-reloaded] debug:> "total": 727 14:09:04.723 [pimatic-nuki-reloaded] debug:> } 14:09:04.723 [pimatic-nuki-reloaded] debug:> } 14:09:04.723 [pimatic-nuki-reloaded] debug:>}
like this???
-
ok. I will try it. But these loginformation are actual.
-
yes, it is. but I will look for it, perhaps there is no connection
I check it. -
‘’‘14:41:00.357 [pimatic-nuki-reloaded] debug: ActionHandler, action received: 2
(node:32412) ExperimentalWarning: Readable[Symbol.asyncIterator] is an experimental feature. This feature could change at any time
14:41:13.751 [pimatic-nuki-reloaded] debug: ‘hausture’ locked ‘’’Sorry, i do not find the right letter.
But the plugin works now, the response for lock and unlock is correct. Just only the percentage of battery is wrong, show 0%.very good work of your side. Thanks.
-
14:41:00.357 [pimatic-nuki-reloaded] debug: ActionHandler, action >received: 2 (node:32412) ExperimentalWarning: Readable[Symbol.asyncIterator] is >an experimental feature. This feature could change at any time 14:41:13.751 [pimatic-nuki-reloaded] debug: 'hausture' locked
ok. I found a way.
But there are no more information in log. should there more? -
The batteryLevel is requested from the bridge on startup and after that every 6 hours (default polling time).
To check what’s happening in your situation.
Can you do a manual request (via browser) and see what the response is?
The manual request is (with your ip:port)http://192.168.178.84:8080/list?token=<your token>
Just cut and paste the response you see in the browser (in a blackbox)
This way I can check how the batteryLevel is formatted
-
‘’’[{“nukiId”:487xxxxxxxx"name":“home”,“lastKnownState”:{“state”:3,“stateName”:“unlocked”,“batteryCritical”:false,“timestamp”:“2021-02-10T14:58:06+01:00”}}]’’’
Here is the answer from the bridge, but there is no value for battery in.
I wrote from my mobile, so again I did not find the right signs for the blackbox. -
Thanks, the batteryLevel is missing in your Nuki system.
It could be a software version of the bridge and/or the lock or a functionality thats missing in the type you use.
Is your Nuki app telling you the battery level? -
May I ask you also to questions about pimatic in a docker container?
If yes, I will start a new chat. But Attention, I started with docker 3 days ago. -
Yes, I can see the battery status with 100%
-
Firmware is 2.9.10, no newer firmware available.