Closed trevor-s8 closed 1 year ago
I'd suggest upgrading go2rtc to 1.5.0
I'd suggest upgrading go2rtc to 1.5.0
Hi, thanks I will give it a try.
I see the instructions for upgrading here https://docs.frigate.video/configuration/advanced/#custom-go2rtc-version
Do you happen to know which build to use for Unraid Docker deployments? https://github.com/AlexxIT/go2rtc/releases/tag/v1.5.0
Whichever one matches your CPU arch, most likely amd64
Whichever one matches your CPU arch, most likely amd64
Thanks. Unfortunately even with 1.5 installed I still get the same error. Using the GUI, I went to the go2rtc dashboard and clicking the stream there is no video with the error
mse: dial tcp 192.168.42.99:554: connect: no route to host
That error means the camera is not online at that IP address
That error means the camera is not online at that IP address
Right, normally. But I can confirm that is the IP address of the camera, and it works in frigate v11 with ffmpeg
In v12, there is something blocking the connection
No there is not, go2rtc can't reach the camera then it can't reach the camera.
You could always try ffmpeg in go2rtc as well and of course using the go2rtc restream for frigate is not required either
No there is not, go2rtc can't reach the camera then it can't reach the camera.
When I get back home I’ll show the v11 logs showing it works with no other changes.
I’ll try the second suggestion, but again, there is audio in the recordings, just no video.
I don’t see how there can truly be no route to host if I am getting audio from the camera
I've had funky issues with the camera/doorbell severely malfunctioning if your running it with go2rtc without the backchannel turned off. The backchannel turned on tells the camera that there should be active 2 way audio and it seems to sit in higher power state its not designed to sit at from what I can tell. Just add #backchannel=0 to the end of the go2rtc rtsp line (I don't use the substream for it, but I'd add it to both), restart frigate, then restart the doorbell and hopefully all will be well.
Just add #backchannel=0 to the end of the go2rtc rtsp line
You will want to do this regardless, if you don't the doorbell button doesn't work because it thinks there is a call active. Might also solve your video issue. I have the same doorbell but haven't noticed this behaviour.
If that doesn't work, whats your doorbells firmware? I saw talks of the latest firmware being dodgy and breaking peoples setups.
Mine is currently Eng_N_V1.000.0000000.7.R.20210220 and works fine
I've had funky issues with the camera/doorbell severely malfunctioning if your running it with go2rtc without the backchannel turned off. The backchannel turned on tells the camera that there should be active 2 way audio and it seems to sit in higher power state its not designed to sit at from what I can tell. Just add #backchannel=0 to the end of the go2rtc rtsp line (I don't use the substream for it, but I'd add it to both), restart frigate, then restart the doorbell and hopefully all will be well.
Just add #backchannel=0 to the end of the go2rtc rtsp line
You will want to do this regardless, if you don't the doorbell button doesn't work because it thinks there is a call active. Might also solve your video issue. I have the same doorbell but haven't noticed this behaviour.
If that doesn't work, whats your doorbells firmware? I saw talks of the latest firmware being dodgy and breaking peoples setups.
Mine is currently Eng_N_V1.000.0000000.7.R.20210220 and works fine
Apologies for the late reply. After adding this it appears things are working in a more stable way. Thank you!
I'm stuck with AD410.
Because I don't understand why in FRIGATE, I can't see the stream in high quality and also I can't see any audio stream.
So I guess that if I record something from my doorbell, I can't heard nothing.
Please can you help me for my config?
########################################## MQTT SERVER E DB
database:
path: /home/frigate.db
mqtt:
host: 192.168.178.81
user: mqtt_user
password: mqtt_user
topic_prefix: frigate
client_id: frigate
########################################## GOOGLE CORAL USB
detectors:
coral:
type: edgetpu
device: usb
########################################## GLOBAL SETTINGS
ffmpeg:
hwaccel_args: preset-vaapi
input_args: preset-http-reolink
output_args:
record: preset-record-generic-audio-copy
objects:
track:
- person
record:
enabled: True
birdseye:
enabled: True
mode: objects
detect:
width: 896
height: 672
fps: 5
enabled: True
snapshots:
enabled: True
live:
quality: 1
########################################## GO2RTC
go2rtc:
streams:
ingresso:
- ffmpeg:http://192.168.178.179/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=mypass
ingresso_sub:
- ffmpeg:http://192.168.178.179/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=mypass
camera_da_letto:
- ffmpeg:https://192.168.178.34/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=mypass
camera_da_letto_sub:
- ffmpeg:https://192.168.178.34/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=mypass
balcone_grande:
- ffmpeg:https://192.168.178.117/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=mypass
balcone_grande_sub:
- ffmpeg:https://192.168.178.117/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=mypass
studio:
- ffmpeg:https://192.168.178.30/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=mypass
studio_sub:
- ffmpeg:https://192.168.178.30/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=mypass
veranda:
- ffmpeg:https://192.168.178.163/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password=mypass
veranda_sub:
- ffmpeg:https://192.168.178.163/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password=mypass
AD410:
- rtsp://admin:mypass@192.168.178.98:554/cam/realmonitor?channel=1&subtype=0#backchannel=0
AD410_sub:
- rtsp://admin:mypass@192.168.178.98:554/cam/realmonitor?channel=1&subtype=1#backchannel=0
########################################## CAMERE
cameras:
ingresso:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/ingresso?video=copy&audi=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/ingresso_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
camera_da_letto:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/camera_da_letto?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/camera_da_letto_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
balcone_grande:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/balcone_grande?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/balcone_grande_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
studio:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/studio?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/studio_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
veranda:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/veranda?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/veranda_sub?video=copy
input_args: preset-rtsp-restream
roles:
- detect
AD410:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp://127.0.0.1:8554/ad410
input_args: preset-rtsp-restream
roles:
- record
# Low Resolution Stream
- path: rtsp://127.0.0.1:8554/ad410_sub
input_args: preset-rtsp-restream
roles:
- detect
detect:
width: 640
height: 360
fps: 15
I can see bad quality and no audio. I renamed CAMPANELLO in AD410 for you.
You need to select a different live view type other than jsmpeg
My urls for the doorbell are different from yours too.
Main: rtsp://username>:<pass>@<ip:554#backchannel=0 Sub: rtsp://username>:<pass>@<ip:554/cam/realmonitor?channel=1&subtype=1#backchannel=0
Sorry for the offtopic question people, but did someone of you AD410 owners manage to get 2-way comm working in go2rtc?
I am close, but I am stuck at the point where there's no way to get the client (Desktop, mobile, tablet, whatever) microphone enabled when the WebRTC stream is running...
are you using a browser with https connection to go2rtc?
@NickM-27 no the go2rtc (v1.7.0) is running in the Frigate container so straight HTTP.
https is required for two way talk, like it says in the go2rtc docs.
I believe there is a dev tool in chrome to disable this requirement
@NickM-27 oohhhhh didn't know that thanks!
I believe there is a dev tool in chrome to disable this requirement
OK I do a search for it now tnx.
https is required for two way talk, like it says in the go2rtc docs.
Me again.
I actually forgot that I had already go2rtc running in HTTPS. 🤦🏼
The Chrome dev setting is enabled and the host was added to the list, mic is on and its red icon shows up while running the webRTC stream, but no audio comes out from the doorbell.
Describe the problem you are having
After a short time of running, go2rtc seems to lose access to my Amcrest AD410 video doorbell camera for recording. Audio continues to work in the recordings.
Version
0.12.0-da3e197
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
UNRAID
Install method
Docker Compose
Coral version
PCIe
Network connection
Wired
Camera make and model
Amcrest AD410
Any other information that may be helpful
Seemed to work fine in v11 but I unfortunately don't have logs back that far to verify