[Config Support]: Reolink doorbell 2 way audio. Mic not working #10595
-
Describe the problem you are havingI've setup a reolink doorbell over PoE. But when wanting to have a 2-way communication to work. I can only hear the sounds coming from the doorbell. Trying this with a frigate lovelace card in HomeAssistant. Version0.13.2-6476f8a Frigate config filemqtt:
host: 192.168.0.12
user: USER
password: USER
ffmpeg:
hwaccel_args: preset-vaapi
# input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -timeout 5000000 -use_wallclock_as_timestamps 1
# output_args:
# # Optional: output args for detect streams (default: shown below)
# detect: -f rawvideo -pix_fmt yuv420p
# # Optional: output args for record streams (default: shown below)
# record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an
# # Optional: output args for rtmp streams (default: shown below)
# rtmp: -c copy -f flv
detectors:
ov:
type: openvino
device: AUTO
model:
path: /openvino-model/ssdlite_mobilenet_v2.xml
model:
width: 300
height: 300
input_tensor: nhwc
input_pixel_format: bgr
labelmap_path: /openvino-model/coco_91cl_bkgr.txt
go2rtc:
streams:
front1: # <- for RTSP streams
- rtsp://192.168.0.15:554/ # <- stream which supports video & aac audio
doorbell:
- "ffmpeg:http://192.168.0.21/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USER&password=PASS#video=copy#audio=copy#audio=opus"
- rtsp://USER:[email protected]:554/h264Preview_01_sub
doorbell_sub:
- "ffmpeg:http://192.168.0.21/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=USER&password=PASS"
doorbell_snapshot:
- onvif://USER:[email protected]:8000?subtype=MediaProfile00000&snapshot
webrtc:
candidates:
- 192.168.0.12:8555
log:
exec: trace
ffmpeg:
bin: ffmpeg
volume: "-af \"volume=30dB\""
cameras:
front1:
ffmpeg:
inputs:
# High Resolution Stream
- path: rtsp://127.0.0.1:8554/front1
input_args: preset-rtsp-restream
roles:
- record
- detect
input_args: -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1 -c:v mjpeg
output_args:
rtmp: -c:v libx264 -an -f flv
snapshots:
# Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
# This value can be set via MQTT and will be updated in startup based on retained value
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: 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.
# WARNING: Frigate does not currently support limiting recordings based
# on available disk space automatically. If using recordings,
# you must specify retention settings for a number of days that
# will fit within the available disk space of your drive or Frigate
# will crash.
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: 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: 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:
- car
- person
# Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones)
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
################### Doorbell Camera
doorbell:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/doorbell?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/doorbell_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
output_args:
record: preset-record-generic-audio-copy
snapshots:
# Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
# This value can be set via MQTT and will be updated in startup based on retained value
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: 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.
# WARNING: Frigate does not currently support limiting recordings based
# on available disk space automatically. If using recordings,
# you must specify retention settings for a number of days that
# will fit within the available disk space of your drive or Frigate
# will crash.
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: 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: 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:
- car
- person
# Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones)
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: 15Relevant log outputThink this is related to another camera which has doge WiFi connection:
Frigate log:
2024-03-21 19:40:12.627237490 [2024-03-21 19:40:12] frigate.video ERROR : front1: Unable to read frames from ffmpeg process.
2024-03-21 19:40:12.628474188 [2024-03-21 19:40:12] frigate.video ERROR : front1: ffmpeg process is not running. exiting capture thread...
2024-03-21 19:40:16.095078053 [2024-03-21 19:40:16] watchdog.front1 ERROR : Ffmpeg process crashed unexpectedly for front1.
2024-03-21 19:40:16.095081963 [2024-03-21 19:40:16] watchdog.front1 ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2024-03-21 19:40:16.095083633 [2024-03-21 19:40:16] ffmpeg.front1.detect ERROR : [rtsp @ 0x555b37192100] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
2024-03-21 19:40:16.095085178 [2024-03-21 19:40:16] ffmpeg.front1.detect ERROR : Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2024-03-21 19:40:16.095086519 [2024-03-21 19:40:16] ffmpeg.front1.detect ERROR : Output file #0 does not contain any stream
Alot of frameworks passing in the logs
Go2RTC:
frame=46191 fps= 15 q=-1.0 size=N/A time=00:52:14.52 bitrate=N/A speed= 1x
frame=46199 fps= 15 q=-1.0 size=N/A time=00:52:15.04 bitrate=N/A speed= 1x
This seems to be relevant to the doorbell, this seems to be the trying with my mobile phone
Nginx log:
2024-03-21 19:56:54.608727974 192.168.0.11 - - [21/Mar/2024:19:56:54 +0000] "GET /live/mse/api/ws?src=doorbell&authSig=xxxxx HTTP/1.1" 101 264292 "-" "Mozilla/5.0 (Linux; Android 14; CPH2399 Build/UKQ1.230924.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/122.0.6261.119 Mobile Safari/537.36 Home Assistant/2024.1.5-12102 (Android 14; CPH2399)" "192.168.0.2, 192.168.0.12"
2024-03-21 19:56:57.387591539 192.168.0.11 - - [21/Mar/2024:19:56:57 +0000] "GET /live/mse/api/ws?src=front1&authSig=xxxx HTTP/1.1" 101 118852 "-" "Mozilla/5.0 (Linux; Android 14; CPH2399 Build/UKQ1.230924.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/122.0.6261.119 Mobile Safari/537.36 Home Assistant/2024.1.5-12102 (Android 14; CPH2399)" "192.168.0.2, 192.168.0.12"Frigate statsNo response Operating systemProxmox Install methodDocker Compose Coral versionCPU (no coral) Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 22 replies
-
|
should check stream info from system page top right while the mic is active |
Beta Was this translation helpful? Give feedback.
-
|
Okido. What should I notice there? There's quite alot of data on it :) Here I've activated the microphone: I see something with audio send only and receive only ? |
Beta Was this translation helpful? Give feedback.
-
|
seems like this might be a doorbell issue, we can see that data is indeed being sent to the doorbell |
Beta Was this translation helpful? Give feedback.
-
|
I see, thanks for pointing that out. That's strange then because I can communicate (2ways) through the reolink app.... |
Beta Was this translation helpful? Give feedback.
-
|
the reolink app does not use the same mechanism that frigate / go2rtc must, so there could be any number of issues along the way |
Beta Was this translation helpful? Give feedback.
-
|
After adding the it seems I'm getting some extra errors in the logs: |
Beta Was this translation helpful? Give feedback.
-
|
I have heard some reports that the latest update broke two way talk via rtsp |
Beta Was this translation helpful? Give feedback.
-
|
FWIW, I'm on the previous firmware (v3.0.0.2555_23080700) and my 2-way talk is working. |
Beta Was this translation helpful? Give feedback.
-
|
No wayyyyyy :'( Thanks for the heads up tho ! |
Beta Was this translation helpful? Give feedback.
-
|
@supermarkert @NickM-27 I've just downgraded to v3.0.0.2033_23090402. Holy chips the 2 way communication is working ! So indeed the newer firmware kills this :( |
Beta Was this translation helpful? Give feedback.
-
|
Can somebody provide a working firmware version? It seems I cannot download it any longer. @AussiSG @supermarkert |
Beta Was this translation helpful? Give feedback.
-
|
No, I don't have any copies. Looks like you'll have to contact Reolink support. While you're at it, complain to them that they don't keep links to older firmwares on their site. The firmware management on their website is shameful at this point. When I bought my RLC-822A, it came with firmware that was newer than what was available to download for several months. |
Beta Was this translation helpful? Give feedback.
-
|
there is a repo of copies https://github.com/AT0myks/reolink-fw-archive |
Beta Was this translation helpful? Give feedback.
-
|
DB_566128M5MP_P.2033_23041302.Reolink-Video-Doorbell-PoE.OV05A10.5MP.REOLINK.tar.gz |
Beta Was this translation helpful? Give feedback.
-
|
I took this firmware from Reolink and installed it myself to my Reolink Doorbell POE (DB_566128M5MP) , have you checked compatibility with your doorbell before installling? |
Beta Was this translation helpful? Give feedback.
-
|
FWIW My PoE doorbell was on version 3215_2401262241. Reolink support sent me firmware 2676_23090702 that caused a boot loop. I'm guessing the firmware itself is fine on its own, but that the existing newer database on the camera was incompatible with the downgrade. In any case, they exchanged it for a working camera. |
Beta Was this translation helpful? Give feedback.
-
|
Same thing happened to me. I have the PoE doorbell and after trying to downgrade firmware to this one, it got stuck in a boot loop. Anyone have ideas on how to get the 2-way audio working on the newer doorbells? |
Beta Was this translation helpful? Give feedback.
-
|
@soncodi And which firmware do you have on the new camera they sent you? I've just bought a black PoE and I'm on 3215_2401262241. Home Assistant reports a firmware is available (4110_2410111120), not the mobile app and Reolink's website offers it as well as 3308_2407315183. Did anyone try one of those yet ? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
@supermarkert @NickM-27 I've just downgraded to v3.0.0.2033_23090402.
Holy chips the 2 way communication is working !
So indeed the newer firmware kills this :(