[Camera Support]: Onvif not working in 0.16-beta3, works in 0.15.1 with same camera #18731
Replies: 9 comments 32 replies
-
|
Frigate 0.16 updated the ONVIF Python package to Hikvision users have reported that setting Does your camera have a configuration for basic or digest authentication? Do you have any special characters in your password? |
Beta Was this translation helpful? Give feedback.
-
|
Well, it works in 0.15.1, i have tried to switch back and forth between versions(0.15<->0.16) multiple times to confirm that this is not a 'glitch', i have set ignore_time_mismatch: True in onvif config, camera has both basic and digest auth. i tried both(multiple times), no special characters in password, only letters and numbers. Also i tested onvif using free windows app - onvif device manager, it connects without any problems and shows profile list , same as frigate 0.15.1 |
Beta Was this translation helpful? Give feedback.
-
|
The logs are showing that your camera itself is refusing the connection with a 400 error. You can see what Frigate is doing in the code here, which mimics what Home Assistant does: Line 93 in 2d586ee You could also try setting |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for repeating, but i have tls_insecure: true and ignore_time_mismatch: True in config: I'm not touching frigate config, not changing anything, i just change:
When i change it back to frigate:stable-tensorrt it starts working I have attached 2 debug logs: from 0.15.1 (working onvif) and 0.16.beta3(not working onvif) |
Beta Was this translation helpful? Give feedback.
-
|
For some users, the old version of |
Beta Was this translation helpful? Give feedback.
-
|
Hikvision cameras have settings for the auth mode used, I had to change from digest to use the API in automations |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
I have the exact same problem. Older fw like the one shown by NickM-27 work fine. However, a new camera, with this similar UI (as the one shown by @rstanislav have this problem. Tried all combinations of configurations, different users, etc, nothing works. Everything results in the same Not sure what to do next. |
Beta Was this translation helpful? Give feedback.
-
|
This is most likely a digest authentication issue, as @NickM-27 indicated. |
Beta Was this translation helpful? Give feedback.
-
|
Well, but I tried both "digest" and "digest&ws-username token", same issue
on both. Same with tls insecure true/false. Same with the time flag set
true/false.
What else can I do?
El mié., 10 de diciembre de 2025 20:57, Josh Hawkins <
***@***.***> escribió:
… This is most likely a digest authentication issue, as @NickM-27
<https://github.com/NickM-27> indicated.
—
Reply to this email directly, view it on GitHub
<#18731 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD73TR3K35RFXESQJTACCD4BCXNDAVCNFSM6AAAAAB7LUSK32VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRSGUYTMMA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Does it work if you disable authentication? That would confirm the issue. I'm not sure what else can be done. Myself nor any of the other devs have the specific camera in question, so we can't reproduce the issue. We've not had any other reports of users with issues that were unable to be resolved through at least one of the means described in this discussion. |
Beta Was this translation helpful? Give feedback.
-
|
I haven't figured a way to get access to onvif without any authentication.
the webgui let me enable it without any users on the list (as seen on the
above image), but that only means you can't use onvif at all.
Does the 19.12 version reported by the webgui means something?
I think this is just a hikvision thing, on the newer firmwares
El mié., 10 de diciembre de 2025 21:26, Josh Hawkins <
***@***.***> escribió:
… Does it work if you disable authentication? That would confirm the issue.
I'm not sure what else can be done. Myself nor any of the other devs have
the specific camera in question, so we can't reproduce the issue. We've not
had any other reports of users with issues that were unable to be resolved
through at least one of the means described in this discussion.
—
Reply to this email directly, view it on GitHub
<#18731 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD73TWH442K76LKZD2AZBT4BC22VAVCNFSM6AAAAAB7LUSK32VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRSGUZTGMY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Some users have reported that for some Hikvision cameras, you need to create a separate ONVIF user. Standard admin credentials that you use to log into the camera's firmware will not work for ONVIF. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the users shown in that list from that picture are just for onvif.
I've tried with a regular user as well as an administrator, and the same
thing happens.
I've set the debug option for ptz on frigate, but I only see the url that
the code access, but not its contents. Maybe there's something else I could
turn on for debugging purposes?
El mié., 10 de diciembre de 2025 23:59, Josh Hawkins <
***@***.***> escribió:
… Some users have reported that for some Hikvision cameras, you need to
create a separate ONVIF user. Standard admin credentials that you use to
log into the camera's firmware will not work for ONVIF.
—
Reply to this email directly, view it on GitHub
<#18731 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD73TRYZKY7I3SPJOZ7US34BDMYBAVCNFSM6AAAAAB7LUSK32VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRSGYYTKMA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
@cocus Frigate’s developers couldn’t care less about this issue. Their stance is that it’s “not a Frigate problem” but a “third-party library” problem - never mind that Frigate relies on that library. And since Home Assistant uses the same library, they seem to feel entirely absolved of responsibility. As I mentioned on Reddit: it’s embarrassing. I honestly didn’t expect this kind of behavior as Frigate+ user. |
Beta Was this translation helpful? Give feedback.
-
Just curious - with what information we have provided and what you have deduced about the issue, what is the course of action you are expecting us as the Frigate developers to take? Since we have plenty of evidence that this is an upstream issue, the standard way to approach this in the open source world is to have the upstream maintainers address their package's issue. |
Beta Was this translation helpful? Give feedback.
-
If updating or replacing the ONVIF library breaks functionality that previously worked, this is likely an issue on Frigate’s side - especially given that many users purchase hardware (and spend real money) based on Frigate’s compatibility list. In such cases, rolling back the changes may be the most appropriate course of action, particularly since the author of the library in question appears entirely indifferent to the problem despite an opened issues. This would be understandable if the issue were limited to Hikvision cameras, but based on the information I have, the root cause is a severe violation of the ONVIF protocol implementation within the library, specifically at the authentication stage. |
Beta Was this translation helpful? Give feedback.
-
|
I want to address the idea that “if updating the ONVIF library breaks functionality that previously worked, it must be a Frigate issue.” That’s not accurate. As you know, Frigate doesn’t implement ONVIF ourselves, we rely entirely on upstream libraries. When an upstream ONVIF implementation changes behavior, becomes stricter, introduces bugs, or handles authentication differently, those changes come from the library, not from Frigate’s code. This is normal in open-source software: consumers of a library inherit its strengths and weaknesses, and protocol-level issues have to be fixed upstream, not in every project that uses it. As for why we upgraded: the old ONVIF package was generating a large volume of reports from users whose cameras worked in Home Assistant but failed in Frigate. That strongly indicated the old library had significant gaps or non-compliant behavior that we could not fix locally. Moving to the newer, widely used library (the same one HA uses) resolved ONVIF functionality for many more users than it affected. I fully understand that this update caused issues for you and the other user in this thread, but rolling back would simply re-break ONVIF for a much larger portion of the community. So this is not a reasonable course of action. We’ll continue to investigate reproducible regressions on our side, but protocol violations or authentication issues inside the upstream library are not something Frigate can realistically maintain or patch long-term, especially if the ones writing and maintaining those patches don't have the problematic hardware to test with. |
Beta Was this translation helpful? Give feedback.
-
|
I'll also say that If you’ve pinpointed the root cause in And this is really the beauty of open source: users who run into real-world problems often become the very contributors who help resolve them. Your findings could meaningfully improve the experience for a lot of people. |
Beta Was this translation helpful? Give feedback.
-
|
TL;DR: I don't see evidence of a bug in Frigate or On further investigation, I do not believe what you have reported as a bug is actually a bug. Tracing the code,
The In Frigate sets this in its code based on your config variable, Line 104 in 1de7519 So, if you set The logs you posted here and in your report at openvideolibs/python-onvif-zeep-async#122 are indicative of setting So, while I'd suggest also trying to set Finally, Hikvision users have also reported needing to use a separate ONVIF user and that the admin credentials to log into the camera's firmware will not work for ONVIF. That's about all the debugging I can do without the hardware to reproduce. If you find more, please let us know. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I'm not a Frigate+ user, and I certainly can't expect an open source
team to fix problems for my setup, but it's true that if the core library
has a bug, it might be cool to fix that bug. Then again, I haven't used
that library myself to know exactly what's going on, so if you have and
know where's the issue, it might be possible to spin up a PR against it. If
the owners don't like it, well, it's not the end of the world, in theory we
could just patch the library inside the frigate docker ourselves every
single time there's a frigate update.
Would be cumbersome, but well, I prefer that.
So that's the thing, what can I change on the config to enable much more
verbosity from the ptz?
then, I could try to reproduce the issue using just the library, and then
see what's going on. If you have done that, and might have some tips, I'll
take them.
El jue., 11 de diciembre de 2025 00:25, Stanislav ***@***.***>
escribió:
… @cocus <https://github.com/cocus> Frigate’s developers couldn’t care less
about this issue. Their stance is that it’s “not a Frigate problem” but a
“third-party library” problem - never mind that Frigate relies on that
library. And since Home Assistant uses the same library, they seem to feel
entirely absolved of responsibility.
I shared detailed information and full debug logs a while back explaining
exactly why this happens. In short: during authentication, the library
claims it will use the plain password, yet it sends a hashed one instead,
which of course causes authentication to fail. The library’s authors on
GitHub clearly aren’t interested either; they haven’t even responded to the
issue that’s been sitting there for almost a year.
As I mentioned on Reddit: it’s embarrassing. I honestly didn’t expect this
kind of behavior as Frigate+ user.
—
Reply to this email directly, view it on GitHub
<#18731 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD73TQTP6UZOKVIUJI5LB34BDPZJAVCNFSM6AAAAAB7LUSK32VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRSGYZDMNI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
When I created the first issue a long time ago, the Frigate developers said they wouldn’t accept any fixes (PRs) because Frigate’s rules don’t allow changes aimed at addressing problems with specific devices. And since the author of the ONVIF library also isn’t interested in fixing it, things don’t look very promising. Especially considering response from Frigate earlier - basically, “if something breaks when using a new onvif library, we should just remove that camera from the compatibility list.” |
Beta Was this translation helpful? Give feedback.
-
|
@cocus If you haven't seen the thread on the Home Assistant repo where users have reported similar issues and solved them, you might want to see if any of those work for you: home-assistant/core#119107 |
Beta Was this translation helpful? Give feedback.
-
Oh, HOLD ON! I just used another user and password, and it now works. I was using "onvif" as a username. I changed my password but still used the same "onvif" user and it now works!. The original password didn't have any exclamation marks, but it did have upper/lowercase and numbers. New password has lowercase only and a single exclamation mark, and it works. I've tried with the combo "homeassistant" as user and "homeassistan!" as password (note the typo, this is due to the webgui not letting me use the username string in the password), and that works. So for others having this issue, you might want to test that password and see if it works for you! |
Beta Was this translation helpful? Give feedback.
-
|
Great! Can you describe the combination of Frigate config settings that works for you? |
Beta Was this translation helpful? Give feedback.
-
Sure, I have the following on frigate (using the test password to show, I'm using something different): On the camera side: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much. This should help other users in the future. |
Beta Was this translation helpful? Give feedback.
-
|
wth.... i feel like its wrong.. but yeah the fix for me was to create a new user...... i tried removing and readding the first user i made, even tried using the password above and failed still its like something gets it in a bad state like the user is tied to the auth mode and even removing it it under the hood stores it in memory/cache/db or something on the camera tldr if you made it here just try a new user after you have tried changing all the other suggestions above 😆 edit: worth noting when i removed the old user the new user no longer worked... readding the old user again made the new user work again there is deffs dragons in this camera |
Beta Was this translation helpful? Give feedback.
-
|
I recently upgraded from Frigate 14 to 16 and also found my ONVIF PTZ no longer worked in the Home Assistant advanced camera card. I tried several user accounts along with 'tls_insecure: true' and 'ignore_time_mismatch: true', no luck. What worked for me was switching to an admin user. Previously a standard user had worked. Reolink TrackMix PoE on latest firmware (v3.0.0.5428_2509171972). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
Camera: hikvison DS-2DE3A404IWG-E(from recommended Frigate list) with 5.8.0 firmware, ntp time is set and sync on server and camera, ignore_time_mismatch: True is added to config, time inside docker container is also correct, ONVIF device manager is connects successfully, but frigate fails to connect with 'Unable to get Onvif media profiles for camera: cam5: The action requested requires authorization and the sender is not authorized'. On v0.15.1 it works without any problems.
Steps to reproduce
--
Version
0.16-beta3
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
--docker-compose file or Docker CLI command
--Relevant Frigate log output
Relevant go2rtc log output
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
Hikvison DS-2DE3A404IWG-E
Screenshots of the Frigate UI's System metrics pages
--
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions