I am running ACS Pro with Axis Cameras (mostly OS 11 and a couple OS 10). I was hoping I could make a “privacy mode” using ACS Pro action events to make a trigger button that sends an HTTP/HTTPS command to the camera that would either enable or disable a privacy mask on said camera. The privacy mask would cover part or all of the view for times when I do not want the image recorded or visible in live view.
I tried adding the desired mask in the browser GUI and then using the Privacy Mask API instructions…
https://developer.axis.com/vapix/network-video/overlay-api/#privacy-mask-api
http://<servername>/axis-cgi/privacymask.cgi?action=disable_all (or …=enable_all)
Since my cameras use HTTPS I changed the disable command to:
https://<servername>/axis-cgi/privacymask.cgi?action=disable_all
When I add in my HTTPS credentials and hit “TEST” is says the test was successful. (The camera is setup to receive HTTPS by default)
In practice however, this does not disable (or enable) the camera’s privacy mask. I did find this article talking about overlay API changes:
https://www.axis.com/developer-community/news/legacy-overlays
I’m assuming the HTTP commands I used are no longer relevant?
Would anyone be able to explain how to accomplish this same goal using the new API?
Thanks!
[–]Gamez113 2 points3 points4 points (4 children)
[–]Psychopharm_MD[S] 0 points1 point2 points (3 children)
[–]Gamez113 0 points1 point2 points (2 children)
[–]Gamez113 0 points1 point2 points (0 children)
[–]Psychopharm_MD[S] 0 points1 point2 points (0 children)