You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Reolink camera with a proprietary stream protocol and I'm using Neolink (as a docker image) to convert it to RTSP. Sometimes when the camera is not in use, I turn it off (unplug it). In this case, go2rtc starts failing completely on an assert and exits. That disrupts all my cameras, as all go through go2rtc.
This behavior started I believe after 1.2.0. Reverting to 1.2.0 mitigates this.
If the Neolink instance is down, it fails on "dial tcp x.x.x.x:554: connect: no route to host" and this doesn't bring the whole go2rtc instance down, only triggers a retry on the stream.
I believe what's happening is, that neolink is probably creating a rtsp stream which is "empty" when the camera is down, and go2rtc can't handle that. It would probably be the best if if the assertions didn't bring the whole instance down, only the stream that's faulty.
I am trying to add 2 Reolink Lumus cameras to Go2RTC in Frigate via Neolink as the OP did with his Reolink. I currently have them working in the Generic Camera integration at "rtsp://192.168.1.100:8554/camera_name" and in Frigate with this as the path under "cameras". Note: 192.168.1.100 is my Home Assistant URL. What are the syntax to include them in Go2RTC and then in cameras in Frigate?
I tried "rtsp://192.168.1.100:8554/camera_name" with or without the port in streams and " path: rtsp://127.0.0.1:8554/camera_name" under cameras/camera_name
I have a Reolink camera with a proprietary stream protocol and I'm using Neolink (as a docker image) to convert it to RTSP. Sometimes when the camera is not in use, I turn it off (unplug it). In this case, go2rtc starts failing completely on an assert and exits. That disrupts all my cameras, as all go through go2rtc.
This behavior started I believe after 1.2.0. Reverting to 1.2.0 mitigates this.
If the Neolink instance is down, it fails on
"dial tcp x.x.x.x:554: connect: no route to host"
and this doesn't bring the whole go2rtc instance down, only triggers a retry on the stream.I believe what's happening is, that neolink is probably creating a rtsp stream which is "empty" when the camera is down, and go2rtc can't handle that. It would probably be the best if if the assertions didn't bring the whole instance down, only the stream that's faulty.
Here's the stacktrace from the failed assertion:
Thanks
The text was updated successfully, but these errors were encountered: