First of all, flash the latest version (you may wait a little because I’m about to release 8.12).
Then, try to enable “Restart on disconnect” and set “Restart if bluetooth beacons not received” to something like 60 seconds.
Many thanks, i’ll wait for the new version. Thank you.
Where do you get the identifier from? I think that’s what’s making it hard for me. I’ve tried using lock.nuki, as it’s the entity id of the lock itself, I also tried using the device id I found in the diagnostics and this 
but nothing worked
You can see it in the MQTT Info in the the device view (under your MQTT integration) in the auto-discovery topics (Payload). The format is nuki_ followed by a lower-case hexadecimal number.
Wow, my mistake is I even used that from nuki>presence>devices
But I used capital letters as it’s shown there.
Thank you very much!!!
1 Like
I think I have the same problem. Despite changing the Query interval (I set 3600 seconds), I am receiving every 3 seconds lots of MQTT messages. Does anybody has this “problem” too?
Well, that was a bug in 8.4. Unless you first installed that version, you should not be affected by that (since fixed) bug. Most likely you have enabled RSSI reporting, then some messages every few seconds are normal (depending on your RSSI reporting interval, which is completely separate from the lock query interval).
RSSI reporting was disabled (-1) I have updated to version 8.18 but same behaviour. Every 3 seconds 3 messages are received (topic presence/devices, battery/voltage and info/hardwareVersion). Maybe I should try with a fresh start.
@dani85 Please post the content of the system information page (click on the firmware version number). It might be better to create an issue on Github though in order to not spam this thread.
Hello,
i have a problem with the delay. When I click unlock in MQTT, it takes 3-8 seconds for the lock to open. the same with locking. does anyone have any tips on what could be wrong here?
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.