Hi Nuki team,
I have been testing the Nuki Opener on a Ritto TwinBus installation (apartment station 17230/0) with three independent entrances.
Building layout
The building has:
• Street gate A (one side of the residential block)
• Street gate B (opposite side of the residential block)
• Courtyard entrance door
All three entrances can normally be opened from my apartment intercom.
Findings
The Opener can successfully learn the opening signal for any one of these entrances.
For example:
• If I teach the Courtyard entrance, it works perfectly.
• If I then teach Street gate A, Street gate A works, but the Courtyard entrance no longer does.
• The same happens with Street gate B.
In other words, every newly learned entrance replaces the previously learned one.
This behavior is completely reproducible.
Interesting observation
The Opener is also able to execute “Open” without using Ring to Open on this installation.
This suggests that the firmware is not simply replaying a generic bus command but has learned the specific TwinBus telegram required for the selected entrance.
Therefore, it appears that the firmware currently stores only one learned door-opening telegram.
Questions
-
Is storing only one learned door-opening telegram an intentional firmware limitation?
-
Is there an undocumented API or BLE command that allows selecting or uploading multiple learned telegrams?
-
Is support for storing multiple learned telegrams planned for a future firmware update?
Supporting multiple learned telegrams would allow the Opener to work correctly in apartment buildings with multiple independent entrances.
I would be happy to provide additional information, logs, photos or perform further testing if that helps.
Thank you!