Opener ring sound issue when not connected

Hello Nuki dev. team and community.

I encounter a reproducible issue, that I had after installing my Opener (miraculously solved by a hardware replacement), and that reappeared when updating to firmware v1.10.1:

My Opener is standalone (I have no bridge, no smart lock…), is connected to an Urmet 1150 intercom (which was a replacement of another home unit type, because the original Urmet 1130/12 reference no more exist).
The opener configures well, works well (producing sounds when pushing the button, opening the door, detecting ring when looking the history log, …) but it does not produce a ring sound when someone rings.
My Opener settings are configured to produce a sound (maximum volume) when someone rings… but it does not work.

As explained, this issue was solved 2 years ago by replacing the module (after lot of tryes and tests), but reappeared after this last firmware update.

But I suspect the issue not being an hardware issue but a software bug, because:

  • the log history displays correctly that a ring happen at the correct time (so what would prevent it to produce the sound ?)
  • when I press the interphone ring button at the building front door (I’m ou of Opener Bluetooth range), the opener does not produce sound (the issue we speak here), but when coming back to my house and opening the Nuki app, immediately the Opener produce the ring sound (while I touched nothing else) ! As if the connection of the smartphone to the Opener would unblock the ring sound blocked and delayed somewhere in the opener software until that event occurs.

If you know a workaround…
Else please, fix this bug quickly, since I bought this Opener specifically for replacing my interphone low ring sound.


Exactly the same thing happens to me and it is very annoying not to have sound when ringing the doorbell, I need this bug to be resolved urgently, thank you very much

Nuki told me that it was because not working without the bridge… which is not totally true since it worked perfectly without it during 2 years, so if it is no more the case now, it is only because of their software update.

Whatever, I had to improve my installation and now I have a bridge, and the issue is solved.

But I’m not happy of the Nuki support: this is clearly a bug introduced by their software update and they provided no solution excepted resquesting me to buy an additional device for 100€.

Well, I have a bridge and it happens to me, so as you say, the problem is not there, it is clear that it is in the bridge.
Thank you

Hum, you should contact them. For me the discussions stopped at “you must buy the bridge to solve the issue”.
My request reference was 380865 in case you want to enforce your problem by showing the issue is not isolated.