Autotracking isn't working when it seems it should #9855
-
I'm having trouble with the auto tracking on this PTZ. While i can successfully connect to onvif for the ptz controls, the autotracking isn't working. config.yml cameras: MainLot_PTZ:
log 2024-02-14 21:44:13.571085154 [INFO] Preparing Frigate... ONVIF TEST Connected to ONVIF camera PTZ configuration options: PTZ service capabilities: PTZ status: |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 15 replies
-
Your camera is reporting an error: What model camera are you using? First thing I would do is to try disabling zooming in your config: |
Beta Was this translation helpful? Give feedback.
-
I've created a PR (#9859) that should correct the issues you're having. |
Beta Was this translation helpful? Give feedback.
-
@hawkeye217 this actually worked. im just a total noob. I was modifying a totally different file for some reason. I can now verify that this commit does fix my ptz auto tracking issue. Also, i am still using the tensorrt image and it's still working. Thank you |
Beta Was this translation helpful? Give feedback.
-
Is there any reason why the ptz camera all of a sudden can't return home (i say "all of a sudden" but now i'm second guessing myself if the preset ever worked)? I can control everything (left, right, up, down and zoom) except for the preset function: 2024-02-20 22:21:43.597017431 [2024-02-20 22:21:43] frigate.comms.dispatcher INFO : Setting ptz command to move_right for ptz all of the above logs show that a function is being called but when it comes to selecting the preset, it doesn't work and doesn't show errors in the logs. I even disabled all the other ptz cameras and simplified the config but still not working. I even reverted back to the original onvif.py (i'm still on ver 3.1): mqtt: logger: #logger: Optional: default log level (default: shown below)default: debugOptional: module by module log level configurationffmpeg: go2rtc: detectors: model: cameras: ptz:
autotracking:
enabled: true
calibrate_on_startup: false
required_zones:- office
return_preset: "1"
timeout: 10
movement_weights: []
It works natively in the camera, it even shows the preset name in frigate UI. Also, when i simplified the config, i also deleted the frigate.db file. I tried to see if there was any activity in the inspection window but i couldn't see any even from the functions that are working. |
Beta Was this translation helpful? Give feedback.
-
I'll show the full logs for good measure: 2024-02-20 22:19:53.884044609 [INFO] Preparing Frigate... |
Beta Was this translation helpful? Give feedback.
Great, glad to hear. The fix is in 0.13.2, which has already been released - so you can update at your convenience.