Replies: 8 comments 15 replies
-
|
Love this idea! |
Beta Was this translation helpful? Give feedback.
-
|
hello, i have 32 hikvision différents model with ONVIF bad implementation i can do the hikvision brand issues |
Beta Was this translation helpful? Give feedback.
-
|
I'm happy to support here too. I have an Axis Q6128-e I have some python knowledge (and some other languages etc). I do wonder though how much effort this proxy would be, opposed to a "patched" frigate build. I will need to better understand what the gap exactly is (why is that function so essential for autotracking and how would a proxy/patch fix this), and if this fix is the same for all axis cameras and all other brands too, or if they just all have different quirks. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Could you enable onvif debug logs, restart Frigate, and paste the output here? |
Beta Was this translation helpful? Give feedback.
-
|
Happy to! 2025-05-22 18:12:26.535718614 You have successfully opted out to send the telemetry data. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, it looks like the same issue as it's always been, unfortunately - Axis firmware doesn't implement support for the ONVIF standard's
So yes, manual changes will still be required. Perhaps @markdmann 's code will also solve this. |
Beta Was this translation helpful? Give feedback.
-
Yup. It’s so darn close to being completed. I just need a few more hours and I can drop the repository with the home assistant addon. I’ll need someone to test the docker container who is running bare metal frigate as I’m running bare metal Home Assistant with a frigate add on. It should work regardless. The way it functions is by setting your ONVIF login information for each axis ptz camera in the frigate config to the IP address running my bridge software (in my case and ideally it’s all on the same machine). Each camera then gets a unique port (multi camera support, single bridge app). My bridge software listens on each port for onvif soap commands coming from frigate, translates them to the Axis VAPIX communication standard, sends them to the camera, listens for the response, then re-translates the VAPIX responses back into the ONVIF formats frigate expects, and sends them back to frigate. It’s very lightweight and as far as I can tell adds little if any latency to the control. Since the bridge software is written to translate between the two standards, it should work for every AXIS PTZ camera that accepts VAPIX. In the end, it’s likely something that could be integrated directly into to frigate to add support for VAPIX. Understandably, that could be more than the devs want to commit to, and in the end, it might be better to leave it external as a separate docker container. I could package the communication layer as a single file and break out the information specific to each camera/brand as a separate config that the community could add on to as needed. I’m hoping I can share this weekend! I just need a few hours without kids breathing down my neck lol. |
Beta Was this translation helpful? Give feedback.
-
|
Updating to 0.16 beta 2 and applying the patches (forcing "get_service_capabilities" to true and changing ["absolute_zoom_range"] to ["zoom_limits"]) made it finally work so it did something :D |
Beta Was this translation helpful? Give feedback.
-
|
I have just finished up writing and testing software that does this for axis cameras, I’m not sure about other cameras but perhaps others can build on my code in time. It functions by running on the same box as frigate, intercepts then translates onvif soap commands to axis VAPIX commands, and then sends VAPIX commands to the camera. It also works in reverse to send frigate the correct information. I have a bit more work to put I to it and hopefully in the next few days I’ll have it packaged up to run in docker or home assistant as an add on. I shall return. |
Beta Was this translation helpful? Give feedback.
-
|
I think go2rtc itself may be a good place for it. It already exposes an ONVIF server, and PTZ controls are being worked on. @AlexxIT, do you have some opinion on it? However, go2rtc exposes a single ONVIF server. I don't know if different PTZ controls can be tied to different ONVIF profiles. If yes, all good, but Frigate would need to support selecting which profile to control the PTZ on. |
Beta Was this translation helpful? Give feedback.
-
|
Any features outside of regular streaming (file recording, PTZ, events) should be well designed from a code design perspective. It takes time. |
Beta Was this translation helpful? Give feedback.
-
|
If there is any movement on this, I am willing to contribute support for a Sunba 405-D20X. |
Beta Was this translation helpful? Give feedback.
-
|
Went ahead and created a small proxy here: https://github.com/eporsche/frigate-to-baby1t-onvif-proxy It translates from RelativeMovement to Continious Movement (which my camera supports) Does not support zoom or automatic follow yet. |
Beta Was this translation helpful? Give feedback.
-
|
lol, I wish I had found this like 1 week earlier before starting from scratch and proto-typing an ONVIF proxy in Node-Red for my TP-Link Tapo C500 cameras. Forking your repo to see if I can add my Tapo changes. I'm still pretty new to ONVIF specs but catching on quickly and was able to get AutoTracking working with the C500 which responds to RelativeMovement commands although the cords don't appear to be scaled correctly for the FOV. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry guys! I got sick and lost track of this project. I have it mostly working but somehow broke it while trying to get it packaged as a downloadable add-on, had been running locally for a while but since I ran out of free time, I had to revert to my blue Iris build... which I don't like. Want to get back on frigate.
My life is always busy but gets stupid crazy at times. I'll try to post my code as it sits and see if one of you guys can take it to the next step, I'm absolutely swamped at work and with the family. Teamwork makes the dream work. I should have posted it long ago.
…________________________________
From: sirduke989 ***@***.***>
Sent: Tuesday, November 11, 2025 10:53:26 AM
To: blakeblackshear/frigate ***@***.***>
Cc: Mark Mann ***@***.***>; Mention ***@***.***>
Subject: Re: [blakeblackshear/frigate] Camera control proxy (Discussion #16960)
lol, I wish I had found this like 1 week earlier before starting from scratch and proto-typing an ONVIF proxy in Node-Red for my TP-Link Tapo C500 cameras. Forking your repo to see if I can add my Tapo changes. I'm still pretty new to ONVIF specs but catching on quickly and was able to get AutoTracking working with the C500 which responds to RelativeMovement commands although the cords don't appear to be scaled correctly for the FOV.
—
Reply to this email directly, view it on GitHub<#16960 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BRVDA7F6IAWTNOPOHOU7YPT34IPBNAVCNFSM6AAAAABYL7SMF6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJTHA4TCNQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Many cheap cameras have incomplete and buggy implementations of ONVIF or don't implement the specifications at all, relying on proprietary protocols for camera control.
Even expensive cameras rarely work with Frigate's autotracking system due to incomplete ONVIF implementations.
Frigate developers understandably resist including workarounds for these issues in the codebase. It would make it messy, complex and expensive to maintain.
Would it make sense to create a separate project that provides an ONVIF proxy? It could implement all the hacks needed for various cameras, including ones that don't support ONVIF at all but have other protocols or APIs to control PTZ and other camera features, while providing a clean, ONVIF-compliant interface for Frigate (and other consumers).
Or perhaps it should provide a new, modern API rather than ONVIF, which is arguably overly complex and is starting to feel dated. (If one were to create a protocol from scratch today, one probably wouldn't base it on SOAP.) Then it could also support common camera features not covered by ONVIF.
Essentially, it could do for camera control what go2rtc does for video streams.
(This discussion started with this comment.)
Beta Was this translation helpful? Give feedback.
All reactions