-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go2rtc media player not working with Reolink camera #562
Comments
Thanks for putting that patch together, and sorry for not noticing it sooner (I expected to get notified, so I hadn't been watching the issue 🤷🏻♂️). I grabbed the go2rtc master build. I'm no longer seeing the 400 errors on the |
Try to update firmware for your doorbell. Also check this issue #331 |
OK. Looks like I was wrong about it not working. It does work, but the audio clip I was sending was too short. The first second or so of audio seems to be clipped, and the doorbell only starts playing audio after that. The audio clip I was using was only about a second of TTS, so it just got completely clipped off. Additionally, the audio cuts off before getting to the end of the message. So if, e.g., I have a 5 second audio clip, the doorbell only plays the middle 3 seconds or so. In the logs, I see a |
OK. This is another issue. Will check it with my camera |
@ebroder Could you post your logs from getting some audio to play from the doorbell? I have the same configuration as yours but I can't get any audio file to play. It always fails with
so I want to compare your logs with mine. |
Yeah sure - you can see the logs here: https://gist.github.com/ebroder/3cc8e08dbadbd4645196c3ce88c8c10a I'm just using the developer tools to call |
I have a Reolink Doorbell and am trying to setup a media player entity through go2rtc so that I can send messages from the TTS service.
Currently, if I open the "video+audio+microphone" stream, I'm able to trigger talkback to the camera. However, I haven't been able to get the media player entity to work.
I've uploaded my go2rtc.yaml, the stream info from when I'm successfully able to talkback using the browser, stream info from when TTS is unable to successfully talkback, the relevant snippet of my HA configuration.yaml, and the logs from the go2rtc service here: https://gist.github.com/ebroder/b6d6d7753e994d49b43c1d47689d6b06
I specifically noticed that, after the go2rtc client issues the
PLAY
request to the Reolink RTSP server, it gets back a400 Bad Request
, but I don't understand RTSP well enough to know why that's happening.The text was updated successfully, but these errors were encountered: