I too have the impression that it takes longer with mqtt now (but not as long as 8 seconds though). It seems to me that was quicker with older versions of nuki hub.
Have you looked at the logs (serial or MQTT)? Your Nuki Hub might be too far away from the lock, requiring multiple attempts for the action to get through.
I have a BT signal of about 61 dBm. How do I read the logs from the Nuki Hub or ESP32?
Enable MQTT logging and a sensor in HA for the topic.
I activated the MQTT logging. But where can I find this sensor? Sorry, I’m brand new to Mqtt
Add something like this to your configuration:
mqtt:
sensor:
- name: "Nuki Hub Log"
unique_id: '<some unique ID>'
state_topic: "nuki/maintenance/log"
device:
identifiers: nuki_<your lock's ID - lowercase hexadecimal>
entity_category: diagnostic
Thanks! I have installed form scratch version 8.19 and now works as a charm.
It would be great if the publish interval of the topic presence/devices could be configured. I have opened an issue on Github.
1 Like
Is it normal for Opener to show an “open” in the app every 30 minutes? Does that have to do with Nuki Hub? Never had that before. Ring detection also says recognized.
Looks like a malfunction. You can try removing the batteries for a few seconds to reset the Opener.
I reset it to factory settings. Let’s see what happens now.
On another question: Can I create an automation to activate RTO when I enter a certain area? Unfortunately I can’t find a way.
Hello and thank you for this great work. After first using unsuitable ESP32, I can now get the Bluetooth connection and the connection to the Mqtt. But unfortunately I’m probably too stupid to integrate the whole thing into HA. I configured the following according to the pictures:
However, I can’t see the entities in HA. Despite hours of testing, its empty
Anyone have an idea? It is actually planned to use the connection of the Nuki via the HA platform in Homey. The HA Top is suitable for this… But unfortunately I fail here…
@Kai102
There must be something wrong with the discovery of the lock. Normally you should have a state in MQTT Explorer. Mine looks like this:
According to this, NUKIhub should show the state too:
Second thing, for autodiscovery the topic normally is homeassistant. It should be set here in NUKIhub:
And in my HA it looks like this:
If its working right in NUKIhub you should have 2 topics in MQTT, nuki for the state of the lock etc and homeassistant for the autodiscovery. But at first you should have to check why the lock state isn’t shown.
@streetjumper16
Yes you can, just make an automation, trigger by entering your zone and make an action to unlock your opener. Unlocking it means to enable RTO, how long RTO is enabled you have to configure before in your opener with the nuki app.
Same here, did you manage to get it faster?
I remember that it was 1-2 seconds in the past
I think it is something with the last update of the Nuki Lock device and not the esp32 device
@madface
It’s going ok ! The problem was … (I don’t know 
)
I reinstalled the Nuki lock again. It worked on the third attempt, but then everything was there all of a sudden. 15 entities found. And quickly the integration into Homey and then it looks like this:
From here I can continue to control everything I want (love the Homey 
… HA is a great thing and can certainly do everything that the Homey can do, but with the Homey I feel in better hands and use it therefore HA only as a bridge, but that’s very much appreciated…
The correct ESP32 is important. I use this one here
and they work. The ones currently offered by AZ unfortunately already fail with the 2nd project (this one and Miflora …)
Thx
The type of the esp32 shouldn’t make a difference in my opinion, since the chip is always the same.
I use this one:
Since it has not pin header i though it has more charme 
. But i should work with your one either.
Maybe the distance is too far to the lock. If you reboot the esp, does it show the state after rebooting?
Maybe the logs could help, to set up a sensor with the logs, it’s a little above:
If the lock state is “undefined”, NUKI Hub will not publish auto discovery topics. I means the communication with the lock failed, so there it 1. makes no sense to publish anything and 2. it needs to query the lock to decide wether to publish some topics or not (e. g. wether to publish the door sensor topic).
If you have a Pro lock, it’s now official that you can’t use Wifi and NUKI Hub (or the official NUKI Bridge) at the same time. As soon as you enable Wifi, communication with NUKI Hub stops.
Hello, I have nuki integrated in home assistant via esp32 it works fine , I bought a nuki keypad, is integrated with the nuki app and works perfect, but I cant integrate to home assitant I clicked "Enabled keypad control via MQTT" but after this I´m lost. I´m trying to follow the steps by the github page but I don´t know too much about mqtt, I go to services and mqtt:publish I tryed to wright something like this, but I dont know if is the way…
topic: nuki/keypad/command/name
payload: user
…