You have 2way audio working with this config? What does your custom:frigate-card conf look like please?
What’s the best way to get the camera feed to pop-up in PIP mode on Android (Shield) TV when the doorbell is pressed?
I’m using Frigate and Scripted on Proxmox integrated with HA.
Thanks
I use PipUp
Is it possible to use the Reolink Integration for HA with Microphone /2Way audio working with a fast connection? Currently using Frigate. But Microphone is not working on iOS. Also, the stream is very fast via webrtc.
You can play the webrtc using dashcast.
My Reolink POE doorbell is connected to my HA via Reolink integration.
I have setup an automation , when bell is pressed it will send the “camera.reolink_video_doorbell_poe_fluent” stream to Google home max media player.
The automation works, but the problem is, the video feed that streams to Google Home Max has a significant delay. Once the bell button is pressed , it takes about 5 to 10 seconds to show the video feed and the video feed that is shown is not live but a stream that happened 10 to 15 seconds ago.
Apologies if the above issue has already been reported above and I might have missed a solution given.
If some one can point me to the right direction please.
Hey Craig can you please share your Frigate config file for the Reolink doorbell? I am crashing constantly.
1 Like
One thing I did to ensure I had a good power connection was to upgrade my doorbell transformer to a 24v-40A model like this one: https://www.amzn.com/B08JC4PW8M
With the lower voltage transformers you may have reboots our outages due to voltage drop on the small doorbell wires. Here is my Frigate config:
go2rtc:
streams:
doorcam:
- "ffmpeg:http://*CAMERAIP*/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=*USER*&password=*PASSWORD*#video=copy#audio=copy#audio=opus"
- "rtsp://*CAMERAIP*/Preview_01_main#audio=opus"
doorcam_sub:
- "ffmpeg:http://*CAMERAIP*/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=*USER*&password=*PASSWORD*"
- "rtsp://*CAMERAIP*/Preview_01_sub#audio=opus"
cameras:
doorcam:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp://*GO2RTCIP*:8554/doorcam
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://*GO2RTCIP*:8554/doorcam_sub
input_args: preset-rtsp-restream
roles:
- detect
live:
stream_name: doorcam_sub
detect:
width: 640
height: 480
fps: 4
3 Likes
This doorbell uses PoE, no need for a doorbell transformer.
I can’t say for sure, but if I were to make an educated guess/bet, I’d say yes.
The responsiveness in Homekit, for example, with feed directly from Scrypted is instant. I don’t let Home Assistant touch any streams of the camera except on its dashboard and then only via Scrypted.
Scrypted has Google support so you should be able to do a direct connection like I have with Homekit.
1 Like
The are multiple versions of the doorbell
Hey there, a question for everyone that already got two way adudio working. what’s the delay on the backchannel? for me, everything i’ve tried seem to make my streams from the doorbell to the computer go just fine (<500ms delay) but the delay for the audio from my mic to the doorbell is MASSIVE (>2000ms)
is this normal for this configuration or do yours work better?
Hi,
I need help, I cannot get 2-way audio working.
HA Green
HA Core 2024.2.5
Reolink firmware v3.0.0.2033_23041302
Frigate 0.13.2 with its internal go2rtc 1.8.4
Frigate integration 5.1.0
Frigate card.
NGINX NPM add-on for HTTPS.
Fully Kiosk Browser on Android (using HTTPS). Microphone permissions are given to FKB. A green dot is displayed on the Android upper left corner.
I can see the camera image and hear the sound from the Frigate card.
There is a microphone button on the Frigate card (muted).
When I touch the microphone button, it changes state.
But when I talked to the Android app, no sound comes out of the doorbell.
Can you help me ?
(everything between starts* is anonymised)
frigate.yml:
mqtt:
host: *IP* # YOUR MQTT IP
port: 1883
topic_prefix: frigate
client_id: frigate
user: *myuser* # YOUR MQTT USERNAME
password: *mypass* # YOUT MQTT PASSWORD
stats_interval: 60
go2rtc:
streams:
reolink_sub:
- rtsp://*user:pwd*@*IP*:554/h264Preview_01_sub
- ffmpeg:reolink_sub#audio=opus
reolink_main:
- rtsp://*user:pwd*@*IP*:554/h264Preview_01
- ffmpeg:reolink_main#audio=opus
cameras:
reolink:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp://127.0.0.1:8554/reolink_main
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/reolink_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
enabled: False
live:
stream_name: reolink_sub
Frigate card:
type: custom:frigate-card
cameras:
- camera_entity: camera.reolink
live_provider: go2rtc
go2rtc:
modes:
- webrtc
stream: reolink_sub
menu:
buttons:
microphone:
enabled: true
alignment: matching
type: toggle
timeline:
enabled: false
cameras:
enabled: false
frigate:
enabled: false
download:
enabled: false
media_player:
enabled: false
mute:
enabled: true
alignment: matching
camera_ui:
enabled: false
substreams:
enabled: false
live:
enabled: true
clips:
enabled: false
snapshots:
enabled: false
style: overlay
position: left
button_size: 80
live:
controls:
thumbnails:
mode: none
auto_mute: all
preload: false
microphone:
always_connected: false
dimensions: {}
media_gallery:
controls:
thumbnails:
size: 140
show_favorite_control: false
show_timeline_control: false
show_download_control: false
filter:
mode: none
Hi everyone,
Has anyone had success creating a “media_player” for sending custom sound to the Reolink Doorbell and could share an example?
I’m totally lost about how can I reproduce an mp3 file over it.
3 Likes
There’s one version of the PoE doorbell, not including enclosure color - which is specifically what the thread is about.
Sure, but it’s pretty obvious when talking about transformers that the WiFi doorbell is being referred to and saying there’s only one version of the doorbell is incorrect and can be misleading
Not really…
The POE version also can be powered by a transformer!
1 Like
What’s the subject/topic of this thread? “Reolink Doorbell POE”
No one’s talking about a wifi doorbell. And it doesn’t matter how this doorbell is powered, the important thing is that it’s WIRED and that Reolink only has a single version of it.