No frames have been received, check error logs problem in Frigate

[RvdBgithub]

Describe the problem you are having

When frigate start I see this message. "No frames have been...."
When I click on this black screen then 1/2 seconds later I see the stream of the camera..

At the right bottom I see first "System is Healthy"

later it says Fietsenachter is offline

Version

version: 0.14.1

Frigate config file

<mqtt:
  host: 192.168.1.2 #Insert the IP address of your Home Assistant
  port: 1883 #Leave as default 1883 or change to match the port set in yout MQTT Broker configuration
  topic_prefix: frigate
  client_id: frigate
  user: XXXXXXX #Change to match the username set in your MQTT Broker
  password: XXXXXXX #Change to match the password set in your MQTT Broker
  stats_interval: 60

go2rtc:
  streams:
    fietsenachter:
      - rtsp://rtsp:[email protected]:554/av_stream/ch0
      - ffmpeg:fietsenachter#video=h264#hardware


cameras:
  fietsenachter: #Change this tilo a name of the camera that makes sense to you
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac #Insert this if your camera supports audio output
      inputs:
        - path: rtsp://rtsp:[email protected]:554/av_stream/ch0 #Change as per your camera documentation for high quality feed
          roles:
            - record
        - path: rtsp://rtsp:[email protected]:554/av_stream/ch1 #Change as per your camera documentation for low quality feed
          roles:
            - detect
    detect:
      height: 360 #Change this to match the resolution of your detection channel (in this case channel 1)
      width: 640 #Change this to match the resolution of your detection channel (in this case channel 1)
      fps: 10 #This is the frame rate for detection, between 5-10 fps is sufficient.
    record:
      enabled: true
      retain:
        days: 0 #The number of days a recording will be kept for after a motion is detected.
        mode: motion
      events:
        retain:
          default: 30 #The event data will be kept for 1 day. After this period, the event data will be automatically deleted.
          mode: motion
    objects:
      track:
        - person
        - car
version: 0.14>

Relevant Frigate log output

2025-01-09 17:15:04.741287146  [INFO] Preparing Frigate...
2025-01-09 17:15:04.841763516  [INFO] Starting Frigate...
2025-01-09 17:15:13.451301026  [2025-01-09 18:15:13] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2025-01-09 17:15:13.451308249  [2025-01-09 18:15:13] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-01-09 17:15:13.451311133  [2025-01-09 18:15:13] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-01-09 17:15:13.486547081  [2025-01-09 18:15:13] frigate.util.config            INFO    : frigate config does not need migration...
2025-01-09 17:15:13.934109708  [2025-01-09 18:15:13] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2025-01-09 17:15:13.998401743  [2025-01-09 18:15:13] peewee_migrate.logs            INFO    : Starting migrations
2025-01-09 17:15:14.001763453  [2025-01-09 18:15:14] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-01-09 17:15:14.027853284  [2025-01-09 18:15:14] frigate.app                    INFO    : Recording process started: 306
2025-01-09 17:15:14.048382002  [2025-01-09 18:15:14] frigate.app                    INFO    : Recording process started: 307
2025-01-09 17:15:14.062316029  [2025-01-09 18:15:14] frigate.app                    INFO    : go2rtc process pid: 99
2025-01-09 17:15:14.197229466  [2025-01-09 18:15:14] detector.cpu                   INFO    : Starting detection process: 335
2025-01-09 17:15:14.241227031  [2025-01-09 18:15:14] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2025-01-09 17:15:14.325739551  [2025-01-09 18:15:14] frigate.app                    INFO    : Output process started: 337
2025-01-09 17:15:14.495439008  [2025-01-09 18:15:14] frigate.app                    INFO    : Camera processor started for fietsenachter: 352
2025-01-09 17:15:14.495445792  [2025-01-09 18:15:14] frigate.app                    INFO    : Capture process started for fietsenachter: 356
2025-01-09 17:15:14.956753975  [2025-01-09 18:15:14] frigate.video                  ERROR   : fietsenachter: Unable to read frames from ffmpeg process.
2025-01-09 17:15:14.956760900  [2025-01-09 18:15:14] frigate.video                  ERROR   : fietsenachter: ffmpeg process is not running. exiting capture thread...
2025-01-09 17:15:34.925037642  [2025-01-09 18:15:34] watchdog.fietsenachter         ERROR   : Ffmpeg process crashed unexpectedly for fietsenachter.
2025-01-09 17:15:34.925632561  [2025-01-09 18:15:34] watchdog.fietsenachter         ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-01-09 17:15:34.925742688  [2025-01-09 18:15:34] ffmpeg.fietsenachter.detect    ERROR   : [rtsp @ 0x56339dcd1fc0] method DESCRIBE failed: 454 Session Not Found
2025-01-09 17:15:34.925839482  [2025-01-09 18:15:34] ffmpeg.fietsenachter.detect    ERROR   : rtsp://*:*@192.168.1.56:554/av_stream/ch1: Server returned 4XX Client Error, but not one of 40{0,1,3,4}
2025-01-09 17:15:35.077636052  [2025-01-09 18:15:35] frigate.video                  ERROR   : fietsenachter: Unable to read frames from ffmpeg process.
2025-01-09 17:15:35.078689125  [2025-01-09 18:15:35] frigate.video                  ERROR   : fietsenachter: ffmpeg process is not running. exiting capture thread...

Relevant go2rtc log output

2025-01-09 17:15:04.706061773  [INFO] Preparing new go2rtc config...
2025-01-09 17:15:04.980401069  [INFO] Got IP address from supervisor: 192.168.1.2
2025-01-09 17:15:05.197991985  [INFO] Got WebRTC port from supervisor: 8555
2025-01-09 17:15:07.902720079  [INFO] Starting go2rtc...
2025-01-09 17:15:08.643779089  18:15:08.640 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-01-09 17:15:08.643786311  18:15:08.641 INF config path=/dev/shm/go2rtc.yaml
2025-01-09 17:15:08.647344327  18:15:08.644 INF [rtsp] listen addr=:8554
2025-01-09 17:15:08.647350277  18:15:08.644 INF [webrtc] listen addr=:8555/tcp
2025-01-09 17:15:08.647608928  18:15:08.644 INF [api] listen addr=:1984
2025-01-09 17:15:14.754380444  [INFO] Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

docker-compose file or Docker CLI command

I don't know, but I think I don't have this

Object Detector

CPU (no coral)

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

in my configuration.yaml I have also

#ffmpeg ffmpeg:

[hawkeye217]

2025-01-09 17:15:34.925742688  [2025-01-09 18:15:34] ffmpeg.fietsenachter.detect    ERROR   : [rtsp @ 0x56339dcd1fc0] method DESCRIBE failed: 454 Session Not Found
2025-01-09 17:15:34.925839482  [2025-01-09 18:15:34] ffmpeg.fietsenachter.detect    ERROR   : rtsp://*:*@192.168.1.56:554/av_stream/ch1: Server returned 4XX Client Error, but not one of 40{0,1,3,4}

Frigate is having problems connecting to the camera RTSP url you provided.

[RvdBgithub]

Hello Hawkeye217

Thanks for your reply. I found out the following
I bought Sonoff SlimCam gen 2 camera's. And followed this youtube: https://www.youtube.com/watch?v=cRjKu0Y6USY
I think the man uses in this film the gen1 camera maybe? Because at my system I was getting problems.

I found out that the second stream (low quality feed) also the channel must 0 (zero) instead of 1

• path: rtsp://rtsp:[email protected]:554/av_stream/ch0 #Change as per your camera documentation for high quality feed
  roles:
  - record
  - path: rtsp://rtsp:[email protected]:554/av_stream/ch0 #Change as per your camera do quality feed
  roles:
  - detect

[hawkeye217]

Great, glad you were able to figure it out!

[RvdBgithub]

yes, I'm happy to use frigate now!
thanks for your help!