AuthorizationId doesn't change on rolling auth log about nuki_hub HOT 3 CLOSED

State/AuthorizationId not changing with different codes/fingerprints is correct.
The keypad has one authorization (id) which is the same for all actions executed through the keypad, regardless of used code and method. Trigger and codeId are specific to certain codes and actions (e.g. fingerprint, arrow or code).

I do agree that it might not be the best value for the HA sensor.
I'll change it to index which will count up with every new log entry.

There are some more needed improvements on the rolling log as rebooting the ESP currently resets the rolling log and replays the max auth log count (default 5)

from nuki_hub.

i am testing a workaround with any statechange of timeSecond as trigger.

trigger:
  - platform: numeric_state
    entity_id:
      - sensor.nuki_garage_rolling_authorization_log
    attribute: timeSecond
    above: -1
    below: 61

action:
  - conditions:
      - condition: state
        entity_id: sensor.nuki_garage_rolling_authorization_log
        attribute: authorizationName
        state: garagehaus (Keypad)
    sequence:
      - service: cover.toggle
        target:
          entity_id: cover.garagentor_haus
        data: {}
      - service: notify.mobile_app
        data:
          title: garagehaus (Keypad) triggered
          message: ""

from nuki_hub.

an easy way to trigger automations if code/fingerprint is entered.
also trigger automation whene last key entered is the same as before.
if homeassistant reboots the last key entered should not trigger the automation.

from nuki_hub.