Doorbel reboot generates a fingerprint and NFC event

[Stendec1]

Feedback

I have implemented this automation that actions the front door NUKI doorlock and it is working perfectly.
However a nightly update rebooted the doorbel and apparently generated a fingerprint and NFC event resulting in the front door being opened!

URL

https://www.home-assistant.io/integrations/unifiprotect/

Version

2024.12.5

Additional information

No response

[home-assistant]

Hey there @RaHehl, mind taking a look at this feedback as it has been labeled with an integration (unifiprotect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of unifiprotect can trigger bot actions by commenting:

• @home-assistant close Closes the feedback.
• @home-assistant rename Awesome new title Renames the feedback.
• @home-assistant reopen Reopen the feedback.
• @home-assistant unassign unifiprotect Removes the current integration label and assignees on the feedback, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

[RaHehl]

#36485 will add a additional warning "When the device becomes unavailable and becomes available again in Home Assistant, repeated event processing can occur. The state change is not an issue with the integration but should be considered, mainly if the device is used for actions such as unlocking doors."

[deebeo-blip]

I am using the example doorbell automation with a notifcation through alexa "someone's at the door". I am having the issue that ,after an update, which happens at 3am, my familiy is spooked by alexa telling them someone was at the door.

Can the example automation Yaml be altered in a way which prevents that from happening? The Fingerpringt yaml automation has a few lines in them which to me look like something similar would have to be used:

not trigger.event.data.old_state.attributes.get('restored', false) and not trigger.event.data.old_state.state == 'unavailable' and trigger.event.data.new_state is not none and trigger.event.data.new_state.attributes.event_type == 'scanned' and

does anybody know if there is an event type like "ring" and if the "new_state" is being reset after a reboot? What would be the best way to solve this? I think an edit of the example automation would provide value to many new users which are not super firm in yaml scripting. Thanks!