go2rtc: RTSP wrong input / Frigate beta 7 + go2rtc
I am currently using go2rtc within frigate beta 7 and have noticed that while everything seems to come up fine and work for hours I am seeing string of RTSP wrong input particularly from my tp-link tapo cameras, they seem to sometimes get permanently STUCK in this state… A full restart of frigate seems to cause go2rtc to connect to them again.
I am wondering if this may be caused by intermitted network/wifi connectivity issues bumping them offline but they then just don’t recover clearly.
go2rtc:
webrtc:
candidates:
- 192.168.102.30:8555
- stun:8555
streams:
doorbell:
- rtsp://admin:{FRIGATE_RTSP_PASSWORD2}@192.168.103.8:554
- "ffmpeg:doorbell#audio=opus" # transcodes audio to opus for webrtc compatibility
basement:
- rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.4:554
- "ffmpeg:basement#audio=opus" # transcodes audio to opus for webrtc compatibility
living_room:
- rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.5:554
- "ffmpeg:living_room#audio=opus" # transcodes audio to opus for webrtc compatibility
kitchen:
- rtsp://admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.7/live
- "ffmpeg:kitchen#audio=opus#audio=aac" # transcodes audio to opus for webrtc compatibility
basement_hall:
- rtsp://tapo_admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.145/stream1
- "ffmpeg:basement_hall#audio=opus#audio=aac" # transcodes audio to opus for webrtc compatibility
main_hall:
- rtsp://tapo_admin:{FRIGATE_RTSP_PASSWORD}@192.168.103.225/stream1
- "ffmpeg:main_hall#audio=opus#audio=aac" # transcodes audio to opus for webrtc compatibility
garage_front:
- http://192.168.103.3/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password={FRIGATE_RTSP_PASSWORD}
backyard:
- http://192.168.103.2/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password={FRIGATE_RTSP_PASSWORD}
2023-02-02 11:45:35.339488071 11:45:35.339 INF go2rtc version 1.1.1 linux/amd64
2023-02-02 11:45:35.339770467 11:45:35.339 INF [api] listen addr=:1984
2023-02-02 11:45:35.340120865 11:45:35.340 INF [rtsp] listen addr=:8554
2023-02-02 11:45:35.340510247 11:45:35.340 INF [srtp] listen addr=:8443
2023-02-02 11:45:35.340735038 11:45:35.340 INF [webrtc] listen addr=:8555
2023-02-02 12:03:23.769565472 12:03:23.769 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="read tcp 192.168.102.30:46402->192.168.103.225:554: i/o timeout" url=rtsp://tapo_admin:*********@192.168.103.225/stream1
2023-02-02 12:03:23.892670242 12:03:23.892 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error=EOF url=ffmpeg:main_hall#audio=opus#audio=aac
2023-02-02 12:03:27.455087637 12:03:27.454 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:03:27.686624697 12:03:27.685 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error=EOF url=ffmpeg:kitchen#audio=opus#audio=aac
2023-02-02 12:03:28.671849336 12:03:28.671 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="read tcp 192.168.102.30:34162->192.168.103.7:554: i/o timeout" url=rtsp://admin:********@192.168.103.7/live
2023-02-02 12:03:31.048918045 12:03:31.048 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="read tcp 192.168.102.30:47430->192.168.103.8:554: i/o timeout" url=rtsp://admin:******@192.168.103.8:554
2023-02-02 12:03:35.508684009 12:03:35.508 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:03:36.986237015 12:03:36.985 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:03:39.991208029 12:03:39.990 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:05:44.122643248 12:05:44.111 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:05:47.646200531 12:05:47.645 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:05:51.251384499 12:05:51.251 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
2023-02-02 12:05:57.224034165 12:05:57.222 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://tapo_admin:*********@192.168.103.145/stream1
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 1
- Comments: 30 (15 by maintainers)
Jump over wrong packets in release, but this is not total fix yet https://github.com/AlexxIT/go2rtc/releases/tag/v1.1.2
@AlexxIT I just tried with a camera that has known packet issues via WiFi (previously would lead to many RTSP wrong input) and the stream has not gone down since using the master version
I don’t mind improving support for cheap glitchy cameras. I just can not repeat these problems in my own.