frigate: [Config Support]: Failed to start add-on Port '8555'

Describe the problem you are having

I just upgraded to 0.12.0 and Frigate won’t start. When I click on “Start” I get the following message: “Failed to start add-on Port ‘8555’ is already in use by something else on the host.” Nothing in the log file since it didn’t try to start. Everything was working fine prior to upgrade. I tried repotting my host and that did not fix the problem.

Version

0.12.0

Frigate config file

mqtt:
  host: 192.168.1.112
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: homeassistant
  password: 
  stats_interval: 60

database:
  path: /media/frigate/clips/frigate.db
  
detectors:
  coral:
    type: edgetpu
    device: usb

cameras:
  garage:
    ffmpeg:
      input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
      output_args: 
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
      inputs:
        - path: rtsp://user:pwd@192.168.70.72:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
            - rtmp
        - path: rtsp://user:pwd@192.168.70.72:554/live
          roles:
            - record
    detect:
      width: 704
      height: 480
      fps: 5
    objects:
      track:
        - person
        - cat
      filters:
        person:
          threshold: 0.6
    motion:
      mask:
        - 700,0,700,46,515,46,515,0
        - 704,480,704,457,446,313,269,480
        - 704,192,641,140,512,123,500,202,704,354
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 10
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      retain:
        default: 5
        
  basement:
    ffmpeg:
      input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
      output_args: 
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac      
      inputs:
        - path: rtsp://usedr:pwd@192.168.70.71:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
            - rtmp
        - path: rtsp://user:pwd@192.168.70.71:554/live
          roles:
            - record
    detect:
      width: 704
      height: 480
      fps: 5
    objects:
      track:
        - person
        - cat
      filters:
        person:
          threshold: 0.6
    motion:
      mask:
        - 700,0,700,46,515,46,515,0
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 10
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      retain:
        default: 5
        
  backyard:
    ffmpeg:
      input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
      output_args: 
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
      inputs:
        - path: rtsp://user:pwd@192.168.70.73:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
            - rtmp
        - path: rtsp://user:pwd@192.168.70.73:554/live
          roles:
            - record
    detect:
      width: 704
      height: 480
      fps: 5
    objects:
      track:
        - person
        - cat
      filters:
        person:
          threshold: 0.6
    motion:
      mask:
        - 700,0,700,46,515,46,515,0
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 10
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      retain:
        default: 5

  front:
    ffmpeg:
      input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
      output_args: 
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
      inputs:
        - path: rtsp://user:pwd@192.168.70.74:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
            - rtmp
        - path: rtsp://user:pwd@192.168.70.74:554/live
          roles:
            - record
    detect:
      width: 704
      height: 480
      fps: 5
    objects:
      track:
        - person
        - cat
      filters:
        person:
          threshold: 0.6
    motion:
      mask:
        - 700,0,700,46,515,46,515,0
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 10
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      retain:
        default: 5
        
  front-door:
    ffmpeg:
      input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1
      output_args: 
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
      inputs:
        - path: rtsp://user:pwd@192.168.70.75:554/cam/realmonitor?channel=1&subtype=1
          roles:
            - detect
            - rtmp
        - path: rtsp://user:pwd@192.168.70.75:554/live
          roles:
            - record
    detect:
      width: 704
      height: 480
      fps: 5
    objects:
      track:
        - person
        - cat
      filters:
        person:
          threshold: 0.6
    motion:
      mask:
        - 700,0,700,46,515,46,515,0
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 10
    snapshots:
      enabled: True
      timestamp: False
      bounding_box: True
      retain:
        default: 5
                
birdseye:
  enabled: True
  width: 1280
  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: 3
  # 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: motion

Relevant log output

n/a

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

Coral version

USB

Any other information that may be helpful

No response

About this issue

Original URL
State: closed
Created a year ago
Reactions: 1
Comments: 32

Most upvoted comments

most likely you have webrtc card installed which is also using port 8555, you will need to remove that to start frigate. Once started, you can add back webrtc card (or whatever it is) and use the embedded version of go2rtc

NickM-27 on Apr 10, 2023

I had the identical error after the last update. In my case there was a conflict with go2rtc. After disabling go2rtc Frigate started without a problem.

PioKow2023 on May 26, 2023

I had even dummier case. I had been playing around by installing Frigate and also Frigate (full access). When I decided that I will be using only Frigate (full access) - I uninstalled original Frigate (w/o full access) add-on. But then I couldn’t start Frigate (full access) as HassOS coulnd’t find docker image or something like that.

So I installed previously removed Frigate add-on and was mostly playing around with Frigate (full access). After few days I couldn’t manage to start add-on as it was throwing this error (about used port).

Found out that Frigate add-on had “Start on boot” checked (turned on). So looks like after reboot 1st add-on (which I don’t use) started and I couldn’t start Frigate (full access).

Leaving this comment here, maybe someone will do something dummy like me and will try to figure out what’s wrong 😆

janis-vitols on Oct 3, 2023

Frigates internal go2rtc supports all features so there’s no reason to run both.

Ah, does it support two-way audio ?

Yes, of course

NickM-27 on Apr 30, 2023

Could you please be more specific? How do I do that?

And what about these cards?

Thank you!

type: custom:webrtc-camera
show_state: true
show_name: true
camera_view: auto
url: rtsp://admin:xxxxxxxxxxxxx@192.168.0.203:554/Streaming/Channels/101
intersection: 0.75
ui: true
ptz:
  opacity: 0.8
  service: onvif.ptz
  distance: 0.1
  speed: 0.8
  move_mode: RelativeMove
  data_left:
    pan: LEFT
    device_id: 59b6890852a183a12d10985a1502aad6
  data_right:
    pan: RIGHT
    device_id: 59b6890852a183a12d10985a1502aad6
  data_up:
    tilt: UP
    device_id: 59b6890852a183a12d10985a1502aad6
  data_down:
    tilt: DOWN
    device_id: 59b6890852a183a12d10985a1502aad6
  data_zoom_in:
    zoom: ZOOM_IN
    entity_id: 59b6890852a183a12d10985a1502aad6
  data_zoom_out:
    zoom: ZOOM_OUT
    entity_id: 59b6890852a183a12d10985a1502aad6

you simply go to Settings -> Devices & Services -> webRTC Camera and press the 3 dots then delete. Then you press the add button, webRTC Camera and then add it. When it asks for the location of the server it will either have frigate autofilled if you run the addon or you will put frigate_ip:1984 making sure that frigate_ip is actually the ip address of frigate

NickM-27 on Apr 10, 2023

I have the same problem. So I have to replace WebRtc for go2rtc? I was using WebRtc because of PTZ…

webrtc card uses go2rtc behind the scenes. So you simply remove the integration and then re-add it pointing the integration at frigate:1984

NickM-27 on Apr 10, 2023

Okay. I don’t really have time to do that now so I’ve just restored back to 0.11.0 and everything is back up and running so I’ll just stay there for now. Thanks.

ronrath on Apr 10, 2023