You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Being able to lockout use of a scanned tag by requiring biometric authorization to proceed with trigger.
One scenario may be to restrict unlocking a door just because the tag was scanned by the mobile.
Another scenario may be restricting an action when a child scans a tag using parent's mobile.
Describe alternatives you've considered, if any
It seems to be the responsibility of the mobile application to provide this function. The web interface can be configured for password or numeric pin lockout on entities, but that requires setting up cards and interacting with the HA app which is avoided when scanning an NFC tag or QR code.
Additional context
It's unclear if a new property to indicated protected would be required on the side of HA core tag configuration, or just an association in-app against some configured tag.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Being able to lockout use of a scanned tag by requiring biometric authorization to proceed with trigger.
One scenario may be to restrict unlocking a door just because the tag was scanned by the mobile.
Another scenario may be restricting an action when a child scans a tag using parent's mobile.
Describe alternatives you've considered, if any
It seems to be the responsibility of the mobile application to provide this function. The web interface can be configured for password or numeric pin lockout on entities, but that requires setting up cards and interacting with the HA app which is avoided when scanning an NFC tag or QR code.
Additional context
It's unclear if a new property to indicated
protected
would be required on the side of HA core tag configuration, or just an association in-app against some configured tag.The text was updated successfully, but these errors were encountered: