frigate: [Support]: Frigate errors and unable to stream to tv in automations

Describe the problem you are having

I am having trouble with my docker container running frigate, I have the ability to manually stream a camera to a tv but when trying to do so in a automation is will say the camera won’t allow streaming or something similar. I also have errors showing in the logs of the docker container and HA itself regarding the issue with communications between hubs. Any Help will be much appreciated. I trying to learn and hope I am getting better. I promise not to break it again if you can fix this for me please

Version

0.13.1-34FB1C2

Frigate config file

mqtt:
  # Optional: Enable mqtt server (default: shown below)
  enabled: true
  # Required: host name
  host: MQTTLocalip
  # Optional: port (default: shown below)
  port: 1883
  # Optional: topic prefix (default: shown below)
  # NOTE: must be unique if you are running multiple instances
  topic_prefix: frigate
  # Optional: client id (default: shown below)
  # NOTE: must be unique if you are running multiple instances
  client_id: frigate
  # Optional: user
  # NOTE: MQTT user can be specified with an environment variable or docker secrets that must begin with 'FRIGATE_'.
  #       e.g. user: '{FRIGATE_MQTT_USER}'
  user: mqtt_user
  # Optional: password
  # NOTE: MQTT password can be specified with an environment variable or docker secrets that must begin with 'FRIGATE_'.
  #       e.g. password: '{FRIGATE_MQTT_PASSWORD}'
  password: password
  stats_interval: 60

# Optional: Detectors configuration. Defaults to a single CPU detector
detectors:
  coral:
    type: edgetpu
    device: usb

# Optional: Database configuration
database:
  # The path to store the SQLite DB (default: shown below)
  path: /config/frigate.db

# Optional: Audio Events Configuration
# NOTE: Can be overridden at the camera level
audio:
  # Optional: Enable audio events (default: shown below)
  enabled: false
  # Optional: Configure the amount of seconds without detected audio to end the event (default: shown below)
  max_not_heard: 30
  # Optional: Configure the min rms volume required to run audio detection (default: shown below)
  # As a rule of thumb:
  #  - 200 - high sensitivity
  #  - 500 - medium sensitivity
  #  - 1000 - low sensitivity
  min_volume: 500
  # Optional: Types of audio to listen for (default: shown below)
  listen:
  - bark
  - fire_alarm
  - scream
  - speech
  - yell
  # Optional: Filters to configure detection.
  filters:
    # Label that matches label in listen config.
    speech:
      # Minimum score that triggers an audio event (default: shown below)
      threshold: 0.8

# Optional: logger verbosity settings
logger:
  # Optional: Default log verbosity (default: shown below)
  default: info
  # Optional: Component specific logger overrides
  logs:
    frigate.event: debug

# Optional: set environment variables
environment_vars:
  EXAMPLE_VAR: value

# Optional: birdseye configuration
# NOTE: Can (enabled, mode) be overridden at the camera level
birdseye:
  # Optional: Enable birdseye view (default: shown below)
  enabled: true
  # Optional: Restream birdseye via RTSP (default: shown below)
  # NOTE: Enabling this will set birdseye to run 24/7 which may increase CPU usage somewhat.
  restream: false
  # Optional: Width of the output resolution (default: shown below)
  width: 1280
  # Optional: Height of the output resolution (default: shown below)
  height: 720
  # Optional: Encoding quality of the mpeg1 feed (default: shown below)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 8
  # Optional: Mode of the view. Available options are: objects, motion, and continuous
  #   objects - cameras are included if they have had a tracked object within the last 30 seconds
  #   motion - cameras are included if motion was detected in the last 30 seconds
  #   continuous - all cameras are included always
  mode: objects
  # Optional: Threshold for camera activity to stop showing camera (default: shown below)
  # Optional: Configure the birdseye layout

# Optional: ffmpeg configuration
# More information about presets at https://docs.frigate.video/configuration/ffmpeg_presets
ffmpeg:
  # Optional: global ffmpeg args (default: shown below)
  global_args: -hide_banner -loglevel warning -threads 2
  # Optional: global hwaccel args (default: shown below)
  # NOTE: See hardware acceleration docs for your specific device
  hwaccel_args: preset-vaapi
  # Optional: global input args (default: shown below)
  input_args: preset-rtsp-generic
  # Optional: global output args
  output_args:
    # Optional: output args for detect streams (default: shown below)
    detect: -threads 2 -f rawvideo -pix_fmt yuv420p
    # Optional: output args for record streams (default: shown below)
    record: preset-record-generic
    # Optional: output args for rtmp streams (default: shown below)
    rtmp: preset-rtmp-generic
  # Optional: Time in seconds to wait before ffmpeg retries connecting to the camera. (default: shown below)
  # If set too low, frigate will retry a connection to the camera's stream too frequently, using up the limited streams some cameras can allow at once
  # If set too high, then if a ffmpeg crash or camera stream timeout occurs, you could potentially lose up to a maximum of retry_interval second(s) of footage
  # NOTE: this can be a useful setting for Wireless / Battery cameras to reduce how much footage is potentially lost during a connection timeout.
  retry_interval: 10

# Optional: Detect configuration
# NOTE: Can be overridden at the camera level
detect:
  # Optional: width of the frame for the input with the detect role (default: use native stream resolution)
  width: 1280
  # Optional: height of the frame for the input with the detect role (default: use native stream resolution)
  height: 720
  # Optional: desired fps for your camera for the input with the detect role (default: shown below)
  # NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera.
  fps: 5
  # Optional: enables detection for the camera (default: True)
  enabled: true
  # Optional: Number of consecutive detection hits required for an object to be initialized in the tracker. (default: 1/2 the frame rate)
  min_initialized: 2
  # Optional: Number of frames without a detection before Frigate considers an object to be gone. (default: 5x the frame rate)
  max_disappeared: 25
  # Optional: Configuration for stationary object tracking
  stationary:
    # Optional: Frequency for confirming stationary objects (default: same as threshold)
    # When set to 1, object detection will run to confirm the object still exists on every frame.
    # If set to 10, object detection will run to confirm the object still exists on every 10th frame.
    interval: 50
    # Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s)
    threshold: 50
    # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever)
    # This can help with false positives for objects that should only be stationary for a limited amount of time.
    # It can also be used to disable stationary object tracking. For example, you may want to set a value for person, but leave
    # car at the default.
    # WARNING: Setting these values overrides default behavior and disables stationary object tracking.
    #          There are very few situations where you would want it disabled. It is NOT recommended to
    #          copy these values from the example config into your config unless you know they are needed.
    max_frames:
      # Optional: Default for all object types (default: not set, track forever)
      default: 3000
      # Optional: Object specific values
      objects:
        person: 1000
  # Optional: Milliseconds to offset detect annotations by (default: shown below).
  # There can often be latency between a recording and the detect process,
  # especially when using separate streams for detect and record.
  # Use this setting to make the timeline bounding boxes more closely align
  # with the recording. The value can be positive or negative.
  # TIP: Imagine there is an event clip with a person walking from left to right.
  #      If the event timeline bounding box is consistently to the left of the person
  #      then the value should be decreased. Similarly, if a person is walking from
  #      left to right and the bounding box is consistently ahead of the person
  #      then the value should be increased.
  # TIP: This offset is dynamic so you can change the value and it will update existing
  #      events, this makes it easy to tune.
  # WARNING: Fast moving objects will likely not have the bounding box align.
  annotation_offset: 0

# Optional: Object configuration
# NOTE: Can be overridden at the camera level
objects:
  # Optional: list of objects to track from labelmap.txt (default: shown below)
  track:
  - person
  # Optional: mask to prevent all object types from being detected in certain areas (default: no mask)
  # Checks based on the bottom center of the bounding box of the object.
  # NOTE: This mask is COMBINED with the object type specific mask below
  # Optional: filters to reduce false positives for specific object types
  filters:
    person:
      # Optional: minimum width*height of the bounding box for the detected object (default: 0)
      min_area: 5000
      # Optional: maximum width*height of the bounding box for the detected object (default: 24000000)
      max_area: 100000
      # Optional: minimum width/height of the bounding box for the detected object (default: 0)
      min_ratio: 0.5
      # Optional: maximum width/height of the bounding box for the detected object (default: 24000000)
      max_ratio: 2.0
      # Optional: minimum score for the object to initiate tracking (default: shown below)
      min_score: 0.5
      # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below)
      threshold: 0.7
      # Optional: mask to prevent this object type from being detected in certain areas (default: no mask)
      # Checks based on the bottom center of the bounding box of the object

# Optional: Motion configuration
# NOTE: Can be overridden at the camera level
motion:
  # Optional: The threshold passed to cv2.threshold to determine if a pixel is different enough to be counted as motion. (default: shown below)
  # Increasing this value will make motion detection less sensitive and decreasing it will make motion detection more sensitive.
  # The value should be between 1 and 255.
  threshold: 30
  # Optional: The percentage of the image used to detect lightning or other substantial changes where motion detection
  #           needs to recalibrate. (default: shown below)
  # Increasing this value will make motion detection more likely to consider lightning or ir mode changes as valid motion.
  # Decreasing this value will make motion detection more likely to ignore large amounts of motion such as a person approaching
  # a doorbell camera.
  lightning_threshold: 0.8
  # Optional: Minimum size in pixels in the resized motion image that counts as motion (default: shown below)
  # Increasing this value will prevent smaller areas of motion from being detected. Decreasing will
  # make motion detection more sensitive to smaller moving objects.
  # As a rule of thumb:
  #  - 10 - high sensitivity
  #  - 30 - medium sensitivity
  #  - 50 - low sensitivity
  contour_area: 10
  # Optional: Alpha value passed to cv2.accumulateWeighted when averaging frames to determine the background (default: shown below)
  # Higher values mean the current frame impacts the average a lot, and a new object will be averaged into the background faster.
  # Low values will cause things like moving shadows to be detected as motion for longer.
  # https://www.geeksforgeeks.org/background-subtraction-in-an-image-using-concept-of-running-average/
  frame_alpha: 0.01
  # Optional: Height of the resized motion frame  (default: 100)
  # Higher values will result in more granular motion detection at the expense of higher CPU usage.
  # Lower values result in less CPU, but small changes may not register as motion.
  frame_height: 100
  # Optional: motion mask
  # NOTE: see docs for more detailed info on creating masks
  # Optional: improve contrast (default: shown below)
  # Enables dynamic contrast improvement. This should help improve night detections at the cost of making motion detection more sensitive
  # for daytime.
  improve_contrast: false
  # Optional: Delay when updating camera motion through MQTT from ON -> OFF (default: shown below).
  mqtt_off_delay: 30

# Optional: Record configuration
# NOTE: Can be overridden at the camera level
record:
  # Optional: Enable recording (default: shown below)
  # WARNING: If recording is disabled in the config, turning it on via
  #          the UI or MQTT later will have no effect.
  enabled: true
  # Optional: Number of minutes to wait between cleanup runs (default: shown below)
  # This can be used to reduce the frequency of deleting recording segments from disk if you want to minimize i/o
  expire_interval: 60
  # Optional: Sync recordings with disk on startup and once a day (default: shown below).
  sync_recordings: false
  # Optional: Retention settings for recording
  retain:
    # Optional: Number of days to retain recordings regardless of events (default: shown below)
    # NOTE: This should be set to 0 and retention should be defined in events section below
    #       if you only want to retain recordings of events.
    days: 0
    # Optional: Mode for retention. Available options are: all, motion, and active_objects
    #   all - save all recording segments regardless of activity
    #   motion - save all recordings segments with any detected motion
    #   active_objects - save all recording segments with active/moving objects
    # NOTE: this mode only applies when the days setting above is greater than 0
    mode: all
  # Optional: Recording Export Settings
  export:
    # Optional: Timelapse Output Args (default: shown below).
    # NOTE: The default args are set to fit 24 hours of recording into 1 hour playback.
    # See https://stackoverflow.com/a/58268695 for more info on how these args work.
    # As an example: if you wanted to go from 24 hours to 30 minutes that would be going
    # from 86400 seconds to 1800 seconds which would be 1800 / 86400 = 0.02.
    # The -r (framerate) dictates how smooth the output video is.
    # So the args would be -vf setpts=0.02*PTS -r 30 in that case.
    timelapse_args: -vf setpts=0.04*PTS -r 30
  # Optional: Event recording settings
  events:
    # Optional: Number of seconds before the event to include (default: shown below)
    pre_capture: 5
    # Optional: Number of seconds after the event to include (default: shown below)
    post_capture: 5
    # Optional: Objects to save recordings for. (default: all tracked objects)
    objects:
    - person
    # Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones)
    # Optional: Retention settings for recordings of events
    retain:
      # Required: Default retention days (default: shown below)
      default: 10
      # Optional: Mode for retention. (default: shown below)
      #   all - save all recording segments for events regardless of activity
      #   motion - save all recordings segments for events with any detected motion
      #   active_objects - save all recording segments for event with active/moving objects
      #
      # NOTE: If the retain mode for the camera is more restrictive than the mode configured
      #       here, the segments will already be gone by the time this mode is applied.
      #       For example, if the camera retain mode is "motion", the segments without motion are
      #       never stored, so setting the mode to "all" here won't bring them back.
      mode: motion
      # Optional: Per object retention days
      objects:
        person: 15

# Optional: Configuration for the jpg snapshots written to the clips directory for each event
# NOTE: Can be overridden at the camera level
snapshots:
  # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
  enabled: true
  # Optional: save a clean PNG copy of the snapshot image (default: shown below)
  clean_copy: true
  # Optional: print a timestamp on the snapshots (default: shown below)
  timestamp: false
  # Optional: draw bounding box on the snapshots (default: shown below)
  bounding_box: true
  # Optional: crop the snapshot (default: shown below)
  crop: false
  # Optional: height to resize the snapshot to (default: original size)
  height: 175
  # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones)
  # Optional: Camera override for retention settings (default: global values)
  retain:
    # Required: Default retention days (default: shown below)
    default: 10
    # Optional: Per object retention days
    objects:
      person: 15
  # Optional: quality of the encoded jpeg, 0-100 (default: shown below)
  quality: 70

# Optional: RTMP configuration
# NOTE: RTMP is deprecated in favor of restream
# NOTE: Can be overridden at the camera level
rtmp:
  # Optional: Enable the RTMP stream (default: False)
  enabled: true

# Optional: Restream configuration
# Uses https://github.com/AlexxIT/go2rtc (v1.8.3)
go2rtc:
  streams:
    yard:
    - rtsp://user:password@ipcam:554/H.264
    - "ffmpeg:yard#audio=opus"
    yard_sub:
    - rtsp://user:password@ipcam:554/Streaming/Channels/102
    - "ffmpeg:yard_sub#audio=opus"
    fronth:
    - rtsp://user:password@ipcam/h264/ch01/main/av_stream
    fronth_sub:
    - rtsp://user:password@ipcam/h264/ch01/main/av_stream
    shed:
    - rtsp://user:password@ipcam/Streaming/Channels/501
    shed_sub:
    - rtsp://user:password@ipcam/Streaming/Channels/502
    both:
    - rtsp://user:password@ipcam:554/Streaming/Channels/1
    - "ffmpeg:both#audio=opus"
    both_sub:
    - rtsp://user:password@ipcam:554/Streaming/Channels/102
    - "ffmpeg:both_sub#audio=opus"
  webrtc:
    candidates:
      - HAlocaladress:8555
      - stun:8555

# Optional: jsmpeg stream configuration for WebUI
live:
  # Optional: Set the name of the stream that should be used for live view
  # in frigate WebUI. (default: name of camera)
  # Optional: Set the height of the jsmpeg stream. (default: 720)
  # This must be less than or equal to the height of the detect stream. Lower resolutions
  # reduce bandwidth required for viewing the jsmpeg stream. Width is computed to match known aspect ratio.
  height: 720
  # Optional: Set the encode quality of the jsmpeg stream (default: shown below)
  # 1 is the highest quality, and 31 is the lowest. Lower quality feeds utilize less CPU resources.
  quality: 8

