Frigate WebUI showing blank camera views #16810
Unanswered
deathgr1n
asked this question in
Config Support
Replies: 2 comments
-
It looks like I may have found the answer, my config on my amcrest cameras was bad. I changed the configs to the snippet below and all cameras are successfully streaming correctly in Frigate WebUI now. I am going to keep the issue open for a couple days before closing just to see if anyone has any advice for a better Frigate Config. |
Beta Was this translation helpful? Give feedback.
0 replies
-
UPDATE: Still seems to be hit or miss. Turning on dark mode for the WebUI seems to kill some of the feeds but leaving light mode on seems to keep most of the feeds with a static image at least. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
Hello all,

My Frigate WebUI, displaying on a tv using a raspberry pi 4 with Chromium, flickers the camera views for a second and then all but one or two camera views go black/blank (see attached image) but from my desktop PC with any browser or from my laptop with any browser, the views show a static image until motion is detected then shows the live view (like it should, as is my understanding). Same thing if I click on a specific view, from the raspberry pi, it stays blank but if I do it from my desktop or laptop, it shows the live view fine. So I am not sure if I have an incorrect configuration some where? Any help is very appreciated!
Version
0.15.0-cea210d
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
Frigate stats
No response
Operating system
Other Linux
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Using Ubuntu 24.04.2 LTS (Xubuntu)
I also noticed these logs when running chromium-browser from cli to start:
user@host:~ $ chromium-browser http://192.168.1.240:5000/#FrontDoorCam (Front Door Cam is one cam that works the whole time, never goes blank/black)
close object 1: Invalid argument
close object 2: Invalid argument
close object 3: Invalid argument
[2273:13:0225/213741.855161:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
close object 1: Invalid argument
close object 3: Invalid argument
close object 4: Invalid argument
^C[2194:2194:0225/213754.198243:ERROR:wayland_event_watcher.cc(47)] libwayland: warning: queue 0x1c00015380 destroyed while proxies still attached:
[2194:2194:0225/213754.198511:ERROR:wayland_event_watcher.cc(47)] libwayland: wl_shm_pool#45 still attached
user@host:~ $ chromium-browser http://192.168.1.240:5000
close object 1: Invalid argument
close object 2: Invalid argument
close object 3: Invalid argument
[2420:12:0225/213800.680626:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
close object 1: Invalid argument
close object 2: Invalid argument
close object 4: Invalid argument
[2420:12:0225/213802.235690:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
[2420:12:0225/213802.267202:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
[2420:12:0225/213810.033218:ERROR:ffmpeg_common.cc(970)] Unsupported pixel format: -1
Also, here is a screenshot of my camera settings:

Beta Was this translation helpful? Give feedback.
All reactions