Smart Lock Ultra/Pro/Go Firmware Beta 5.8.x

Smart Lock Ultra/Pro/Go Updates

Smart Lock Beta 5.8.0
(05.03.2026)

  • Enhanced logging for Beta-user troubleshooting

Smart Lock Beta 5.8.1
(19.03.2026)

  • Overall performance and stability improvements

Smart Lock Beta 5.8.3
(23.03.2026)

  • Infrastructure upgrade → more info here.
1 Like

Hi,

Everything was working perfect for me with Smart Lock Beta 5.8.0 on a Nuki Ultra.
Last night it updated itself to Smart Lock Beta 5.8.1 and since then the Auto Unlock works BUT it doesn’t UNLATCH the lock. It just opens the lock and in order for me to open the door I have to open the app and open the door manually.
I tried to recalibrate the lock but it didn’t help…
Is there a way to downgrade to 5.8.0 or are you aware of a workaround?

Thanks in advance.

If you look into the activity protocol of the lock, do you see a difference in the auto-unlock entries before the update and afterwards?

In your Smart Locks settings > administration > general > door fitting, is there handle or knob/bar active? (This setting actually defines the default behavior of Auto-Unlock. Only for knob/bar it is “open door”. For handle it’s “unlock”).

Hi Jurgen,

Thanks for your reply!

Looking into the activity log, I can definitely see that before the firmware update, whenever I arrived home, a log entry with my name and both Auto Unlock & Opened door appears.
However, after the firmware update - ONLY Auto Unlock appears in the log.

In the Smart Locks settings > administration > general > door fitting, the knob/bar is active, as it was before…

Waiting for a solution…

Thanks again.

Short term solution is to choose the lock action you want to be executed in the expert settings of Auto-Unlock in the Nuki App.

Which App do you use, iOS or Android? And beta or release? (You can find the detailed App version in the Menu > Help > App version section)

So I understand this is a bug…
I’m using the release iOS version.
Found it and selected Open Door instead of Unlock under - Device found.
Thanks.

Thanks for your feedback. We have identified the issue to be an iOS issue and we are going to addressed it and provide a fix as soon as possible.

1 Like

That’s GREAT!
I’m so happy I was able to help you identify this bug.

2 Likes

Did you change anything on MQTT? ioBroker MQTT is no longer working reliably — there are disconnects or error messages.

Client [Nuki_xxxxx] Received pubrec on Nuki_xxxx for unknown messageId 1

I do notice that the last week the notifications arrive late. From minutes to even half an hour later.

The notifications come later and later. Strange that it is suddenly like this now.