Closed jay-kub closed 1 year ago
You need to add #backchannel=0
to the end of the go2rtc stream for the doorbell to disable the two way talk connection
That worked! Thank you so much for the help and for everything you guys are doing to put this great project together.
Where did you find that URL rtsp://REDACTED/Sms=1.unicast for the AD410? Or is that a go2rtc thing? My AD410 is always exceeding fps limit and putting out streams that Frigate/ffpmeg don't like (non-monotonous DTS and such).
Describe the problem you are having
TLDR: after starting Frigate my Amcrest AD410 Doorbell goes into "intercom" mode and no longer functions as a doorbell.
After starting Frigate the Amcrest AD410 stops operating as a doorbell. Pushing the doorbell button does not send a notification to my phone, it does not register a ringing sound to the person at the doorbell, and it does not cause my mechanical doorbell chime to ring. Frigate does receive the rtsp feed from the doorbell camera and functions normally.
After Frigate completes it startup process, the LED status light on the AD410 changes from solid green to solid blue. When the LED is solid blue all doorbell functions listed above cease entirely. When I shut down the Frigate docker container, the LED immediately switches back to solid green and all doorbell functions are restored.
I was unable to find any documentation for the AD410 status lights, but it appears that solid blue LED indicates that the doorbell is in "call" or "intercom" mode. I tested this by shutting down Frigate, ringing the doorbell, and answering the video call notification received via Amcrest. When the call begins the LED status light changes to solid blue and pushing the doorbell button does not elicit any response.
My guess is that the connection from Frigate via go2rtc/rtsp is triggering the AD410 to believe it is in call/intercom mode. When I connect the AD410 to Surveillance Station via rtsp I do not run into the same issues. I'm not sure if this is truly a Frigate issue or if it's go2rtc/Synology, but for what it's worth I did open a ticket with Amcrest who determined that the device needed to be RMAd. Shortly thereafter I came to realize the issue was tied to Frigate. As a workaround I have setup Surveillance Station to receive the rtsp feed and am passing that feed through to Frigate.
Version
0.12.1-367D724
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Amcrest AD410
Any other information that may be helpful
No response