Closed felipecrs closed 1 year ago
More details:
Oh no! I think I'm connecting to my camera using its wi-fi interface even though it's wired! I'll check this.
Could that be the reason of the issue?
Could that be the reason of the issue?
One of my reolink cams (Reolink Duo 2) has a much worse time over WiFi producing a lot of these errors meanwhile on ethernet it is rock solid
Ok, update:
Very surprisingly, my camera uses the same mac address for both wi-fi and ethernet. I could probably reset it in the Tuya app so that it would lose the wi-fi credentials, however, I decided to just configure my access point to block wi-fi access to its mac address.
I'll monitor now if the issue comes back.
Ok... the issue happens even when I'm 100% sure that it's connected over ethernet. =/
And I think this is expected (not to be related to wi-fi in my case), because my wi-fi connection is very strong and reliable. I have other 2 cameras connected through wi-fi (different model however) that never triggers this RTSP wrong input issue.
2023-02-01 17:33:17.325867081 14:33:17.323 INF go2rtc version 1.1.0 linux/amd64
2023-02-01 17:33:17.325957193 14:33:17.323 INF [api] listen addr=:1984
2023-02-01 17:33:17.325961195 14:33:17.324 INF [rtsp] listen addr=:8554
2023-02-01 17:33:17.325963577 14:33:17.325 INF [srtp] listen addr=:8443
2023-02-01 17:33:17.325965735 14:33:17.325 INF [webrtc] listen addr=:8555
2023-02-01 17:34:14.742230610 14:34:14.741 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://admin:12345@192.168.1.33:554/0/av1
2023-02-01 17:34:23.900767023 14:34:23.900 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://admin:12345@192.168.1.33:554/0/av1
2023-02-01 17:34:24.215586332 14:34:24.215 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://admin:12345@192.168.1.33:554/0/av1
2023-02-01 17:34:24.595960394 14:34:24.594 WRN github.com/AlexxIT/go2rtc/cmd/streams/producer.go:132 > error="RTSP wrong input" url=rtsp://admin:12345@192.168.1.33:554/0/av1
And I think this is expected (not to be related to wi-fi in my case), because my wi-fi connection is very strong and reliable.
Not speaking of your case but I'd say that's not really the case. In my example I was testing the reolink camera on a desk in the same room as my WiFi router. I don't think (at least in my case) it has to do with bad WiFi just how the data is sent.
also, RTSP Wrong Input
means that the camera is sending invalid TCP packets
I don't think (at least in my case) it has to do with bad WiFi just how the data is sent.
I see. That's a valid point.
also, RTSP Wrong Input means that the camera is sending invalid TCP packets
Oh crap. I hope the only solution for this issue isn't replacing its firmware then.
I need access to this stream.
There you go:
rtsp://admin:12345@179.106.189.52:63499/0/av0
@felipecrs I believe AlexxIt meant access to a live stream from the camera directly
Well... isn't that what I sent? lol
There is no response from your stream. You can use ngrok tunnel and send link in private msg. Check contacts in github profile.
Sorry about that. I'm suffering of a major outage from my ISP, that's why it must not be working for you. I'll let you know once my ISP stabilizes.
It's back on business now, if you want to try.
Does this camera work anywhere at all? It sends all sorts of garbage at the place where the frame should end. Maybe it only works in UDP mode.
Well... yes. This RTSP wrong input just keeps popping in my go2rtc logs, but it appears to be working normally. Also, I'm using this very same camera in Frigate since years, when there was no go2rtc.
But, if you think it's not worth to spend more time on it, don't worry, I'm okay 😅
I mean, even in go2rtc it appears to be working normally if I don't check the logs.
Maybe with local connection it can work better. Even via TCP. I think frames should be read very fast.
Alright, thanks a lot for the investigation anyway. Can I close this issue and disable the port forward to the camera on my router then?
Ok
Hi, I have 10 cameras but only one of this model (INQMEGA IL-PTZ381-2M-C: https://aliexpress.com/item/4000780447748.html), and it keeps causing go2rt to send this in the logs:
It mentions
av0
, but if I removeav0
from my go2rtc config and putav1
instead, it errors the same but withav1
now.I did my best to isolate the issue. This is the minimal config and environment to reproduce it:
https://user-images.githubusercontent.com/29582865/216083346-4269f618-4556-4893-8669-636064f69f41.mp4
Logs: