Difference between authorizing with ID Type "app" or "bridge"

Nuki APIs Bluetooth API
1

What exactly is the difference or are the consequences of using these two?

Will the lock handle these differently? Are there consequences for re-authorizing the same bridge or app?

2

I am testing the difference, when I authorize as “app” and I ie perform a lock action changing the status I get this as expected:

iBeacon ID: 004C Major: 7503 Minor: 39044 UUID: a92ee200-5501-11e4-916c-0800200c9a66 Power: -59
But it does not change back to “Power: -60” after reading the status.

When authorize as “bridge” I also get the above but when the status has changed and I have read the (new) status it changes to:

iBeacon ID: 004C Major: 7503 Minor: 39044 UUID: a92ee200-5501-11e4-916c-0800200c9a66 Power: -60

Two questions:

  • Is this by design, so if an app is registered the lock always keeps sending the “Power: -59” flag indicating something has changed?

  • Does the lock keep track if all authorized devices have read a changed status until changing the “Power” flag back to -60?

I am testing with a v2 lock:
firmwareVersion :2.14.5
hardwareRevision :11.1

3

First off: This is outside of the publicly documented part of the BLE API (Because it is not intended that anyone tries to authorize itself as bridge and potentially mess up the system, neither is it intended to build devices with bridge like functionality replacing the Nuki Bridge).

Yes

No. The “What’s new flag” is used only by the bridge and only modified when the bridge connects.