Camera's are not showing up in feed,

[Framdark]

I just setup Viewu everything says it is connected and I checked logs of the docker container and it says device is paired, however no video feeds are showing up in any menus in the app. Any help is apricated, thanks!

[mjehrhart]

Okay, let's first check your NVR screen. Do you see data on that page - camera names, go2rtc, and mqtt info? If this page is mostly blank, then there's a config issue. But we can figure that out and get you up and running.

[Framdark]

All I can see is mqtt info such as clientid, host, port etc the rest of it is blank.

[DrSpaldo]

I am not sure if this is related or not. But since one of the recent updates my timeline stopped working, I think I found the issue? see attached:

Looks like a small typo? ;)

[mjehrhart]

Could you help me out a bit more, please? Where's the typo? Did you update the Viewu Server or just the app? I wasn't working on anything with the event timeline yesterday. Maybe take a look at the Viewu Server logs. I wonder if your Viewu Server lost its connection. Only time I've seen this is when my router goes down for a few minutes. If this happens the connection to the MQTT is broken and does not reconnect. Its on my list to look review.

For those who do not know how to check logs, here's a quick guide.

Viewing Docker logs is straightforward and can be done using a few different commands and options depending on your needs. Here are the most common methods:

Viewing Logs for a Specific Container

1. Using docker logs Command:

   • To view the logs of a specific container, use the docker logs command followed by the container ID or name.

     docker logs <container_id_or_name>

   • Example:

     docker logs my_container

2. Real-time Log Streaming:

   • To stream the logs in real-time (similar to tail -f in Unix), use the -f or --follow option.

     docker logs -f <container_id_or_name>

   • Example:

     docker logs -f my_container

3. Viewing Specific Time Range Logs:

   • Use the --since and --until options to view logs within a specific time range.

     docker logs --since="2023-05-01T00:00:00" --until="2023-05-01T01:00:00" <container_id_or_name>

   • Example:

     docker logs --since="2024-05-20T12:00:00" --until="2024-05-20T13:00:00" my_container

Viewing Logs for All Containers

1. Using docker-compose logs:

   • If you are using Docker Compose, you can view logs for all services defined in the docker-compose.yml file.

     docker-compose logs

   • To stream logs in real-time:

     docker-compose logs -f

2. Using docker logs with --tail Option:

   • To view the last few lines of logs from a container, use the --tail option.

     docker logs --tail 100 <container_id_or_name>

   • Example:

     docker logs --tail 50 my_container

Filtering Logs

1. Using grep for Filtering:
   • You can pipe the docker logs output to grep to filter specific keywords.

     docker logs <container_id_or_name> | grep "keyword"

   • Example:

     docker logs my_container | grep "error"

Using Docker Desktop or Other GUI Tools

1. Docker Desktop:

   • If you are using Docker Desktop, you can view logs directly from the GUI by selecting the container and navigating to the logs tab.

2. Other GUI Tools:

   • Tools like Portainer, Rancher, and other Docker management GUIs also provide easy access to container logs.

Summary of Common Commands

# View logs of a container
docker logs <container_id_or_name>

# Stream logs in real-time
docker logs -f <container_id_or_name>

# View logs within a specific time range
docker logs --since="2024-05-20T12:00:00" --until="2024-05-20T13:00:00" <container_id_or_name>

# View the last 100 lines of logs
docker logs --tail 100 <container_id_or_name>

# View logs for all services in a docker-compose setup
docker-compose logs

# Stream logs in real-time for docker-compose
docker-compose logs -f

# Filter logs for a specific keyword
docker logs <container_id_or_name> | grep "keyword"

These commands should help you effectively manage and troubleshoot your Docker containers by providing access to their logs. For more detailed information, you can refer to the official Docker documentation.

[mjehrhart]

@Framdark could you post your frigate config file here or dm with it. I wrote the app with my config file in hand as thats the only one I had available to me. There are a lot of one-offs in setting this up. So I'm probably missing a key value pair that your config expects to have in it.

[Framdark]

okay ill send it here I just need to remove the password from stuff

mqtt:
  enabled: true
  host: 192.168.1.1xx
  port: 1883
  user: mqtt
  password: xxx

birdseye:

  enabled: true
  mode: continuous
  restream: false

go2rtc:
  streams:
    garage:
    - rtsp://admin:xxx@192.168.1.1xx:554/cam/realmonitor?channel=1&subtype=00
    - ffmpeg:garage#audio=opus
    # doorbell:
    # - ffmpeg:http://192.168.1.1xx/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=xxx#video=copy#audio=copy#audio=opus
    # - rtsp://admin:xxx@192.168.1.1xx/Preview_01_sub
    garagesub:
    - rtsp://admin:xxx@192.168.1.1xx:554/cam/realmonitor?channel=1&subtype=02
    - ffmpeg:garagesub#audio=opus
    # doorbellsub:
    # - ffmpeg:http://192.168.1.xxx/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=xxx
    northeastside:
    - rtsp://admin:xxx@192.168.1.1xx:554/cam/realmonitor?channel=1&subtype=00
    - ffmpeg:northeastside#audio=opus
    northeastsidesub:
    - rtsp://admin:xxx@192.168.1.1xx:554/cam/realmonitor?channel=1&subtype=02
    - ffmpeg:northeastsidesub#audio=opus
    eastside:
    - rtsp://admin:xxx@192.168.1.1xx:554/cam/realmonitor?channel=1&subtype=00
    - ffmpeg:eastside#audio=opus
    eastsidesub:
    - rtsp://admin:xxx@192.168.1.1xx:554/cam/realmonitor?channel=1&subtype=02
    - ffmpeg:eastsidesub#audio=opus

  webrtc:
    listen: 192.168.1.1xx:8555
    candidates:
    - 192.168.1.1xx:8555
ffmpeg:
  hwaccel_args: preset-vaapi
  output_args:
    record: preset-record-generic-audio-copy
  input_args: preset-rtsp-restream
cameras:
  garage: 
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/garage
        input_args: preset-rtsp-restream
        roles:
        - audio
        - record
    record:
      enabled: true
      retain:
        days: 14 
        mode: all
    detect:
      enabled: false
  garagesub:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/garagesub
        roles:
        - detect
        - record
    birdseye:
      enabled: false
    detect:
      enabled: true
    objects:
      track:
      - person
    record:
      enabled: true
      retain:
        days: 0
        mode: all
      events:
        retain:
          default: 1.5
          mode: motion
  northeastside:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/northeastside
        input_args: preset-rtsp-restream
        roles:
        - audio
        - record
    record:
      enabled: true
      retain:
        days: 14 
        mode: all
    detect:
      enabled: false
  northeastsidesub:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/northeastsidesub
        roles:
        - detect
        - record
    birdseye:
      enabled: false
    detect:
      enabled: true
    objects:
      track:
      - person
      filters:
        person:
          mask:
          - 255,560,241,631
    record:
      enabled: true
      retain:
        days: 0
        mode: all
      events:
        retain:
          default: 1.5
          mode: motion
  eastside:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/eastside
        input_args: preset-rtsp-restream
        roles:
        - audio
        - record
    record:
      enabled: true
      retain:
        days: 14 # <- number of days to keep continuous recordings
        mode: all
    detect:
      enabled: false
  eastsidesub:
    enabled: true
    ffmpeg:
      inputs:
      - path: rtsp://127.0.0.1:8554/eastsidesub
        roles:
        - detect
        - record
    birdseye:
      enabled: false
    detect:
      enabled: true
    motion:
      mask:
      - 0,0,0,167,1118,445,1159,0
      - 887,616,881,640,881,663,888,720,850,720,797,720,739,720,680,720,634,720,594,720,568,720,498,677,457,647,574,613,582,582,591,552,596,530,614,505,692,526,734,531,750,513,775,505,857,528
    objects:
      filters:
        person:
          mask:
          - 486,720,503,652,522,609,567,563,595,523,623,484,712,506,792,507,843,512,894,556,904,635,890,693,805,720,757,720
          - 0,720,0,696,0,676,0,646,0,580,0,542,22,501,80,487,126,484,197,497,242,515,281,537,290,605,295,671,291,720
    record:
      enabled: true
      retain:
        days: 0
        mode: all
      events:
        retain:
          default: 1.5
          mode: motion

detectors: 
  coral:
    type: edgetpu
    device: usb
telemetry:
  stats:
    intel_gpu_stats: true

[Framdark]

thank you I had no idea how to do that

[mjehrhart]

I edited your post to allow text formatting. To format you need three ``` above and below the text

thanks for posting the config.

[Framdark]

No problem thanks for explaining how to format it

[mjehrhart]

are you beta testing 0.14?

[Framdark]

no I am using 0.13.2

[Framdark]

The one thing I think it might be is because I was testing it out before I set up reverse proxy so it is currently set on my local ip addr do you think that would change anything?

[DrSpaldo]

@mjehrhart I’m not sure if you want to split my post out? It may not be related. In the mqtt topic it looks like it’s looking for frigagte instead of frigate?

[mjehrhart]

I found the issue. Viewu expects a whole number for default. I didn't realized a user could put in a decimal for the value.

"retain": {
            "default": 1.5,
            "mode": "motion",
            "objects": {}
          }

Will you change the default value to a whole number like 1 or 2 and restart Frigate. You have three areas in your config where this needs to be changed. I will look at fixing it on my end as well so you can revert back to decimal.

[mjehrhart]

@DrSpaldo thanks for finding the typo. I fixed it but that wouldn't have an impact on the event timeline. That text was only displayed on the settings page.

[DrSpaldo]

No probs, I’ll look at what’s happening with my settings

[Framdark]

That fixed it, but I am not able to use the go2rtc option because it gives me a black screen but when I use rtsp it works. I'd rather not use rtsp because then it shows the passwords to my cameras in plain text so could you help me fix that please

[Framdark]

I fixed it didn't like the ip addr being localhost

[mjehrhart]

You can turn off displaying of the url by toggling Developer Mode in the settings page. What is the url for the go2rtc? This is a new feature that went into the app recently, so I may need to work on it some more.

[mjehrhart]

Thats what I thought the issue would be. Good find.

[mjehrhart]

I also fixed the issue and changed the accepted value from Int to Float. But I need to test it more before adding it to a build release.

[mjehrhart]

I'm closing this issue, if you feel I shouldn't have please open a new issue.

[Framdark]

You can turn off displaying of the url by toggling Developer Mode in the settings page. What is the url for the go2rtc? This is a new feature that went into the app recently, so I may need to work on it some more.

it just says the local ip address so in the case of mine 192.168.1.1xx then the name of camera instead of it being the entire long name of the camera which includes the username and password like in rtsp version

[mjehrhart]

Can you post an screenshot? I think without seeing anything, thats how its supposed to be.

[Framdark]

I edited this post to shrink the images down some.

[Framdark]

Top one is go2rtc bottom one is rtsp. The difference is the bottom one includes password and other info where as go2rtc one doesn’t. If there was some way to make it not show whole link that could fix problem but as of now if someone isn’t using go2rtc every time they look at camera feed it’ll show them password and username

[mjehrhart]

I'm not totally following. Is the issue that the url display the password and text? or is it not displaying the camera feed?

The url can be turned off by turning off Developer Mode.

Let me know and we'll figure this out.

[Framdark]

Oh nevermind then. If you can turn it off in developer mode then it doesn’t matter sorry about that!

[mjehrhart]

Anytime. The Developer Mode is to aid in installation setup and testing. Thats all. You can turn it off whenever you like.