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
The only alerts created for development purpose are created by the false cameras (you can check cameras' behavior here : #10).
But the the timestamp of the alerts are set by the engine which means :
we cannot create alerts in the past
all the alerts will be attached to the same Sequence object in the API database (which means a Wildfire) because we need to have a pause of 30min between two alerts in order to create a new Sequence.
Wanted Behavior
We would like to be able to create Detections with a python script, using the /detections/ POST endpoint of the dev env API (documentation here)
In order to link the detections to an existing cameras you will have to generate a token thankts to the endpoint /cameras/{camera_id}/token. For that you can hardcode camera_id=1 for the static camera and camera_id=2 for the ptz camera.
No need to containerized the script, you can use the localhost:5050 url.
Current Behavior
The only alerts created for development purpose are created by the false cameras (you can check cameras' behavior here : #10).
But the the timestamp of the alerts are set by the engine which means :
Wanted Behavior
We would like to be able to create Detections with a python script, using the /detections/ POST endpoint of the dev env API (documentation here)
In order to link the detections to an existing cameras you will have to generate a token thankts to the endpoint /cameras/{camera_id}/token. For that you can hardcode camera_id=1 for the static camera and camera_id=2 for the ptz camera.
The text was updated successfully, but these errors were encountered: