Questions and feedback regarding Frigate 0.16 Beta 2

[milosivanovic]

I decided to upgrade from 0.15 stable to 0.16 Beta 2 to test it out and I noticed a few things and have a few questions.

My instance of Frigate runs on an Intel(R) Core(TM) i3-N305 and it also uses a Google Coral TPU via USB for detection.

1. ONVIF, which worked fine in 0.15 now results in "Unable to get Onvif media profiles for camera: : Sender not Authorized" showing in the logs when I open the camera's live view in Frigate (where the PTZ control bar would then show, which no longer does) despite me not making any changes to the 0.15 config file. Does something extra need to be done to make this work in 0.16 Beta 2?
2. I'm suddenly getting a couch detected as a person 24/7 (immediately on startup and forever after that) which never happend in 0.15. I also got a plant identified as a person after a car drove by and triggered motion, which has not happened before either in 0.15 in many weeks of use. I compared the sha256sum of the edgetpu_model.tflite and it's identical on both versions which I assume means that object detection quality shouldn't have changed between these two versions, but it has. Why is that, and is it possible for me to go back to the previous object detection because that one performed better?
3. If I want to try one of the supported YOLO models, would I be able to do that with a Coral TPU and if not, would I be able to do it with my i3-N305 iGPU, and if so, how can I configure this?
4. I noticed that the live streaming experience on 0.16 Beta 2 is objectively better in the sense that the bitrate is appropriately lowered so video now loads very quickly. I didn't see these bitrate changes described in the release notes so I'm just wondering what specifically changed regarding the ffmpeg ingestion. And, since the live streaming experience is so much better due to the lowered bitrate, I'm wondering if it's possible to apply these same changes when viewing recordings as well? In any version of Frigate, including 0.16 Beta 2, viewing recordings simply entails sending the original high bitrate files (2Mbps per camera in my case) and that takes quite a while to load and scrub through, especially when viewing internationally or on a mobile connection. It would be great to be able to stream recordings at the same bitrate as the live stream if the system is performant enough to do transcoding or whatever Frigate is now doing to the live stream to make the experience that much better.

Just as a note, I am aware of Frigate+ but the point of Frigate for me is that it's open-source and fully local; I'm not willing to connect/integrate/send any data/images/video anywhere, even for training. If I wanted that I would sign up to Google Nest. I would be open to paying to download a better model (without connecting or sending anything else), but that doesn't seem to be something Frigate is offering.

If there's a better place to ask these questions, please let me know.

[hawkeye217]

1. ONVIF, which worked fine in 0.15 now results in "Unable to get Onvif media profiles for camera: : Sender not Authorized" showing in the logs

The ONVIF package was updated for 0.16. ONVIF auth issues sometimes have to do with a time mismatch on the camera and the host. You can try setting ignore_time_mismatch: true under your onvif config.

2. I'm suddenly getting a couch detected as a person 24/7 (immediately on startup and forever after that) which never happend in 0.15.... Why is that, and is it possible for me to go back to the previous object detection because that one performed better?

There were plenty of tweaks in 0.16 that affect object detection. If something is falsely detected as a person, you can use a number of ways to prevent this: Object filters and/or an object mask.

3. If I want to try one of the supported YOLO models, would I be able to do that with a Coral TPU and if not, would I be able to do it with my i3-N305 iGPU, and if so, how can I configure this?

No, the Coral TPU can only run mobiledet models. You can try using the OpenVINO detector.

4. I noticed that the live streaming experience on 0.16 Beta 2 is objectively better in the sense that the bitrate is appropriately lowered so video now loads very quickly. I didn't see these bitrate changes described in the release notes so I'm just wondering what specifically changed regarding the ffmpeg ingestion. And, since the live streaming experience is so much better due to the lowered bitrate, I'm wondering if it's possible to apply these same changes when viewing recordings as well?

There were no bitrate changes for ffmpeg in 0.16, but perhaps other changes made your live view more responsive. Frigate's recordings use a completely different player than the live player. There is an open feature request to record a camera's sub stream along with the main stream, which would help your use case: #2082

Just as a note, I am aware of Frigate+ but the point of Frigate for me is that it's open-source and fully local; I'm not willing to connect/integrate/send any data/images/video anywhere, even for training. If I wanted that I would sign up to Google Nest. I would be open to paying to download a better model (without connecting or sending anything else), but that doesn't seem to be something Frigate is offering.

Frigate+ base models are now available with a Frigate+ subscription where no uploading of your own images are required. When you subscribe, you have the ability to download a base model and use that right away.

[milosivanovic]

I appreciate all the answers. Regarding ONVIF, I added ignore_time_mismatch: true but I'm still seeing the same error. Is there a way to debug what's being sent and/or received to see if the username and password are being sent correctly to the cameras?

[hawkeye217]

You could try enabling ONVIF debug logs:

logger:
  default: info
  logs:
    frigate.ptz.onvif: debug

You could also try temporarily changing your password to something simple.

[milosivanovic]

@hawkeye217 I enabled debug logs but it's not showing much. This is tested with 0.16 Beta 3. The password is already simple.

2025-06-03 20:29:04.105501443  [2025-06-03 20:29:04] frigate.ptz.onvif              INFO    : Attempting ONVIF initialization for front_right (retry 1/5)
2025-06-03 20:29:04.313881722  [2025-06-03 20:29:04] frigate.ptz.onvif              DEBUG   : Onvif media xaddr for front_right: http://192.168.2.75/onvif/media_service
2025-06-03 20:29:04.315874934  [2025-06-03 20:29:04] frigate.ptz.onvif              DEBUG   : Onvif capabilities for front_right: ('http://192.168.2.75/onvif/ptz_service', '/usr/local/lib/python3.11/dist-packages/onvif/wsdl/ptz.wsdl', '{http://www.onvif.org/ver20/ptz/wsdl}PTZBinding')
2025-06-03 20:29:04.331430791  [2025-06-03 20:29:04] frigate.ptz.onvif              ERROR   : Unable to get Onvif media profiles for camera: front_right: Sender not Authorized
2025-06-03 20:29:04.331758096  [2025-06-03 20:29:04] frigate.ptz.onvif              WARNING : ONVIF initialization failed for front_right
2025-06-03 20:29:04.332694077  [2025-06-03 20:29:04] frigate.ptz.onvif              DEBUG   : Could not initialize ONVIF for front_right

[hawkeye217]

Not sure what else to recommend, then. Authorization issues are normally a result of either special characters in the password, time mismatches between the host and camera, basic vs digest auth, or just mistyped credentials.