[Bug]: upgraded to v0.14Beta now Camera Live View Not Working

[jeremy-betts]

Describe the problem you are having

After upgrading from v0.13.2 to v0.14.Beta2 the live view for cameras does not work. All other camera views work.

In the chrome console I get the following error:
WebSocket connection to 'ws://192.168.100.29:5000/live/mse/api/ws?src=backyard' failed: WebSocket is closed before the connection is established.
(anonymous) @ BirdseyeLivePlayer-C2UwuJJ6.js:12

Steps to reproduce

From the main Frigate screen click a camera preview. The video fails to load for the individual camera.

Version

v0.14.Beta2

Frigate config file

logger:
  # Optional: default log level (default: shown below)
  default: debug
  # Optional: module by module log level configuration
  logs:
    frigate.mqtt: debug
mqtt:
  enabled: true
  host: 192.168.100.29 # <---- same mqtt broker that home assistant uses
  user: ha
  password: b00bi3s
  port: 1883
  topic_prefix: frigate

go2rtc:
  streams:
    back_hill:
      - rtsp://admin:@192.168.100.203:80/ch0_0.264
    back_hill_sub:
      - rtsp://admin:@192.168.100.203:80/ch0_1.264
    backyard:
      - rtsp://admin:@192.168.100.201:80/ch0_0.264
    backyard_sub:
      - rtsp://admin:@192.168.100.201:80/ch0_1.264
    chicken_run:
      - rtsp://admin:[email protected]:554/11
    chicken_run_sub:
      - rtsp://admin:[email protected]:554/12
record:
  enabled: true
  expire_interval: 60
  retain:
    days: 3
    mode: all
  events:
    pre_capture: 3
    post_capture: 5
    retain:
      default: 14
      mode: active_objects

snapshots:
  enabled: true
  clean_copy: true
  timestamp: true
  bounding_box: true

cameras:
  backyard: # <--- this will be changed to your actual camera later
    enabled: true
    motion:
      threshold: 30
      mask: 
        0.349,0.31,0.246,0.407,0.183,0.293,0.179,0.11,0.204,0.001,0.996,0.003,0.993,0.216,0.904,0.198,0.82,0.341,0.717,0.25,0.554,0.289
    record:
      enabled: true
      events:
        retain:
          default: 10
    ffmpeg:
      hwaccel_args: preset-jetson-h264
      inputs:
        - path: rtsp://127.0.0.1:8554/backyard
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/backyard_sub
          input_args: preset-rtsp-restream
          roles:
            - detect

    zones:
      zone_0:
        coordinates: 241,177,239,124,336,119,351,169
    detect:
      stationary:
        interval: 100
        threshold: 25
    objects:
      filters:
        car: {}
        bear: {}
  back_hill: # <--- this will be changed to your actual camera later
    enabled: true
    motion:
      threshold: 20
    record:
      enabled: true
      events:
        retain:
          default: 10
    ffmpeg:
      hwaccel_args: preset-jetson-h264
      inputs:
        - path: rtsp://127.0.0.1:8554/back_hill
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/back_hill_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      stationary:
        interval: 100
        threshold: 25
    objects:
      filters:
        car:
          mask:
            - 414,127,461,186

  chicken_run: # <--- this will be changed to your actual camera later
    enabled: true
    motion:
      threshold: 30
    record:
      enabled: true
      events:
        retain:
          default: 10
    ffmpeg:
      hwaccel_args: preset-jetson-h264
      inputs:
        - path: rtsp://127.0.0.1:8554/chicken_run
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/chicken_run_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
    detect:
      stationary:
        interval: 100
        threshold: 25
detectors:
  tensorrt:
    type: tensorrt
    device: 0 #This is the default, select the first GPU
detect:
  fps: 2
  enabled: true
  max_disappeared: 25
objects:
  track:
    - person
    - car
    - motorcycle
    - bird
    - cat
    - dog
    - horse
    - sheep
    - cow
    - bear
    - zebra

model:
  path: /config/model_cache/tensorrt/yolov7-tiny-416.trt
  input_tensor: nchw
  input_pixel_format: rgb
  width: 416
  height: 416

birdseye:
  enabled: true
  mode: continuous

version: 0.14
camera_groups: {}

Relevant log output

No relevant logs on the server

Operating system

Debian

Install method

Docker Compose

Network connection

Wired

Camera make and model

Various

Any other information that may be helpful

No response

[NickM-27]

this has already been fixed in the latest commits

[Redsandro]

this has already been fixed in the latest commits

@NickM-27 Are those commits part of the next beta v0.14.Beta3? Because I'm having the same problem in Beta3.

Interestingly, in Firefox, with a broken live view, if you navigate to a random page like about:config, and then press back, the live view starts working.

[hawkeye217]

No, beta 3 does not have these fixes. Beta 4 will.

[Redsandro]

@hawkeye217 great, thank you! You replied so fast I fell off my chair from the sonic boom.

[hawkeye217]

@NickM-27 is usually faster than me 😂

[jeremy-betts]

Any idea when beta4 will be ready?

…

On Mon, Jul 1, 2024 at 7:12 PM Josh Hawkins ***@***.***> wrote: @NickM-27 <https://github.com/NickM-27> is usually faster than me 😂 — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527P3VPGCZ4JBIPGYO73ZKHWAXAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZQGYZTS> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

When it's ready :)

You can always run dev builds in the meantime if you're feeling more adventurous.

[jeremy-betts]

I'm running on a docker container on a jetson nano. Is there a way to run dev?

…

On Tue, Jul 2, 2024 at 9:54 AM Josh Hawkins ***@***.***> wrote: When it's ready :) You can always run dev builds in the meantime if you're feeling more adventurous. — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527O4AYSSO45X4VHCFYTZKK5LTAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZXHE3TC> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[NickM-27]

just change the image to a dev image

[jeremy-betts]

Setting my docker image to ghcr.io/blakeblackshear/frigate:dev-tensorrt-jp4 doesn't work

…

On Tue, Jul 2, 2024 at 10:18 AM Nicolas Mowen ***@***.***> wrote: just change the image to a dev image — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527POWDD2LELK43XMKATZKLACTAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZYGI4TQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

That's not a valid tag. You can find the latest dev builds here: https://github.com/blakeblackshear/frigate/pkgs/container/frigate

[jeremy-betts]

OK I was able to run the dev image but still had the same issue with Live View. When I click on a specific camera it just goes to the loading spinner. Nothing in the chrome console or in the frigate logs. Tried with dev-012aa63-tensorrt-jp4 and dev-fe9a3c9-tensorrt-jp4

…

On Tue, Jul 2, 2024 at 10:50 AM Josh Hawkins ***@***.***> wrote: That's not a valid tag. You can find the latest dev builds here: https://github.com/blakeblackshear/frigate/pkgs/container/frigate — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527PKZKXXF5RAYE5RMQDZKLD5PAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZYGY3DS> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

012aa63 was not a good build, but fe9a3c9 should be.

The most recent frigate live view code uses MSE first, then falls back to jsmpeg if MSE can't connect. Since you're running via docker compose, could you try mapping port 1984 and trying to stream the cameras from the go2rtc UI?

[hawkeye217]

Also, it would be good to see the browser's developer tools network tab

[jeremy-betts]

I tried mapping port 1984 but I get connection refused when trying to open go2rtc UI Here is chrome network log [image: image.png]

…

On Tue, Jul 2, 2024 at 12:28 PM Josh Hawkins ***@***.***> wrote: Also, it would be good to see the browser's developer tools network tab — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527M6UFZ6XBNI6CIF7BTZKLPM5AVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZZGU3TQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

You'll have to post the image to the discussion on the web - Github doesn't know how to deal with email attachments.

[jeremy-betts]

[hawkeye217]

Thanks. The 2nd to the last item on the list there, ws?src=backyard is a websocket connection back to Frigate for your live stream of the backyard camera. It hasn't transferred any data (as indicated by 0 B in the far right column), which is why the loading spinner never disappears.

Do you have any Chrome extensions installed and running? Could you try loading the Frigate UI in incognito mode? Could you try another browser besides Chrome?

[jeremy-betts]

No changes using incognito mode or firefox

…

On Tue, Jul 2, 2024 at 2:24 PM Josh Hawkins ***@***.***> wrote: Thanks. The 2nd to the last item on the list there, ws?src=backyard is a websocket connection back to Frigate for your live stream of the backyard camera. It hasn't transferred any data (as indicated by 0 B in the far right column), which is why the loading spinner never disappears. Do you have any Chrome extensions installed and running? Could you try loading the Frigate UI in incognito mode? Could you try another browser besides Chrome? — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527JDAKV6QVAB434JG7LZKL46HAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBQGUYTI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

Do you have any unique network conditions or are you using a VPN to access Frigate?

[hawkeye217]

When you click on ws or ws?src=backyard from the devtools network pane, do you see any data being transferred?

[hawkeye217]

Also, what's your docker compose?

[jeremy-betts]

I use tailscale to remotely access the Home Assistant UI but I am currently on the same local network.

…

On Tue, Jul 2, 2024 at 2:46 PM Josh Hawkins ***@***.***> wrote: Do you have any unique network conditions or are you using a VPN to access Frigate? It seems like the main Frigate websocket (ws in the network screenshot) isn't receiving data either. — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527NDDB5E4SXBG6OTF6DZKL7RBAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBQGY2TO> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[jeremy-betts]

Yes it appears data is being transferred

Docker compose:
version: "3.9"
services:
frigate:
container_name: frigate
#network_mode: host
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:dev-fe9a3c9-tensorrt-jp4
runtime: nvidia # Add this
volumes:
- ./config:/config
- ./storage:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
environment:
- YOLO_MODELS=yolov7x-320
ports:
- "1984:1984"
- "5000:5000"
- "8080:8080"
- "8554:8554" # RTSP feeds

[hawkeye217]

Thanks.

What's the resolution of your main streams on either the backyard or back_hill cameras?

[jeremy-betts]

I have three cameras two are 1280x960 one is 1920x1080 They all show the same issue

…

On Tue, Jul 2, 2024 at 3:04 PM Josh Hawkins ***@***.***> wrote: Thanks. What's the resolution of your main streams on either the backyard or back_hill cameras? — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527OD2BGXKUOW5CHCCZDZKMBWPAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBQG44TI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

I've put up this PR to see if it helps with your issue: #12271

Once it's merged, pull the dev build and test it for me.

[jeremy-betts]

From my iphone/firefox the live view loads if I pinch to zoom. I tried double clicking from my desktop chrome and the loading spinner zooms but the camera view does not load. On Tue, Jul 2, 2024 at 3:20 PM Jeremy Betts ***@***.***> wrote:

…

I have three cameras two are 1280x960 one is 1920x1080 They all show the same issue On Tue, Jul 2, 2024 at 3:04 PM Josh Hawkins ***@***.***> wrote: > Thanks. > > What's the resolution of your main streams on either the backyard or > back_hill cameras? > > — > Reply to this email directly, view it on GitHub > <#12047 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGJ527OD2BGXKUOW5CHCCZDZKMBWPAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBQG44TI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> >

[Redsandro]

I can confirm dev-be9e606 is working correctly on my env.

[jeremy-betts]

Just loaded docker image

Now I get a picture from the camera but there is no video stream just the static picture

[hawkeye217]

If you right-click on the camera in single cam live view, does your menu pop up with video-related items? For example, do you see "Show All Controls" or "Save Video Frame As..."?

[jeremy-betts]

Sorry I loaded docker image dev-784b701-tensorrt-jp4

[jeremy-betts]

Yes

…

On Wed, Jul 3, 2024 at 8:20 AM Josh Hawkins ***@***.***> wrote: If you right-click on the camera in single cam live view, does your menu pop up with video-related items? For example, do you see "Show All Controls" or "Save Video Frame As..."? — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527MLDGITIPJIO3K4AYDZKP3BZAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBYGIZTG> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

But the video is not playing?

[jeremy-betts]

Right, the video is not playing.

…

On Wed, Jul 3, 2024 at 8:23 AM Josh Hawkins ***@***.***> wrote: But the video is not playing? — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527LSBSC4XXLP3ZARIB3ZKP3ORAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBYGI3TG> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

Okay. From what I can see, there's nothing in Frigate's code that is preventing the video from playing at this point. If the websocket data is flowing (as seen in the dev tools network pane), my best guess is that the issue is likely the actual video data that being sent from your camera. I've only ever seen this before on Mac Safari with a cheap doorbell camera - where the camera's video codec is not playable in the browser player. However in that case, the player actually fires a decode error, which Frigate is able to catch and switch the player type.

There are a few possible options for your case:

1. Don't use go2rtc for restreaming. Frigate will default to its internal live view type, which uses less bandwidth and is more compatible.

2. Continue to use go2rtc, but change the stream names to not match your camera names, and just specify the correct URLs in the path directive for your cameras. For example, if you change the go2rtc stream backyard to backyard_restream, change your path to: - path: rtsp://127.0.0.1:8554/backyard_restream

[hawkeye217]

Something else you could try: continue to use go2rtc, but set the sources to use ffmpeg. For example:

go2rtc:
  streams:
    back_hill:
      - ffmpeg:rtsp://admin:@192.168.100.203:80/ch0_0.264
    back_hill_sub:
      - rtsp://admin:@192.168.100.203:80/ch0_1.264
    backyard:
      - ffmpeg:rtsp://admin:@192.168.100.201:80/ch0_0.264
    backyard_sub:
      - rtsp://admin:@192.168.100.201:80/ch0_1.264
    chicken_run:
      - ffmpeg:rtsp://admin:[email protected]:554/11
    chicken_run_sub:
      - rtsp://admin:[email protected]:554/12

[hawkeye217]

There's something else that would be helpful to see before you make any changes. In the browser dev tools network tab, when you click on the ws?src=<camera name>, can you scroll to the very top of the messages tab and send a screenshot of the lines there? For example:

[jeremy-betts]

[hawkeye217]

Thanks. Can you try changing the audio output on your camera to AAC and testing live view again?

[jeremy-betts]

I don't think these cameras do audio. I can't find any audio parameters on the camera UI

…

On Wed, Jul 3, 2024 at 10:37 AM Josh Hawkins ***@***.***> wrote: Thanks. Can you try changing the audio output on your camera to AAC and testing live view again? — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527JU2BFOQ7RNUR6IZGLZKQLD5AVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNBZHEZDQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

That may explain it. The camera is telling frigate that FLAC audio is being sent and should be decoded in the stream.

[jeremy-betts]

These are cheap cameras but have always been pretty reliable for video. Anyway to disable the audio on the frigate side?

…

On Wed, Jul 3, 2024 at 10:47 AM Josh Hawkins ***@***.***> wrote: That may explain it. The camera is telling frigate that FLAC audio is being sent and should be decoded in the stream. — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527IQG5I7TDJHOYXDKT3ZKQMJ3AVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNJQGA3DG> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

Try what I specified earlier for your go2rtc section in your config:

go2rtc:
  streams:
    back_hill:
      - ffmpeg:rtsp://admin:@192.168.100.203:80/ch0_0.264#video=copy
    back_hill_sub:
      - rtsp://admin:@192.168.100.203:80/ch0_1.264
    backyard:
      - ffmpeg:rtsp://admin:@192.168.100.201:80/ch0_0.264#video=copy
    backyard_sub:
      - rtsp://admin:@192.168.100.201:80/ch0_1.264
    chicken_run:
      - ffmpeg:rtsp://admin:[email protected]:554/11#video=copy
    chicken_run_sub:
      - rtsp://admin:[email protected]:554/12

[NickM-27]

To make sure, I'd suggest "ffmpeg:rtsp://...#video=copy"

[hawkeye217]

Ah yes. We only want video copied, not audio.

[jeremy-betts]

My live view is now working with the go2rtc streams specified as instructed, thank you!

…

On Wed, Jul 3, 2024 at 11:05 AM Josh Hawkins ***@***.***> wrote: Ah yes. We only want video copied, not audio. — Reply to this email directly, view it on GitHub <#12047 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJ527K2HBIN6Z7LZGAFJBDZKQOLBAVCNFSM6AAAAABJQUM326VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNJQGI2DQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

Great! Happy to help.