-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication Type for Access Event #71
Comments
Update:
I'm not sure what "credential_provider" all entails but may be able to get the same information from there? Maybe something like:
Thanks! |
@jblattel this integration uses websockets for status updates as you came to find out. The problem is supporting this across multiple UA hubs as they all have different (and undocumented) messages. |
I'm guessing they are the 3 they indicated (NFC, CALL and PIN_CODE) at least for the door[id] ... authentication.credential_provider - but yeah there is no mention of that really anywhere in the doc. I may go ahead and take a stab at implementing this. Least take a look at the raw logging coming out of the event and test those 3 parameters. Less there's some other hidden code it looks like those event objects and associated attributes just get put up onto the HA bus, so fairly straightforward. |
@jblattel yeah if it's just about adding a property to the event. It should be as simple as getting the property from the "access.logs.add" websocket message and adding it to the event attributes |
@imhotep - I see you merged the change awesome - will close this. |
Hello and thanks for all of your work. I was wondering if you could expose the authentication_type to the Access Event. I believe the API supports this here:
This way we can determine how access was granted and e.g. take action for remotely authorized access vs say a phone tap. Or better way to look at it an unknown user that has been granted access via the actor or the actor him/herself tapping in.
I thought I'd take a stab at working on this myself but my level of understanding of HA is basically NILL.
Thanks again.
The text was updated successfully, but these errors were encountered: