[Camera Support]: Reolink Wifi doorbell configuration - not working #14967
-
Describe the problem you are havingNot able to properly configure Reolink WiFi Doorbell to record on Frigate installed on Rpi 4 (8GB, no coral). Front_Door: Unable to read frames from ffmpeg process. Have verified ffmpeg is installed and does operate. Test converted a file. I am able to on my separate Odroid Home Assistant system to integrate Reolink and view the Reolink WiFi Doorbell. Version0.14.1-f4f3cfa What browser(s) are you using?Chromium Version 130.0.6723.91 (Official Build) built on Debian GNU/Linux 12 (bookworm) (64-bit) Frigate config filemqtt:
enabled: false
ffmpeg:
hwaccel_args: preset-rpi-64-h264 #Enable Hardware Acceleration
go2rtc:
streams:
Front_Door:
- "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=username&password=password#video=copy#audio=copy#audio=opus"
- rtsp://reolink_ip/Preview_01_sub
Front_door_sub:
- "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=username&password=password"
cameras:
# Backdoor:
# ffmpeg:
# inputs:
# - path: rtsp://192.168.0.54:8555/rtsp
# roles:
# - detect
Front_Door:
ffmpeg:
inputs:
- path: rtsp://192.168.0.42:8555/Front_Door #The Stream you want to monitor
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://192.168.0.42:8555/Front_Door_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
enabled: false # Detection is disabled
width: 1280 # The Cameras resolution
height: 720 # The Cameras resolution
#version: 0.14 version: 0.14
version: 0.14Relevant Frigate log output2024-11-13 14:21:18.586143562 [2024-11-13 14:21:18] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x55c82df840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:21:18.586780851 [2024-11-13 14:21:18] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:21:18.679505733 [2024-11-13 14:21:18] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:21:18.679925876 [2024-11-13 14:21:18] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...
2024-11-13 14:21:28.614173928 [2024-11-13 14:21:28] watchdog.Front_Door ERROR : Ffmpeg process crashed unexpectedly for Front_Door.
2024-11-13 14:21:28.615051213 [2024-11-13 14:21:28] watchdog.Front_Door ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-13 14:21:28.615932740 [2024-11-13 14:21:28] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x55bdec4840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:21:28.616763841 [2024-11-13 14:21:28] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:21:28.849478720 [2024-11-13 14:21:28] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:21:28.849734161 [2024-11-13 14:21:28] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...
2024-11-13 14:21:38.662222884 [2024-11-13 14:21:38] watchdog.Front_Door ERROR : Ffmpeg process crashed unexpectedly for Front_Door.
2024-11-13 14:21:38.662762655 [2024-11-13 14:21:38] watchdog.Front_Door ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-13 14:21:38.662944949 [2024-11-13 14:21:38] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x5595b74840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:21:38.663489554 [2024-11-13 14:21:38] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:21:38.842679337 [2024-11-13 14:21:38] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:21:38.844276521 [2024-11-13 14:21:38] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...
2024-11-13 14:21:48.693248450 [2024-11-13 14:21:48] watchdog.Front_Door ERROR : Ffmpeg process crashed unexpectedly for Front_Door.
2024-11-13 14:21:48.694033293 [2024-11-13 14:21:48] watchdog.Front_Door ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-13 14:21:48.694797043 [2024-11-13 14:21:48] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x558570f840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:21:48.695710255 [2024-11-13 14:21:48] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:21:48.800398907 [2024-11-13 14:21:48] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:21:48.800646034 [2024-11-13 14:21:48] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...
2024-11-13 14:21:58.755698363 [2024-11-13 14:21:58] watchdog.Front_Door ERROR : Ffmpeg process crashed unexpectedly for Front_Door.
2024-11-13 14:21:58.755713455 [2024-11-13 14:21:58] watchdog.Front_Door ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-13 14:21:58.755717474 [2024-11-13 14:21:58] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x559fc26840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:21:58.755720751 [2024-11-13 14:21:58] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:21:58.981293031 [2024-11-13 14:21:58] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:21:58.982074540 [2024-11-13 14:21:58] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...
2024-11-13 14:22:08.785507379 [2024-11-13 14:22:08] watchdog.Front_Door ERROR : Ffmpeg process crashed unexpectedly for Front_Door.
2024-11-13 14:22:08.785525156 [2024-11-13 14:22:08] watchdog.Front_Door ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-13 14:22:08.785529249 [2024-11-13 14:22:08] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x55ae860840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:22:08.786026373 [2024-11-13 14:22:08] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:22:08.969929050 [2024-11-13 14:22:08] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:22:08.970593357 [2024-11-13 14:22:08] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...
2024-11-13 14:22:18.813579814 [2024-11-13 14:22:18] watchdog.Front_Door ERROR : Ffmpeg process crashed unexpectedly for Front_Door.
2024-11-13 14:22:18.826109032 [2024-11-13 14:22:18] watchdog.Front_Door ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-13 14:22:18.827082799 [2024-11-13 14:22:18] ffmpeg.Front_Door.detect ERROR : [tcp @ 0x55963a8840] Connection to tcp://192.168.0.42:8555?timeout=5000000 failed: Connection refused
2024-11-13 14:22:18.828534543 [2024-11-13 14:22:18] ffmpeg.Front_Door.detect ERROR : rtsp://192.168.0.42:8555/Front_Door_sub: Connection refused
2024-11-13 14:22:18.924910212 [2024-11-13 14:22:18] frigate.video ERROR : Front_Door: Unable to read frames from ffmpeg process.
2024-11-13 14:22:18.925581075 [2024-11-13 14:22:18] frigate.video ERROR : Front_Door: ffmpeg process is not running. exiting capture thread...Relevant go2rtc log outputno sure where this is located.FFprobe output from your cameraFrom within the container - not sure how to do.Frigate statsNot sure how to obtainOperating systemOther Linux Install methodDocker Compose Object DetectorCPU (no coral) Network connectionWired Camera make and modelReolink Wifi (not-POE) Screenshots of the Frigate UI's System metrics pagesAny other information that may be helpfulI am testing to learn the process to install and configure Frigate to work with the reolink and other type camera(s) prior to working to install on my Home Assistant system. Your help to this very novice is appreciate. |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments 37 replies
-
|
Check out the documentation. You should be using |
Beta Was this translation helpful? Give feedback.
-
|
@hawkeye217 followed your guidance and changed the input urls. Errors have changed and read: The errors have changed. |
Beta Was this translation helpful? Give feedback.
-
|
the lowercase |
Beta Was this translation helpful? Give feedback.
-
|
@PrplHaz4 Nice catch!. BUt unfortunately, did not solve the issue. Logs show: Your help is appreciated. Next thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
@agoose77 - I originally had the camera IPs in the confg file set to what the camera's were identified via my router: 192.168.0.xx. however, #14967 (comment) suggested I should change to 127.0.0.1:8554. Which I did change. I did not change the actual camera IP. Seems like they should be what the camera's IP actually is: 192.168..x. vice 127.0.0.x, etc. And what I think you are saying or asking is - are the IPs in the config and the camera the same ....that answer would be no. @NickM-27 mqtt:
enabled: false
ffmpeg:
hwaccel_args: preset-rpi-64-h264 #Enable Hardware Acceleration
#go2rtc:
# streams:
# Front_Door:
# - "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=username&password=password#video=copy#audio=copy#audio=opus"
# - rtsp://reolink_ip/Preview_01_sub
# Front_Door_sub:
# - "ffmpeg:http://reolink_ip/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=username&password=password"
cameras:
# Backdoor:
# ffmpeg:
# inputs:
# - path: rtsp://192.168.0.54:8555/rtsp
# roles:
# - detect
Front_Door:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/Front_Door #The Stream you want to monitor
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/Front_Door_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
enabled: false # Detection is disabled
width: 1280 # The Cameras resolution
height: 720 # The Cameras resolution
#version: 0.14 version: 0.14
version: 0.14 |
Beta Was this translation helpful? Give feedback.
-
|
Sorry about the bold lettering. |
Beta Was this translation helpful? Give feedback.
-
|
if you are going to be using 127.0.0.1:8554 then you must be using go2rtc |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 as I read to understand you comment #14967 (reply in thread), did I provide the correct config file? |
Beta Was this translation helpful? Give feedback.
-
|
@dwdonnelly there shouldn't be a correlation between the go2rtc IP and the camera IP - the idea is that you set the camera IP in go2rtc, and then hit a single endpoint on the go2rtc server to locate the stream by name |
Beta Was this translation helpful? Give feedback.
-
|
@agoose77, @NickM-27, @PrplHaz4, @hawkeye217—Happy holidays to all. Well, I decided to wipe the thumb drive on the Raspberry Pi 4 and restart with a very basic configuration. Unfortunately, I still have no success getting the Reolink Wi-Fi doorbell to show up in Frigate on the Raspberry Pi 4. I did not setup the Go2rtc, as I wanted to get the video working first. I set the unique Reolink camera settings: On, fluency first and Interframe Space 1x. I have installed/compiled/tested ffmpeg satisfactorily. I can view the front doorbell camera through Home Assistant. I can access the camera through the web browser using 192.168.0.42 and associated UID/PWD. My file structure is as follows: /opt/stacks/frigate (contains storage directory and config.yml and docker-compose.yml) I verified the RTSP port on the camera is set to 8554. What am I missing here? Your help is appreciated. My docker-compose.yml file:
And my config.yml file:
ffmpeg: cameras: Error logs:
|
Beta Was this translation helpful? Give feedback.
-
|
open vlc, and connect to a network stream, try all the urls you have in your config to connect directly to the camera. |
Beta Was this translation helpful? Give feedback.
-
|
The network config on the camera itself may not be setup correctly. and i'm not sure if this link is right I think it should be this, but I'm just not aware if the one you have works or not. |
Beta Was this translation helpful? Give feedback.
-
|
Made the change by adding in the h264, no change. logs provided. see server setup at bottom. Frigate logs: go2rtc log: When you ask about the server config...do you mean this:
ONVIF is selected and set to 8000. |
Beta Was this translation helpful? Give feedback.
-
|
There's the problem. Change 8554 in your camera to 554 |
Beta Was this translation helpful? Give feedback.
-
|
I also missed the port in the link. and try connecting to the links with vlc. |
Beta Was this translation helpful? Give feedback.
-
|
Ok….none of the links worked and the error coming back said could not connect to 554. So I reviewed the server settings in the mobile app…. changed rtsp from 8554 to 554….then tried this link and it works: ***@***.***:554
Should I keep trying different links?
Or?
From: clsferguson ***@***.***>
Sent: Thursday, December 12, 2024 1:46 PM
To: blakeblackshear/frigate ***@***.***>
Cc: dwdonnelly ***@***.***>; Mention ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Camera Support]: Reolink Wifi doorbell configuration - not working (Discussion #14967)
open vlc, and connect to a network stream, try all the urls you have in your config to connect directly to the camera.
http://192.168.0.42/flv?port=1935 <http://192.168.0.42/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=username&password=password> &app=bcs&stream=channel0_main.bcs&user=username&password=password
***@***.***/Preview_01_sub
http://192.168.0.42/flv?port=1935 <http://192.168.0.42/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=username&password=password> &app=bcs&stream=channel0_ext.bcs&user=username&password=password
—
Reply to this email directly, view it on GitHub <#14967 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKDT7CMWC5GBPPOGAXLTKTD2FH7YHAVCNFSM6AAAAABRXSADHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJUHE3TGNQ> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKDT7CLWRD6HYLPA7QAOTY32FH7YHA5CNFSM6AAAAABRXSADHWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAWA6CQ.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
No, need to verify the web ui isn't set to https |
Beta Was this translation helpful? Give feedback.
-
|
Done. Reading the other e-mails.
From: clsferguson ***@***.***>
Sent: Thursday, December 12, 2024 2:33 PM
To: blakeblackshear/frigate ***@***.***>
Cc: dwdonnelly ***@***.***>; Mention ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Camera Support]: Reolink Wifi doorbell configuration - not working (Discussion #14967)
There's the problem. Change 8554 in your camera to 554
—
Reply to this email directly, view it on GitHub <#14967 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKDT7COKFIB3XWK3HGSCNP32FIFLHAVCNFSM6AAAAABRXSADHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJVGAYTKMI> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKDT7CIY7FIVSGSC4XJCDC32FIFLHA5CNFSM6AAAAABRXSADHWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAWA64O.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
Yes – the link below works.
From: clsferguson ***@***.***>
Sent: Thursday, December 12, 2024 2:38 PM
To: blakeblackshear/frigate ***@***.***>
Cc: dwdonnelly ***@***.***>; Mention ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Camera Support]: Reolink Wifi doorbell configuration - not working (Discussion #14967)
I also missed the port in the link.
***@***.***:554/h264Preview_01_sub
and try connecting to the links with vlc.
—
Reply to this email directly, view it on GitHub <#14967 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKDT7CIHVLEXWNW75LZBGY32FIF27AVCNFSM6AAAAABRXSADHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJVGAYTQNQ> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKDT7CPART2RLPYOPYHUU3L2FIF27A5CNFSM6AAAAABRXSADHWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAWA66U.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
Web ui is not set to https? That is done …where…here – see attached photo.
Deselect https?
From: clsferguson ***@***.***>
Sent: Thursday, December 12, 2024 2:40 PM
To: blakeblackshear/frigate ***@***.***>
Cc: dwdonnelly ***@***.***>; Mention ***@***.***>
Subject: Re: [blakeblackshear/frigate] [Camera Support]: Reolink Wifi doorbell configuration - not working (Discussion #14967)
No, need to verify the web ui isn't set to https
—
Reply to this email directly, view it on GitHub <#14967 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKDT7CIY5Q2C7CYECQMQU2L2FIGFFAVCNFSM6AAAAABRXSADHWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJVGAZDANI> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKDT7CKRMZWLBGNEFVPO2L32FIGFFA5CNFSM6AAAAABRXSADHWWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAWA672.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
@clsferguson and all: Just following up to see what suggestion you might have? |
Beta Was this translation helpful? Give feedback.
-
|
The blinking red dot means motion is currently detected. Can you please provide latest logs to see why recordings are not working |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 Thanks for the red dot information. I have been monitoring the camera via VLC, and soo no motion - or anything that would cause a motion activation....so a bit puzzling why the motion indicator is active - if there is no motion.....? Logs follow:
go2rtc:
|
Beta Was this translation helpful? Give feedback.
-
|
You missed scrubbing some passwords. |
Beta Was this translation helpful? Give feedback.
-
|
@clsferguson Thanks. That happens from time to time. Corrected. |
Beta Was this translation helpful? Give feedback.
-
|
i got a reolink wifi doorbell which i manged to wire up. streams: also vlc doesn't work well with mine but ffmpeg via cli works fine |
Beta Was this translation helpful? Give feedback.
-
|
@levski Thanks for the information. While my doorbell is currently wifi based and powered via the old doorbell power source, I plan to have it wired (not POE) via a LAN cable in late April (well - that is the plan anyway?!). With that being said, in comparing your configuration: to mine: Are you not using ffmpeg? Or you just left that line out? Also, with the exception of the different IP addresses (based on one's own overall configuration), I initially tried the 554 port, but that did not work. I see another difference: "..../h264Preview_01_main" where mine is "..../h264Preview_01_sub". So I adjusted to your suggested configuration, saved and restarted. ok then.....a change has occurred...in a positive way - I think. There are far less errors and warnings in the logs. Logs follow: go2rtc: Video results: and
As you can see in the logs, I am trying to select different options: Hence I injected some errors/warnings. So - why is frigate not recording? Many thanks for all the help !! And Happy Holidays! |
Beta Was this translation helpful? Give feedback.
-
|
in your screenshot recordings are disabled to be clear |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 Yes, you are correct. And I cannot figure out how to enable it. (Spoiler alert: I figured it out!) Ok - in reviewing this Common recording configurations and this Configuring the Recording Role I adjusted the configuration by adding in the following code: See full config follows: Now the record button is active NICE! And it is recording! YA! Definitely Happy Holidays ! Now, some testing. I need to figure out my storage situation, which is currently an internal question to myself. So - with the video and recording working, I need to pause, run some testing. And while I am doing that....... @NickM-27, @clsferguson , @levski, @agoose77, @PrplHaz4, @hawkeye217 Many happy and safe holidays and many thanks for all your assistance! |
Beta Was this translation helpful? Give feedback.
-
|
took me some time to figure out some of this stuff and by no means do i fully grasp it yet either but here is how i got with setup and working: Door_Bell: since this is all h264, am just passing it along using go2rtc and frigate. |
Beta Was this translation helpful? Give feedback.
-
|
@levski Many thanks! Working it! |
Beta Was this translation helpful? Give feedback.
@NickM-27 Yes, you are correct. And I cannot figure out how to enable it. (Spoiler alert: I figured it out!)
Ok - in reviewing this Common recording configurations and this Configuring the Recording Role I adjusted the configuration by adding in the following code:
See full config follows: