#UI Protect G4 Doorbell Pro Fingerprint Unable to Fire as Expected

1 messages · Page 1 of 1 (latest)

vagrant arch
#

I've got the G4 Doorbell Pro fingerprint reader setup and running, as well as the UI Protect home assistant integration.

The issue is this:
Trigger is set to "When Event type of Doorbell Camera Fingerprint changes to Identified" it will not fire when an identified fingerprint is scanned (this behavior is not expected).
If I set the trigger to "When Event type of Doorbell Camera Fingerprint changes from Not identified to Identified" then it will fire when an identified fingerprint is scanned, but only right after an unidentified fingerprint is scanned (this behavior is expected).

Anyone else run into this?

frozen sky
#

You will have to trigger on any state change, and then use conditions to check if the event type was “identified”.

The issue is that when you have two successful fingerprint scans, the second one isn’t a “change” (because it was “identified” before and after the second scan) and therefore won’t trigger the automation.

# 

triggers:
  - trigger: state
    entity_id:
      - event.doorbell_camera_fingerprint
conditions:
  - condition: state
    entity_id: event.doorbell_camera_fingerprint
    attribute: event_type
    state: identified
vagrant arch
# frozen sky You will have to trigger on any state change, and then use conditions to check i...

Thank you! So your code worked, but I’m not sure I fully understand why it didn’t work before haha. To be clear, it didn’t matter how many successful attempts I did. 1, 2, 3, etc. None would result in unlocking the door. It seems like there’s a third state of the entity that I can’t select as a from condition, and leaving that blank also didn’t seem to default to it.

That said, your solution worked where the trigger just looked for the state to change then add the identified condition later.

frozen sky
#

With your old code you would have to do an unsuccessful fingerprint attempt before a successful attempt works. Then every subsequent successful attempt won’t work until you have another unsuccessful one.

And keep in mind that is independent of when you create or modify your automation.

vagrant arch
frozen sky
#

maybe I'm still misunderstanding you. I realize you wanted it to trigger every time there is an identified fingerprint. However in your first option, based on how HA works, I would have expected that to only trigger on the first time there is an identified fingerprint following an unidentified fingerprint. If you don't have a bad fingerprint before the good one, it won't trigger.

# 
fingerprint: good good bad  bad  good good good good bad good
    trigger: no   no   no   no   yes  no   no   no   no  yes
vagrant arch
frozen sky
vagrant arch
vagrant arch
#

Fun new side effect noticed: if/when the camera reboots, it triggers the automation and unlocks the door. Seems like the event status/property never clears from “identified”. Anyone know how to clear the field?

frozen sky
#

you don't modify entities' states or attributes; the integration handles that.

What is the state of the event? Does it have a new timestamp?

frozen sky
#

I use a condition for automations where I trigger on event (or button) state changes.

{{ trigger.to_state.state | as_datetime(0|as_datetime) > now() - timedelta(seconds=5) }}

If the event or button changed to a state timestamp that is older than 5 seconds, then ignore it

vagrant arch
#

To be clear, the logbook in HA just shows the timestamp of when it triggered the event.