-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add support for intelbras SS 3540 MF FACE EX (Dahua ASI6213J-MW) Face recognition Acess Control #296
Comments
i think is related to #166 |
i can confirm that doing what was said in #166 allowed me to view full event info. Change codes = ",".join(events) to codes = "All"
|
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Im trying to Add my FaceRecognition Acess control to homeassistant, is a White label from dahua and uses the same API from what i have seen in the codes. I can add the device using the dahua integration, it recognizes as:
Device info
SS 3540 MF FACE EX
by Dahua
Firmware: 2.000.00IB007.0.R,build:2023-02-23,
but i only get the motions events in devicelog, i can turn on the lights , and unlock the door via call service.
Serial Number starts with YP4L
Describe the solution you'd like
A clear and concise description of what you want to happen.
When i call the API in python using digest Auth i get the folling response of event:
And i would like to pass those attributes to HA,
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
the logs:
an example of the device response in the device documentation:
avaible at https://intelbras-caco-api.intelbras.com.br/obtendo_eventos/eventManager
any help is aprecciated as this would add support for alot of future face recognition acess control devices made by dahua
The text was updated successfully, but these errors were encountered: