-
Notifications
You must be signed in to change notification settings - Fork 58
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
Possibility of reading an alert detection for A series. #47
Comments
Hi @migvel, Well I'm not sure, is there a setting on the RLC-520A for polling an external API after a detection event has fired? How are you using it currently? Using the Reolink App? |
Thanks. here I might be assuming something wrongly, but I thought that the api call Alarm -> Motion would access as well the records of the detection of cars/persons, like they would be classified in the same way. I'm getting information for acquiring one of the devices RLC-520A since I would like to automate with some external devices. Regards. |
Oh i see, I'm not sure since I haven't used the RLC-520A yet. So I can't really say if it has some sort of |
Hi I have looked into this after picking up a new Reolink with the AI motion person/vehicle detection capability. I found the following commands available via the api.cgi My question/issue is the recordings are flagged with the AI detection tag, (person/vehicle/motion) and I would like to figure out how to know which mp4 files are tagged. This was the only source I found (https://community.jeedom.com/t/reolink-liste-de-commandes-via-api/25565) GetAiCfg, SetAiCfg, GetAiState [{ |
hi, in the newer firmware of the AI cameras, the returned json from the GetAiState command had changed (taken from a RLC-810a, firmware : v3.0.0.412), here the newer one (face detection is added but hidden in the UI):
|
Hello,
is it possible to read an alert from a RLC-520A that has been triggered by a person/car detection? I mean, to configure the camera with the manufacturer app or webapp but be polling for detections of the AI camera's feature.
Thanks.
The text was updated successfully, but these errors were encountered: