[Camera Support]: Hikvision DS-2SE7C144IW-AE and autotracking #15793
-
Describe the problem you are havingI have a Hikvision DS-2SE7C144IW-AE running firmware V5.5.821 build 220712, which to my knowledge is the latest. I have spent a lot of time trying to find a newer one at least. Hikvision isn't the easiest provider when it comes to firmware. Anyway. The autotracking sometimes works, sometimes not. I have not been able to figure out when and why. Built in tracking has of course been turned off to not conflict with Frigate. My Frigate doesn't start at all if I set I have search the discussion forum and I am not sure that I am seeing the same issue as other's with Hikvision do. Also, the fact is that the autotracking have worked, I just can't figure out why/when it's working. My object detection works great, getting plenty of events over MQTT. Frigate doesn't seem to try to zoom into the object either, which I assume is the same issue as not trying to track the object. Any advice? PS! The camera id for the relevant camera is Version0.15.0-87e7b62 (same with 0.14 stable) What browser(s) are you using?No response Frigate config filecameras:
cam-12-ptz:
enabled: true
ffmpeg:
inputs:
- path: rtsp://l:p@cam-12.localnet/Streaming/Channels/103
roles:
- detect
- path: rtsp://l:p@cam-12.localnet/Streaming/Channels/101
roles:
- record
objects:
filters:
person:
min_score: 0.6
threshold: 0.8
onvif:
host: cam-12
port: 80
user: frigate
password: REDACTED
autotracking:
enabled: true
calibrate_on_startup: false # Frigate doesn't start when doing this on cam-12. Gets stuck at 0%.
zooming: relative
track:
- person
#- car
- bicycle
- motorcycle
- bus
- truck
- dog
- cat
#- bird
required_zones:
- zone_0
return_preset: Preset 6
timeout: 30
zones:
zone_0:
coordinates: 0.072,0.127,0.951,0.107,0.948,0.89,0.069,0.889
loitering_time: 0
inertia: 3
motion:
mask: 0.323,0,0.322,0.078,0.018,0.074,0.017,0
threshold: 40
contour_area: 15
improve_contrast: true
lightning_threshold: 0.6Relevant Frigate log outputRelevant go2rtc log outputN/AFFprobe output from your cameraN/AFrigate statsNo response Operating systemDebian Install methodDocker Compose Object DetectorOpenVino Network connectionWired Camera make and modelHikvision DS-2SE7C144IW-AE Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Answered by
hawkeye217
Jan 4, 2025
Replies: 3 comments 14 replies
-
|
See the autotracking FAQ in the docs: https://docs.frigate.video/configuration/autotracking#i-tried-calibrating-my-camera-but-the-logs-show-that-it-is-stuck-at-0-and-frigate-is-not-starting-up Unfortunately your camera just has old/buggy firmware. |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
Autotracking makes an ONVIF Your calibration logs are exhibiting the exact behavior I've seen with other buggy Hikvisions. I'm a little surprised though that you said that autoracking "sometimes works, sometimes not". If you're seeing an initial movement but then no further movement to follow a subject, that would also be an indication of the |
Beta Was this translation helpful? Give feedback.
-
|
Does Frigate subscribe to events to get I will also have to look into how I can make a Sadly, as said originally, I haven't understood why the tracking sometimes work and sometimes don't. I will definitely try to understand that better in the future, I just don't know what to do, yet. But it could very well be a firmware issue. I have another Hikvision PTZ as well. I remember the first time I tried that one with Frigate. Even with |
Beta Was this translation helpful? Give feedback.
-
|
Frigate doesn't subscribe to anything from ONVIF - everything is polled. Calibration makes a series of movements with the camera (using the special Some Hikvisions (I'm presuming newer models) no longer exhibit this bug. Seems like their firmware devs actually did fix it. |
Beta Was this translation helpful? Give feedback.
-
|
I have now done four tests. First I tested what you said. I enabled calibrate in Frigate's config and restarted. As usual it gets stuck. From what I could see with Whenever Frigate (or the camera, depending on how we want to see it) got stuck I moved it slightly using Hikvision's app. This released it so that Frigate could continue. I guess this hints to the fact that there is some case with the camera where it missed to update its status. Not 100% guaranteed, but likely. After 10-20 moves with the app (I didn't count) the calibration finished. I assume the data is skewed though, but this was a test to get more understanding of the issue afterall. Next I started to do similar things with Left move test: Up/down move test: Zoom test: I will probably take some time here to let things sink into my brain. But if I don't get a better idea I will write a snippet that moves the camera around a bit randomly for 5 minutes to see if I can get it stuck as well. There are a few things I could imagine causing issues, though I see them as extremely far fetched. Like:
Any input is of course welcome. Regardless I am very thankful for the information you have given me. It has given me hope and something to work with. If you don't have any good ideas at the moment I have full understanding of that. I also realize that it's hopeless to support thousands of half broken cameras, so I don't expect assistance. |
Beta Was this translation helpful? Give feedback.
-
|
First hack of random movements and checking For each iteration in its loop it sets Next step for me is to read function |
Beta Was this translation helpful? Give feedback.
-
|
What you're seeing is what I'd expect from the buggy firmware. After a relative movement call, |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
But But I will continue my investigation when I get some more time, I am currently not home anymore. |
Beta Was this translation helpful? Give feedback.
-
|
The ONVIF relative movement command uses a very specific call ( |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I am now starting to understand quite a lot here. I have a reproduction case in a small Python script. I have managed to understand exactly where it goes wrong in Frigate. And finally I also made a simple reproduction case for Pasting the Basically first check that both
Build with: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the confirmation. A summary for future readers of this thread: Buggy Hikvision firmware prevents Frigate's autotracking from working correctly. If autotracking's calibration never progresses past 0%, your Hikvision firmware likely has the bug, as the autotracking FAQ indicates. If you want additional confirmation, you can run the code provided in the comment above. |
Beta Was this translation helpful? Give feedback.
Answer selected by
magma1447
-
|
I made a hack which seems to make auto-tracking work with my camera. The hack/patch contains hard-coded values which I have found by manual work. I see this as a proof of concept and I will keep it running to see if it seems to good enough. I am posting it here as inspiration to others. To make it clear for everyone. This is not something that can be added easily into Frigate. This is definitely not a pull-request, and not a suggestion to the author. Even if it works good enough Frigate would then have to figure out the hard coded values by itself, by looking at the stream and try to figure out how much the camera has moved, with different x/y values given depending on current zoom level. This is my patch. It can be used by a In my case I have updated The Obviously my work could have looked much better. But I don't know Python and I see this as a test and proof of concept. Before I spend more time I would need to know that it works good enough to actually use. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
I have kept trying to patch in an alternative behavior for my camera, and adjusting the math. But, I have also found two new issues with my Hikvision camera. This makes it almost impossible to work with, or maybe even impossible. Three issues in total. I was thinking the devs might want to know about the other Hikvision issues since I have spent quite a few hours on this now.
Showing the zoom value status issue: Next value available requires a z value of In the end I think I will realize that I have just wasted a lot of time and that I will have to buy another camera. This is a 1500 EUR camera though. :( PS! This is just an FYI, I am not expecting any feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the updates. The other issues don't surprise me. It's too bad that the Hikvision firmware devs implementation is subpar. Other users have reported success with newer firmware/newer models, so perhaps they've improved things since releasing your camera. |
Beta Was this translation helpful? Give feedback.
-
I have another that works perfectly fine with a v5.6.x firmware. It came with v5.5 and that one had some weird behavior as well. Next PTZ I will make sure to check the version of available firmwares are, and what year they are from. I am also going to ask my reseller if they have access to other firmwares, but I highly doubt it. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for the confirmation.
A summary for future readers of this thread: Buggy Hikvision firmware prevents Frigate's autotracking from working correctly. If autotracking's calibration never progresses past 0%, your Hikvision firmware likely has the bug, as the autotracking FAQ indicates. If you want additional confirmation, you can run the code provided in the comment above.