Actually, when I unlock using the entity, I can then relock or open (unlatch). But you are right that the UI offers no unlatch directly from locked state using the entity.
For me the unlatched state does not work in most of the cases, since the lock stays only about 1 second in that position this is too fast for my lock (version 2.0). Sometimes MQTT nuki/lock/state changes to unlatched, but most of the time it goes (or stays depending on the state before) on unlocked 
.
WOWWWā¦ it works fine!!!
I didnāt realize that the nuki.open service already existed
Many thanks and sorry for the carelessness @technyon @mundschenk-at
Now Iām using a Aqara Mini Switch WXKG11LM as a remote command instead of Fob
I think adding a sensor for the unlatched state doesnāt make too much sense, as mentioned this often isnāt detected. The bluetooth communication just is too slow, and a sensor that works only sometimes isnāt very useful.
to know the state of the door I use a Aqara door and windows sensor MCCGQ11LM
Yes but the door state is not the same as the lock state. The door can be closed, but the lock open (unlatched).
Yeah, thatās true. If the unlatched is not picked up most of the time, the sensor wonāt be useful.
After a few hours of good operation with the Home Assistant automations through ESP32 with your firmware it no longer works. Not even if I make a direct call to the service:
service: lock.lock
target:
entity_id: lock.nuki
If I turn the ESP32 off and on again ā¦ it works again.
This happens every day. Does it happen to you too? Do you have a solution?
Have a look at the āTroubleshootingā section of the documentation. There are several options to restart device on connection loss (I sometimes have the problem that the device is still on the network. but the MQTT connection stalls).
Besides the troubleshooting, I can recommend to get a W5500 module and connect the ESP via LAN cable. Most of the Wifi problems should be gone now, but a wired connections is still much more stable.
Thats awesome!!!
Thank you!
Iāve everything paired and the bridge receive the commands but nothing happens in the lock.
Nuki start pairing
Nuki paired
Lock action received: lock
Lock action received: unlock
lld_pdu_get_tx_flush_nb HCI packet count mismatch (1, 2)
lld_pdu_get_tx_flush_nb HCI packet count mismatch (0, 1)
Unable to setup HASS. Invalid config received.
Lock action received: unlock
Lock action received: unlatch>
EDIT: Iāve repaired the nuki and now it works
Thank you, I activated the restart option and now it works very well
Hello everyone, and thx a lot for the Tool, Jan!
Iām also trying to connect the program to my Nuki Opener. I allready own a bridge, but am not so happy with HA integration, high latency sending ringing etc. However, Iāve had extremely big problems getting the ESP stable into the WLAN. Sometimes it seems to connect to the Fritz Repeater in the basement instead of the Fritzbox 2 meters away. Tried two different Esp32, same symptom.
Now it worked after hours, but after trying for a long time Iām giving up. Because it crashes constantly when configuring the Nuki Part. Should actually pair with the opener, but it doesnāt. Probably another bug.
question about pairing. I only entered the Nuki PIN, no username password (I donāt know either). is that correct?
Regarding the WiFi, it might help to disable automatic channel selection on the router. On AVM devices this is enabled by default (only needed for 2.4 GHz, 5 GHz can stay on automatic). Again, getting a W5500 LAN module to connect via LAN instead of WiFi is very recommended.
I have unfortunately little control over the WiFi behavior, this is all Espressif code Iām only calling to enable WiFi.
For pairing, thereās no need to enter the PIN. Itās only needed after pairing to access restricted functionality, like the logs from the device. Make sure you are close to the opener when trying to pair. Do you already have a lock paired? Also, what exactly does ācrashā mean?
Has anybody experience with the Bluetooth signal strength of the opener? I get a constant mid-50ies with the lock, but the opener fluctuates wildly between -65 and -80 dB. Now granted, the opener is maybe half a meter further from the ESP, with the intercom in between (and the wall curving slightly away), so -65 dB would not shock me, but itās much worse overall (especially the large fluctuations).
Hi,
my nukihub is connected to mosqiutto. Also the nukihub interface shows it as connected.
But autodiscovery is not working for me. My discovery topic is standard āhomeassistantā and i have of course typed it under advanced setting.
Any advice?
Check for typos?
more than once ā¦
Also tried remove mosquitto and reinstall. Reboot the host (RP 4)
Here the mosquitto log (192.168.178.206 is nukihub):
2022-09-23 16:33:49: New connection from 192.168.178.206:60886 on port 1883.
2022-09-23 16:33:49: Client nukihub already connected, closing old connection.
2022-09-23 16:33:49: New client connected from 192.168.178.206:60886 as nukihub (p2, c1, k15, uāmqqtbrokerā).
Seems OK, isn t it?
Or maybe another way: How can i add the nuki manually? I have no experiences with mqqt and can not find good examples in the web.
Thereās something wrong with your autodiscovery setup, either on the Nukihub or on the HA side.