Closed ScIT-Raphael closed 1 month ago
Most chances are that the esp's BT is too far from the lock. Did you move the esp after pairing?
No, location is the same - around 2.5 meters away from nuki, just pulled it to 1 meter distance - no change.
Please post the full log from startup and I'll have a look.
Same here. [08:33:14][E][nukilock.lock:180]: lockAction failed: 99 [08:33:14][D][binary_sensor:036]: 'Nuki Connected': Sending state OFF [08:33:14][D][lock:055]: 'Nuki Lock': Sending state UNKNOWN [08:33:14][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:15][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:15][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:16][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:16][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:17][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:17][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:18][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:18][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:19][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:19][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:20][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:20][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:21][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:21][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:22][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:22][E][nukilock.lock:075]: requestKeyTurnerState failed: 99 [08:33:22][I][nukilock.lock:025]: event notified 0 [08:33:24][I][nukilock.lock:063]: Bat state: 0xc8, Bat crit: 0, Bat perc:100 lock state: 3 6:33:26
Often it works but sometimes it gives me this error too.
Can you test the sample from the base library NukiBleEsp32?
Sorry for the delay, have changed to the suggested library but havent got any change. Here is the full log:
INFO Reading configuration /config/esphome/node-nuki.yaml...
WARNING The selected Arduino framework version is not the recommended one. If there are connectivity or build issues please remove the manual version.
WARNING The selected Arduino framework version is not the recommended one. If there are connectivity or build issues please remove the manual version.
INFO Starting log output from node-nuki.local using esphome API
INFO Successfully connected to node-nuki.local
[08:21:51][I][app:102]: ESPHome version 2023.3.2 compiled on Mar 28 2023, 08:19:41
[08:21:51][C][wifi:504]: WiFi:
[08:21:51][C][wifi:362]: Local MAC: [redacted]
[08:21:51][C][wifi:363]: SSID: [redacted]
[08:21:51][C][wifi:364]: IP Address: [redacted]
[08:21:51][C][wifi:366]: BSSID: [redacted]
[08:21:51][C][wifi:367]: Hostname: 'node-nuki'
[08:21:51][C][wifi:369]: Signal strength: -69 dB ▂▄▆█
[08:21:51][C][wifi:373]: Channel: 6
[08:21:51][C][wifi:374]: Subnet: 255.255.254.0
[08:21:51][C][wifi:375]: Gateway: [redacted]
[08:21:51][C][wifi:376]: DNS1: [redacted]
[08:21:51][C][wifi:377]: DNS2: 0.0.0.0
[08:21:51][C][logger:293]: Logger:
[08:21:51][C][logger:294]: Level: DEBUG
[08:21:51][C][logger:295]: Log Baud Rate: 115200
[08:21:51][C][logger:296]: Hardware UART: UART0
[08:21:51][C][nukilock.lock:193]: nukilock.lockNuki Lock 'Nuki Lock'
[08:21:51][C][nukilock.lock:194]: nukilock.lockIs Connected 'Nuki Connected'
[08:21:51][C][nukilock.lock:194]: nukilock.lock Device Class: 'connectivity'
[08:21:51][C][nukilock.lock:195]: nukilock.lockIs Paired 'Nuki Paired'
[08:21:51][C][nukilock.lock:195]: nukilock.lock Device Class: 'connectivity'
[08:21:51][C][nukilock.lock:196]: nukilock.lockBattery Critical 'Nuki Battery Critical'
[08:21:51][C][nukilock.lock:196]: nukilock.lock Device Class: 'battery'
[08:21:51][C][nukilock.lock:197]: nukilock.lockDoor Sensor 'Nuki Door Sensor'
[08:21:51][C][nukilock.lock:197]: nukilock.lock Device Class: 'door'
[08:21:51][C][nukilock.lock:198]: nukilock.lockDoor Sensor State 'Nuki Door Sensor State'
[08:21:51][C][nukilock.lock:199]: nukilock.lockBattery Level 'Nuki Battery Level'
[08:21:51][C][nukilock.lock:199]: nukilock.lock Device Class: 'battery'
[08:21:51][C][nukilock.lock:199]: nukilock.lock State Class: ''
[08:21:51][C][nukilock.lock:199]: nukilock.lock Unit of Measurement: '%'
[08:21:51][C][nukilock.lock:199]: nukilock.lock Accuracy Decimals: 0
[08:21:51][C][captive_portal:088]: Captive Portal:
[08:21:53][C][mdns:108]: mDNS:
[08:21:53][C][mdns:109]: Hostname: node-nuki
[08:23:16][E][nukilock.lock:180]: lockAction failed: 99
[08:23:16][D][binary_sensor:036]: 'Nuki Connected': Sending state OFF
[08:23:16][D][lock:055]: 'Nuki Lock': Sending state UNKNOWN
[08:23:16][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:17][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:17][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:18][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:18][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:19][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:19][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:20][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:20][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:21][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:21][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[08:23:22][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
... looping
@ScIT-Raphael, do you mean that it does not work with NukiBleEsp32 sample? If so, I suggest to open the issue there as well. This component is built on top of NukiBleEsp32.
I have exactly the same behaviour. I did even repair sucessfully, it did work again for a few hours and then I have the error again. Strang thing is that it still reports connected... logs_esp-display_logs.txt
also having the same issue after power-off/-on the ESP. Unpair + Pair again seems to fix it for now. I guess the keys should be stored on ESP flash and survive? Maybe something else is changing after power-off/-on so the keys don't work anymore?
after some time, 1-2 hours getting again the same problem when trying to lock the nuki.
[10:33:35][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[10:33:35][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[10:33:36][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[10:33:36][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[10:33:37][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[10:33:37][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
[10:33:38][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
Hi, I'm having the same issue. it's happening right from the start after I pair the devices. few more things I have noticed:
thanks.
My device worked flawlessly for several months, all of a sudden it stopped working. The only interesting part in the logs is
[00:46:01][W][component:204]: Component nuki_lock.lock took a long time for an operation (0.05 s).
[00:46:01][W][component:205]: Components should block for at most 20-30ms.
[00:46:01][E][nukilock.lock:075]: requestKeyTurnerState failed: 99
Things I tried without success:
I have the same problem and additionally a problem with [E][nukilock.lock:191]: lockAction failed: 2
and [E][nukilock.lock:191]: lockAction failed: 3
errors.
Here's a full log of me just trying to open and close the lock. Reliability is below 33%.
So I actually ditched this component and went for the nuki_hub as in this current state your esphome component is production ready for me. No problems with nuki_hub at all so far.
From what I know about esphome the problem might very much be related to these lines:
[12:52:54][W][component:204]: Component api took a long time for an operation (3.06 s).
[12:52:54][W][component:205]: Components should block for at most 20-30ms.
@uriyacovy Do you have any idea what could cause our problems? Your solution is wonderful when it works and it would be awesome if there was a fix for our problems.
Same problem here...
Hi, Though I tried to find some time to support this module, I'm unable to invest the required attention. Hopefully some community member will take the lead. Sorry.
As soon as I want to lock the nuki over home assistant, "Nuki Connected" drops to "Disconnected" and the logs show the following errors:
Do you maybe have an idea how to solve?