cameras:
  yard_camera:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
      - path: rtsp://DOCKERlocaladress:8554/yard_sub
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://DOCKERlocaladress:8554/yard
        input_args: preset-rtsp-restream
        roles:
        - record
        - rtmp
    detect:
      width: 768
      height: 432
      fps: 5
    best_image_timeout: 60

  front_house_camera:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
      - path: rtsp://DOCKERlocaladress:8554/fronth_sub
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://DOCKERlocaladress:8554/fronth
        input_args: preset-rtsp-restream
        roles:
        - record
        - rtmp
    detect:
      width: 960
      height: 576
      fps: 5
    motion:
      mask:
        - 960,0,0,0,0,201,621,197,670,576,960,576
        - 623,190,613,288,0,258,0,181
    best_image_timeout: 60

  shed_camera:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
      - path: rtsp://DOCKER:8554/shed_sub
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://DOCKERlocaladress:8554/shed
        input_args: preset-rtsp-restream
        roles:
        - record
        - rtmp
    detect:
      width: 704
      height: 506
      fps: 5
    best_image_timeout: 60

  both_garages_camera:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
      - path: rtsp://DOCKERlocaladress:8554/both_sub
        input_args: preset-rtsp-restream
        roles:
        - detect
      - path: rtsp://DOCKERlocaladress:8554/both
        input_args: preset-rtsp-restream
        roles:
        - record
        - rtmp
    detect:
      width: 768
      height: 432
      fps: 5
    best_image_timeout: 60

    # Optional: URL to visit the camera web UI directly 

    # Optional: Configuration for the jpg snapshots published via MQTT
    mqtt:
      # Optional: Enable publishing snapshot via mqtt for camera (default: shown below)
      # NOTE: Only applies to publishing image data to MQTT via 'frigate/<camera_name>/<object_name>/snapshot'.
      # All other messages will still be published.
      enabled: true
      # Optional: print a timestamp on the snapshots (default: shown below)
      timestamp: true
      # Optional: draw bounding box on the snapshots (default: shown below)
      bounding_box: true
      # Optional: crop the snapshot (default: shown below)
      crop: true
      # Optional: height to resize the snapshot to (default: shown below)
      height: 270
      # Optional: jpeg encode quality (default: shown below)
      quality: 70
      # Optional: Restrict mqtt messages to objects that entered any of the listed zones (default: no required zones)

    # Optional: Configuration for how camera is handled in the GUI.
    ui:
      # Optional: Adjust sort order of cameras in the UI. Larger numbers come later (default: shown below)
      # By default the cameras are sorted alphabetically.
      order: 0
      # Optional: Whether or not to show the camera in the Frigate UI (default: shown below)
      dashboard: true

    # Optional: Configuration for how to sort the cameras in the Birdseye view.
    birdseye:
      # Optional: Adjust sort order of cameras in the Birdseye view. Larger numbers come later (default: shown below)
      # By default the cameras are sorted alphabetically.
      order: 0

# Optional
ui:
  # Optional: Set the default live mode for cameras in the UI (default: shown below)
  live_mode: mse
  # Optional: Set a timezone to use in the UI (default: use browser local time)
  # timezone: America/Denver
  # Optional: Use an experimental recordings / camera view UI (default: shown below)
  use_experimental: false
  # Optional: Set the time format used.
  # Options are browser, 12hour, or 24hour (default: shown below)
  time_format: browser
  # Optional: Set the date style for a specified length.
  # Options are: full, long, medium, short
  # Examples:
  #    short: 2/11/23
  #    medium: Feb 11, 2023
  #    full: Saturday, February 11, 2023
  # (default: shown below).
  date_style: short
  # Optional: Set the time style for a specified length.
  # Options are: full, long, medium, short
  # Examples:
  #    short: 8:14 PM
  #    medium: 8:15:22 PM
  #    full: 8:15:22 PM Mountain Standard Time
  # (default: shown below).
  time_style: medium
  # Optional: Ability to manually override the date / time styling to use strftime format
  # https://www.gnu.org/software/libc/manual/html_node/Formatting-Calendar-Time.html
  # possible values are shown above (default: not set)
  strftime_fmt: '%Y/%m/%d %H:%M'

# Optional: Telemetry configuration
telemetry:
  # Optional: Enabled network interfaces for bandwidth stats monitoring (default: empty list, let nethogs search all)
  network_interfaces:
  - eth
  - enp
  - eno
  - ens
  - wl
  - lo
  # Optional: Configure system stats
  stats:
    # Enable AMD GPU stats (default: shown below)
    amd_gpu_stats: true
    # Enable Intel GPU stats (default: shown below)
    intel_gpu_stats: true
    # Enable network bandwidth stats monitoring for camera ffmpeg processes, go2rtc, and object detectors. (default: shown below)
    # NOTE: The container must either be privileged or have cap_net_admin, cap_net_raw capabilities enabled.
    network_bandwidth: false
  # Optional: Enable the latest version outbound check (default: shown below)
  # NOTE: If you use the HomeAssistant integration, disabling this will prevent it from reporting new versions
  version_check: true

Relevant log output

(HA ERROR)
2024-02-16 10:26:12.095 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://192.168.7.228:5000/api/stats: Cannot connect to host 192.168.7.228:5000 ssl:default [Connect call failed ('192.168.7.228', 5000)]
2024-02-16 10:26:12.096 ERROR (MainThread) [custom_components.frigate] Error fetching frigate data: 
2024-02-16 10:26:17.096 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://192.168.7.228:5000/api/stats: Cannot connect to host 192.168.7.228:5000 ssl:default [Connect call failed ('192.168.7.228', 5000)]
2024-02-16 10:26:22.096 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://192.168.7.228:5000/api/stats: 502, message='Bad Gateway', url=URL('http://192.168.7.228:5000/api/stats')

(HA ERROR WHEN TRYING TO STREAM ON AUTOMATION)
2024-02-16 10:32:53.808 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_house_camera] Error from stream worker: Error opening stream (ERRORTYPE_5, I/O error) rtmp://192.168.7.228/live/front_house_camera
2024-02-16 10:32:53.803 ERROR (MainThread) [homeassistant.components.automation.tv_cam_auto_test] While executing automation automation.tv_cam_auto_test

(DOCKER ERROR)
2024-02-16 10:26:22.094672730  2024/02/16 10:26:22 [error] 143#143: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.7.214, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001stats", host: "192.168.7.228:5000"

FFprobe output from your camera

[{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"0/0","codec_long_name":"H.264/AVC/MPEG-4AVC/MPEG-4part10","height":576,"width":960}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"streams":[{"avg_frame_rate":"0/0","codec_long_name":"H.264/AVC/MPEG-4AVC/MPEG-4part10","height":576,"width":960}]}}]

Frigate stats

2024-02-16 10:26:20.874107603  [INFO] Preparing Frigate...
2024-02-16 10:26:20.922569771  [INFO] Starting Frigate...
2024-02-16 10:26:23.342936522  [2024-02-16 10:26:23] frigate.app                    INFO    : Starting Frigate (0.13.1-34fb1c2)
2024-02-16 10:26:23.475885503  [2024-02-16 10:26:23] frigate.config                 WARNING : RTMP restream is deprecated in favor of the restream role, recommend disabling RTMP.
2024-02-16 10:26:23.479799983  [2024-02-16 10:26:23] frigate.config                 WARNING : RTMP restream is deprecated in favor of the restream role, recommend disabling RTMP.
2024-02-16 10:26:23.483508213  [2024-02-16 10:26:23] frigate.config                 WARNING : RTMP restream is deprecated in favor of the restream role, recommend disabling RTMP.
2024-02-16 10:26:23.490527401  [2024-02-16 10:26:23] frigate.config                 WARNING : RTMP restream is deprecated in favor of the restream role, recommend disabling RTMP.
2024-02-16 10:26:23.529667966  [2024-02-16 10:26:23] peewee_migrate.logs            INFO    : Starting migrations
2024-02-16 10:26:23.536869999  [2024-02-16 10:26:23] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-02-16 10:26:23.546738385  [2024-02-16 10:26:23] frigate.app                    INFO    : Recording process started: 441
2024-02-16 10:26:23.554717580  [2024-02-16 10:26:23] frigate.app                    INFO    : go2rtc process pid: 100
2024-02-16 10:26:23.622763078  [2024-02-16 10:26:23] frigate.app                    INFO    : Output process started: 454
2024-02-16 10:26:23.648433931  [2024-02-16 10:26:23] frigate.app                    INFO    : Camera processor started for yard_camera: 461
2024-02-16 10:26:23.652322504  [2024-02-16 10:26:23] frigate.app                    INFO    : Camera processor started for front_house_camera: 462
2024-02-16 10:26:23.670549293  [2024-02-16 10:26:23] frigate.app                    INFO    : Camera processor started for shed_camera: 464
2024-02-16 10:26:23.679356464  [2024-02-16 10:26:23] frigate.app                    INFO    : Camera processor started for both_garages_camera: 467
2024-02-16 10:26:23.685416742  [2024-02-16 10:26:23] frigate.app                    INFO    : Capture process started for yard_camera: 469
2024-02-16 10:26:23.691841171  [2024-02-16 10:26:23] frigate.app                    INFO    : Capture process started for front_house_camera: 471
2024-02-16 10:26:23.701761524  [2024-02-16 10:26:23] frigate.app                    INFO    : Capture process started for shed_camera: 473
2024-02-16 10:26:23.721824344  [2024-02-16 10:26:23] frigate.app                    INFO    : Capture process started for both_garages_camera: 478
2024-02-16 10:26:26.284215837  [2024-02-16 10:26:23] detector.coral                 INFO    : Starting detection process: 451
2024-02-16 10:26:26.284220484  [2024-02-16 10:26:23] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-02-16 10:26:26.294160923  [2024-02-16 10:26:26] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-02-16 10:31:33.800966478  [2024-02-16 10:31:33] ffmpeg.yard_camera.record_rtmp ERROR   : [rtsp @ 0x5627ca8fefc0] Missing PPS in sprop-parameter-sets, ignoring
2024-02-16 10:31:33.801514905  [2024-02-16 10:31:33] ffmpeg.yard_camera.record_rtmp ERROR   : [segment @ 0x5627caaafa80] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2024-02-16 10:31:33.807538505  [2024-02-16 10:31:33] ffmpeg.yard_camera.record_rtmp ERROR   : [flv @ 0x5627ca91c140] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2024-02-16 10:31:33.807779575  [2024-02-16 10:31:33] ffmpeg.yard_camera.record_rtmp ERROR   : rtsp://192.168.7.228:8554/yard: Connection timed out
2024-02-16 10:31:33.807980476  [2024-02-16 10:31:33] ffmpeg.yard_camera.record_rtmp ERROR   : [flv @ 0x5627ca91c140] Failed to update header with correct duration.
2024-02-16 10:31:33.808175595  [2024-02-16 10:31:33] ffmpeg.yard_camera.record_rtmp ERROR   : [flv @ 0x5627ca91c140] Failed to update header with correct filesize.
2024-02-16 10:31:33.808401258  [2024-02-16 10:31:33] watchdog.yard_camera           INFO    : Terminating the existing ffmpeg process...
2024-02-16 10:31:33.808595225  [2024-02-16 10:31:33] watchdog.yard_camera           INFO    : Waiting for ffmpeg to exit gracefully...
2024-02-16 10:31:33.830364832  [2024-02-16 10:31:33] ffmpeg.both_garages_camera.record_rtmp ERROR   : [rtsp @ 0x5612f19d0fc0] Missing PPS in sprop-parameter-sets, ignoring
2024-02-16 10:31:33.834561822  [2024-02-16 10:31:33] ffmpeg.both_garages_camera.record_rtmp ERROR   : [segment @ 0x5612f1bb20c0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2024-02-16 10:31:33.838546003  [2024-02-16 10:31:33] ffmpeg.both_garages_camera.record_rtmp ERROR   : [flv @ 0x5612f19de200] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2024-02-16 10:31:33.838717572  [2024-02-16 10:31:33] ffmpeg.both_garages_camera.record_rtmp ERROR   : rtsp://192.168.7.228:8554/both: Connection timed out
2024-02-16 10:31:33.838882257  [2024-02-16 10:31:33] ffmpeg.both_garages_camera.record_rtmp ERROR   : [flv @ 0x5612f19de200] Failed to update header with correct duration.
2024-02-16 10:31:33.839048952  [2024-02-16 10:31:33] ffmpeg.both_garages_camera.record_rtmp ERROR   : [flv @ 0x5612f19de200] Failed to update header with correct filesize.
2024-02-16 10:31:33.839219310  [2024-02-16 10:31:33] watchdog.both_garages_camera   INFO    : Terminating the existing ffmpeg process...
2024-02-16 10:31:33.839356204  [2024-02-16 10:31:33] watchdog.both_garages_camera   INFO    : Waiting for ffmpeg to exit gracefully...
2024-02-16 10:31:53.815527017  [2024-02-16 10:31:53] watchdog.yard_camera           INFO    : No frames received from yard_camera in 20 seconds. Exiting ffmpeg...
2024-02-16 10:31:53.815612272  [2024-02-16 10:31:53] watchdog.yard_camera           INFO    : Waiting for ffmpeg to exit gracefully...
2024-02-16 10:31:53.852732031  [2024-02-16 10:31:53] frigate.video                  ERROR   : yard_camera: Unable to read frames from ffmpeg process.
2024-02-16 10:31:53.852981176  [2024-02-16 10:31:53] frigate.video                  ERROR   : yard_camera: ffmpeg process is not running. exiting capture thread...
2024-02-16 10:31:53.857230282  [2024-02-16 10:31:53] watchdog.both_garages_camera   INFO    : No frames received from both_garages_camera in 20 seconds. Exiting ffmpeg...
2024-02-16 10:31:53.857239624  [2024-02-16 10:31:53] watchdog.both_garages_camera   INFO    : Waiting for ffmpeg to exit gracefully...
2024-02-16 10:31:53.907412869  [2024-02-16 10:31:53] frigate.video                  ERROR   : both_garages_camera: Unable to read frames from ffmpeg process.
2024-02-16 10:31:53.908147264  [2024-02-16 10:31:53] frigate.video                  ERROR   : both_garages_camera: ffmpeg process is not running. exiting capture thread...
2024-02-16 10:32:03.854204528  [2024-02-16 10:32:03] watchdog.yard_camera           ERROR   : Ffmpeg process crashed unexpectedly for yard_camera.
2024-02-16 10:32:03.854649322  [2024-02-16 10:32:03] watchdog.yard_camera           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-02-16 10:32:03.854652672  [2024-02-16 10:32:03] ffmpeg.yard_camera.detect      ERROR   : [rtsp @ 0x55830d9fee40] Missing PPS in sprop-parameter-sets, ignoring
2024-02-16 10:32:03.854655097  [2024-02-16 10:32:03] ffmpeg.yard_camera.detect      ERROR   : rtsp://192.168.7.228:8554/yard_sub: Connection timed out
2024-02-16 10:32:03.854660293  [2024-02-16 10:32:03] ffmpeg.yard_camera.detect      ERROR   : [rtsp @ 0x55830d9fee40] RTP: PT=61: bad cseq be87 expected=a00f
2024-02-16 10:32:03.854674101  [2024-02-16 10:32:03] ffmpeg.yard_camera.detect      ERROR   : [rtsp @ 0x55830d9fee40] RTP: PT=60: bad cseq 888e expected=ec32
2024-02-16 10:32:03.909724769  [2024-02-16 10:32:03] watchdog.both_garages_camera   ERROR   : Ffmpeg process crashed unexpectedly for both_garages_camera.
2024-02-16 10:32:03.909772766  [2024-02-16 10:32:03] watchdog.both_garages_camera   ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-02-16 10:32:03.909843669  [2024-02-16 10:32:03] ffmpeg.both_garages_camera.detect ERROR   : [rtsp @ 0x555f6fdcfe40] Missing PPS in sprop-parameter-sets, ignoring
2024-02-16 10:32:03.909909819  [2024-02-16 10:32:03] ffmpeg.both_garages_camera.detect ERROR   : rtsp://192.168.7.228:8554/both_sub: Connection timed out

Operating system

Other Linux

Install method

Docker Compose

Coral version

USB

Network connection

Wired

Camera make and model

hikvision

Any other information that may be helpful

please help, this is need for security

About this issue

  • Original URL
  • State: closed
  • Created 4 months ago
  • Comments: 15

Most upvoted comments

that error just means frigate is not online yet and the integration requested the stas

Feel free to create a new discussion if something else comes up

there are still a lot of extra config that is not needed. Personally I’d suggest following https://docs.frigate.video/guides/getting_started#configuring-frigate

problem fixed, I don’t think it was anything to do with Frigate but due to me rebuild my docker install with the incorrect mDNS Advertiser on some containers. I shut down frigate and noticed high cpu load so decided to work on another Container and that’s where I think I found the problem. All seems to be working now thank you your advice, as it wasn’t working I was throwing even at it. I still don’t understand most of it, and I don’t like just thinking it just works so will try to study on it some more

It looks like you removed comments but there are still lots of things that look like extra config you don’t use. For example label mapping vehicle and animal but then you are not detecting those object labels. Also, using debug logging is not recommended unless specifically debugging a problem.

the logs that have been provided are not showing any errors so it is not clear if the streams are having problems or not

my point is that a lot was copied from the reference config which is not needed in your config and just makes things more difficult to read.

in any case, please provide new logs