Reolink Elite Floodlight wifi [Camera Support]:

[greyvv]

Describe the problem you are having

trying to add the new reolink floodlight cam to my existing setup. Right now i have the reolink video doorbell working great with the suggested config. The floodlight also has 2-way talk so im attempting to add it the same way to the config, just changing the ip address. I tried adding some detect hight and width parameters to the config that arent listed but they had no effect

thanks

Version

16.1

What browser(s) are you using?

chrome

Frigate config file

mqtt:
  enabled: true
  host: 192.168.x.x
  user: mqtt-user
  password: mqtt-user


go2rtc:
  streams:
    doorbell_cam:
      - "ffmpeg:http://192.168.x.x/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=xxxxx&password=xxxxx#video=copy#audio=copy#audio=opus"
      - rtsp://192.168.x.x/Preview_01_sub
    doorbell_cam_sub:
      - "ffmpeg:http://192.168.x.x/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxxx&password=xxxxx"
    floodlight_cam:
      - "ffmpeg:http://192.168.x.x/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=xxxx&password=xxxxx#video=copy#audio=copy#audio=opus"
      - rtsp://192.168.x.x/Preview_01_sub
    floodlight_cam_sub:
      - "ffmpeg:http://192.168.x.x/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=xxxx&password=xxxxxx"
  webrtc:
    candidates:
      - 192.168.x.x:8555
      - stun:8555

cameras:
  doorbell_cam:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell_cam?video=copy&audio=aac
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/doorbell_cam_sub?video=copy
          input_args: preset-rtsp-restream
          roles:
            - detect
    record:
      enabled: true
      retain:
        days: 14
        mode: all
    motion:
      mask: 0.248,0.06,0.724,0.06,0.725,0,0.249,0
      threshold: 30
      contour_area: 10
      improve_contrast: true
    objects:
      filters:
        person:
          min_area: 150

  floodlight_cam:
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/floodlight_cam?video=copy&audio=aac
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://127.0.0.1:8554/floodlight_cam_sub?video=copy
          input_args: preset-rtsp-restream
          roles:
            - detect
    record:
      enabled: true
      retain:
        days: 14
        mode: all

detectors:
  cpu1:
    type: cpu

version: 0.16-0
detect:
  enabled: false
semantic_search:
  enabled: false
  model_size: small
face_recognition:
  enabled: false
  model_size: small
lpr:
  enabled: false
classification:
  bird:
    enabled: false

Relevant Frigate log output

2025-09-23 17:05:10.478978351  [2025-09-23 17:05:10] frigate.video                  ERROR   : floodlight_cam: Unable to read frames from ffmpeg process.
2025-09-23 17:05:10.479386059  [2025-09-23 17:05:10] frigate.video                  ERROR   : floodlight_cam: ffmpeg process is not running. exiting capture thread...
2025-09-23 17:05:23.677362804  [2025-09-23 17:05:23] watchdog.floodlight_cam        ERROR   : Ffmpeg process crashed unexpectedly for floodlight_cam.
2025-09-23 17:05:23.677680531  [2025-09-23 17:05:23] watchdog.floodlight_cam        ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-09-23 17:05:23.678150200  [2025-09-23 17:05:23] ffmpeg.floodlight_cam.detect   ERROR   : [rtsp @ 0x636d28e50f40] method DESCRIBE failed: 404 Not Found
2025-09-23 17:05:23.678481580  [2025-09-23 17:05:23] ffmpeg.floodlight_cam.detect   ERROR   : [in#0 @ 0x636d28e50bc0] Error opening input: Server returned 404 Not Found
2025-09-23 17:05:23.678756853  [2025-09-23 17:05:23] ffmpeg.floodlight_cam.detect   ERROR   : Error opening input file rtsp://127.0.0.1:8554/floodlight_cam?video=copy&audio=aac.
2025-09-23 17:05:23.678962659  [2025-09-23 17:05:23] ffmpeg.floodlight_cam.detect   ERROR   : Error opening input files: Server returned 404 Not Found
2025-09-23 17:05:23.679169757  [2025-09-23 17:05:23] watchdog.floodlight_cam        INFO    : Restarting ffmpeg...

Relevant go2rtc log output

2025-09-23 17:05:10.476580036  17:05:10.476 WRN [rtsp] error="streams: exec/rtsp\n[rtsp @ 0x57f795630fc0] dimensions not set\n[out#0/rtsp @ 0x57f79563b040] Could not write header (incorrect codec parameters ?): Invalid argument\n[af#0:2 @ 0x57f79558adc0] Error sending frames to consumers: Invalid argument\n[af#0:2 @ 0x57f79558adc0] Task finished with error code: -22 (Invalid argument)\n[af#0:2 @ 0x57f79558adc0] Terminating thread with return code -22 (Invalid argument)\n[out#0/rtsp @ 0x57f79563b040] Nothing was written into output file, because at least one of its streams received no packets...., user/pass not provided" stream=floodlight_cam

FFprobe output from your camera

x

Frigate stats

No response

Operating system

Other Linux

Install method

Docker CLI

Object Detector

CPU (no coral)

Network connection

Wired

Camera make and model

reolink elite floodlight cam

Screenshots of the Frigate UI's System metrics pages

x

Any other information that may be helpful

No response

[inkeep-ai-assistant[bot]]

Your configuration for the Reolink floodlight camera is modeled correctly on the recommended approach for Reolink cameras, but the error indicates that the RTSP restream endpoint for floodlight_cam is not available, resulting in a 404 Not Found from ffmpeg. This suggests that go2rtc is not successfully providing the restream for this camera, possibly due to an issue with the stream source or the stream config.

Here are some direct troubleshooting steps and checks based on the documentation:

1. Confirm Camera Stream URLs

   • Double-check the URLs for your floodlight camera. Try accessing the HTTP FLV stream and RTSP stream directly in a tool like VLC or ffmpeg to confirm they work outside of Frigate(1).

2. Check go2rtc Stream Naming

   • The stream names under go2rtc: streams: must exactly match the names used in your camera ffmpeg input paths. In your config, you have:

     go2rtc:
       streams:
         floodlight_cam:
           - ...
     cameras:
       floodlight_cam:
         ffmpeg:
           inputs:
             - path: rtsp://127.0.0.1:8554/floodlight_cam?video=copy&audio=aac
     

     This matches, which is correct(2).

3. Review go2rtc Logs and Web Interface

   • Use the go2rtc web interface at port 1984 to check if floodlight_cam is receiving a valid stream(3).
   • If you see errors about dimensions or codecs, it may indicate a problem with the camera's video or audio format. Make sure your camera is set to H264 video and AAC/Opus audio if possible(3), (1).

4. Audio Codec Compatibility

   • If your camera does not support AAC audio, the config line #audio=opus is correct for re-encoding audio to Opus(1).

5. Check for Typo or Password Issues

   • Ensure there are no extra spaces, typos, or URL encoding issues in your stream URLs and credentials. For complex passwords, URL-encode them as needed(2).

6. Test Without 2-Way Audio (RTSP Only)

   • Temporarily remove the secondary RTSP stream (the rtsp://.../Preview_01_sub line) and test with only the HTTP-FLV source to see if the main stream works. Some Reolink models may not support both streams simultaneously or may require different RTSP URLs(1).

7. Firmware and Camera Settings

   • Some Reolink models require specific firmware settings to enable HTTP-FLV or RTSP. Check the camera's web interface for stream options and ensure the correct stream type and codec are enabled(1).

8. Container Networking

   • Since you are using Docker CLI, make sure port 8554 is published and accessible to Frigate/ffmpeg and go2rtc, and that there are no firewall or network issues blocking internal connections(2).

If the above steps don't resolve the issue, please provide the output of testing the floodlight camera's HTTP-FLV and RTSP streams directly in VLC or ffmpeg, and check the go2rtc web UI for stream status.

You can reference these sections for more details:

• Restream
• Configuring go2rtc
• Camera Specific Configurations - Reolink

📚 Sources:

1. Camera Specific Configurations
2. Restream
3. Configuring go2rtc

---

Have another question? Just tag @inkeep.

[greyvv]

the http stream wont play in vlc either. error says unknown codec. added the floodlight to frigate just using the rstp stream. that seems to be working fine

[NickM-27]

if it's higher resolution than 5MP that would likely be why, as reolinks are usually h265 only in that case, and http-flv via h265 is very new

[rjgrandy]

the http stream wont play in vlc either. error says unknown codec. added the floodlight to frigate just using the rstp stream. that seems to be working fine

Do you have any trouble getting the main stream up in frigate? The sub stream seems to work just fine, but when I click to go to the camera page, it won't show the main stream and just falls back to low bandwidth mode after a long time.

It does seems to play okay in VLC though.

I am using the RTSP option for both.

[rjgrandy]

I guess this is because my desktop chrome browser doesn't support H265 (I checked it on some website), not sure why, perhaps because it is a VM on Unraid? My phone seems to do okay with the main stream. There doesn't seem to be an option on the camera to change to a H264 main stream... :(

[Cytomax55]

Did you get it working?

[Cytomax55]

@NickM-27
I was lucky enough to talk to odi on digiblur discord and he told me that

when connecting to the REOLINK Elite Floodlight Wifi lower quality channel
https://reolink.com/product/elite-floodlight-wifi/

instead of
stream=channel0_ext

it is
stream=channel0_sub

Here is my working config
#######################

backyard_center:
  - ffmpeg:http://192.168.0.53/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=XXXX#video=copy#audio=copy#audio=opus
  - rtsp://admin:XXXX@192.168.0.53/Preview_01_sub
backyard_center_sub:
  - ffmpeg:http://192.168.0.53/flv?port=1935&app=bcs&stream=channel0_sub.bcs&user=admin&password=XXXXX

########################

You may consider adding this to the camera specific config section
https://docs.frigate.video/configuration/camera_specific

BTW.. thank you again for all you do for frigate, amazing piece of software!

[Cytomax55]

If you opened vlc and opened network stream and typed

rtsp://admin:XXXX@192.168.0.53/Preview_01_sub

making sure to replace xxx with your password
and the ip with your local ip address
and you didnt get video then the problem is with the camera or computer or network

do you have any other cameras you can try out

are you sure vlc plays rtsp streams?
on linux it didnt and i had to install smplayer

I noticed you keep pasting links that i am not using such as

rtsp://admin:xxxx@192.168.xx.xx/Preview_01_main

and i am recommending

rtsp://admin:XXXX@192.168.0.53/Preview_01_sub

are you sure your link even exist? why dont you try my links first just to make sure

[weiserlord]

Yesterday I installed my Elite Floodlight Wifi HW-Version: IPC_NT18NA68MPW and FW: v3.2.0.5316_2508281222 (newest for this HW)

Firgate runs as HAOS addon on a Huidun H50 with N150 Processor
After a long trial an error, I got it running, but still have problems with
„Unable to keep up with recording segments in cache for Garten_Kamera. Keeping the 6 most recent segments out of 7 and discarding the rest“

The cause is the 4k main stream, without it no errors occur.

I tried as shown above

garten_reolink_camera_twt:
- "ffmpeg:http://192.168.XXX.XXX/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=user&password=Pw#video=copy#audio=copy#audio=opus"
- rtsp://User:Pw@192.168.XXX.XXX/h265Preview_01_main"
garten_reolink_camera_twt_sub:
- "ffmpeg:http://192.168.XXX.XXX/flv?port=1935&app=bcs&stream=channel0_sub.bcs&user=User&password=Pw"

With various variations 
…. video=copy#audio=drop
…. video=copy#audio=acc

in fact frigate AND VLC are only able to establish the rtsp stream for the main 4k stream. 
If I open http://192.168.XXX.XXX/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=user&password=Pw#video=copy#audio=copy#audio=opus
on VLC it calls 
„cannot identify audio or video codec“; BUT the audiostream starts to play without video. 

It seems that the reolink floodlight on 4k main streams had a problem to communicate the current codec. 
Any other news on the front?

[weiserlord]

[weiserlord]

I could solve my problem! I installed ffmpeg 8 -> #21125

[DanitiKain]

I could solve my problem! I installed ffmpeg 8 -> #21125

Can you please share full details of what you have done + your config. I tried to follow this and it somewhat works but the live stream will say its in low bandwidth mode due to errors, 2 way audio isn't available on all the streams either.

I have tried so many different configurations. How do I tell what version of ffmpeg I am running inside frigate. I believe I have version 8 extracted properly and the path in the config file I just don't know if it is actually calling that version or not when processing my stream. Anything you could share would be greatly appreciated.

I have also turned down my primary stream to 4k.

I am using the frigate elite pro POE version.

[bagobones]

H.265 does not work on most main line linux distros by default in most browser, most 4k cameras use H.265.

It is possible to get H.265 to work however it may depend on your distro and particular flavour of chrome you are using.. IE Google chrome, chromium etc.

On CatchyOS (arch based distro) with Google Chrome Installed from the AUR H.265 works fine in frigate and on the elite floodlights own browser interface.

On some distros you just need to install the "extra media codecs" pack or one of the "community codecs packs" in others the version of chrome they package does not have it enabled and on some the flatpack version works.

H.265 in a browser under linux is possible but you need to be running a REALLY current set of drivers and browser settings for it to work

Same goes for firefox till recently It did not support it at all until very recently.

[Cytomax55]

I am going to wait for ffmpeg 8 but in the mean time this works great for Two Way Audio

if you use
stream=channel0_MAIN
this will give you h265 which doesnt work

if you use
stream=channel0_ext
this will give you h264 at lower resolution but still higher than sub
Resolution: 2560 x 720

If you use stream=channel0_sub
Resolution: 1536 x 432

i imagine once ffmpeg 8 is packaged with frigate this wont be a problem

camera_43:
      - "ffmpeg:http://192.168.0.43/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user={FRIGATE_RTSP_USER}&password={FRIGATE_RTSP_PASSWORD}#video=h264#audio=copy#audio=opus"
      - "rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.0.43/Preview_01_sub"
    camera_43_sub:
      - "ffmpeg:http://192.168.0.43/flv?port=1935&app=bcs&stream=channel0_sub.bcs&user={FRIGATE_RTSP_USER}&password={FRIGATE_RTSP_PASSWORD}"
      - "rtsp://{FRIGATE_RTSP_USER}:{FRIGATE_RTSP_PASSWORD}@192.168.0.43/Preview_01_sub"