WebRTC
WebRTC copied to clipboard
Some cameras stuck at loading2 status
I have 7 cameras connected using rtsp. All worked well under 2.x version. Upon updating to 3.0.0, some cameras work, some just display a blank screen and loading2. 6 of them are streams from a single NVR, using the same credentials, 3 work and 3 don't. The card is configured as follows:
type: custom:webrtc-camera
url: rtsp://[USER]:[PW]@[NVR_IP]:554/cam/realmonitor?channel=[CHANNEL_NUM]&subtype=1
ui: true
Check this cameras in go2rtc WebUI
Same problem here:
- 3 Wifi cameras working ok
- NVR with 6 cameras, first one working, five stuck at loading2.
Same advice...
Try this
https://github.com/AlexxIT/WebRTC/issues/386#issuecomment-1399156195
Try this
Disabling backchannel with #backchannel=0 worked, Though I don't know how or why it works. Maybe it should be disabled by default? More documentation on this would be very helpful.
Try this
Disabling backchannel with #backchannel=0 worked, Though I don't know how or why it works. Maybe it should be disabled by default? More documentation on this would be very helpful.
https://github.com/AlexxIT/WebRTC/issues/386#issuecomment-1399167086 - Already been suggested But maybe @AlexxIT can explain the backchanel option
I had no experience with a stream that breaks down completely from the backchannel. Someones need to share that stream with me: https://github.com/AlexxIT/go2rtc/wiki/Tunnel-RTSP-camera-to-Intenet
I experience the same issue with YI Home 720p camera hacked FW. Can view the RTSP stream with mpv
and vlc
. This very camera used to work just fine with versions prior to 3.
Adding #backchannel=0
to the URL didn't solve the problem. I can share the stream for you to investigate.
U have pictures of the camera... Are these your cameras!?
On Mon, Jan 23, 2023, 7:58 PM Constantine Poltyrev @.***> wrote:
I experience the same issue with YI Home 720p camera hacked FW. Can view the RTSP stream with mpv. Can't open with vlc though: Failed to setup RTSP session. This very camera used to work just fine with versions prior to 3. Adding #backchannel=0 to the URL didn't solve the problem. I can share the stream for you to investigate.
— Reply to this email directly, view it on GitHub https://github.com/AlexxIT/WebRTC/issues/389#issuecomment-1401222682, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXRHJ4L7OYP5OUIW2HZ7SLWT4SM5ANCNFSM6AAAAAAUCQQHN4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>
It's my own camera, installed in my daughter room, so I can share the stream only during the daytime when she's not in the room. The camera is described here
@shprota All the hacked cameras have terrible RTSP software. Completely out of standards.
@AlexxIT Quite a few cheap chinese cameras have even worse RTSP conformance, so I think, it is still worth the effort.
I am experiencing the same, I have 2 tabs - 1 for outside cameras and one for inside. On both tabs, there is always 6 cameras (more did not work properly in 2.x). Since migrating to 3.0.1, sometimes some of the inside cameras do not load, sometimes some of the outside cameras do not load. It seems to stuck with restart from some quick testing. Outside cameras are Dahua (Chinese clone) Inside cameras are Tapo C200s.
On first boot, all inside were working and only 1 outside. On second boot, only 4/6 inside were working and 2 outside.
It seems to stuck, even when checking from different devices and only reboot changes it.
I have migrated back to 2.x for now as it is flawless over there.
Cheap Chinese cameras, can usually give a limited number of simultaneous connections. One place where go2rtc can help is if you set it up properly. And only connect to cameras through it.
@AlexxIT i have verified specifically for that case which is not what is happening. Any way I can see more logs?
Installed go2rtc separately in a container, same result. I think, judging by the rest, the problem is when connecting to a nvr with multiple channels. I did not find a way to see logs in more detail that I can share with you.
@cheycron have you checked only WebRTC and only MSE?
Awesome! This issue has been fixed by the latest release. Thanks, Alex!
Still happening on 3.0.1 for me.
I have the same problem with 3.01 4 cam with nvr. But 1 is connecting all the time. Downgrade to 3.0 works.
Same here. Cameras used to work fine using old webcast/rtc. Now just stuck on loading.
It works with the last update. Thx
Which update are you referring to?
From: AFPhome @.> Sent: 09 February 2023 21:34 To: AlexxIT/WebRTC @.> Cc: atv2016 @.>; Comment @.> Subject: Re: [AlexxIT/WebRTC] Some cameras stuck at loading2 status (Issue #389)
It works with the last update. Thx
— Reply to this email directly, view it on GitHubhttps://github.com/AlexxIT/WebRTC/issues/389#issuecomment-1424868495, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEBCFUYJGXRBAZSKCKZQOVTWWVPFZANCNFSM6AAAAAAUCQQHN4. You are receiving this because you commented.Message ID: @.***>
The latest version 3.0.2
Hmm, ok, still can't cast a RTSP stream to any chromecast here.
I confirm the issue has gone away after updating to 3.0.2. Great work!
I'm running into this same issue using several different unifi cameras on v3.1.0 of WebRTC Camera. Checking the cameras in the go2rtc web UI shows that they are registering properly, and clicking on the 'stream' link allows me to stream the video. These cameras were previously working on the prior webrtc backend.
As part of the transition to v3.1.0, I've mapped 8555 tcp/udp back from docker to the host, and forwarded the ports on my router. I've also tried connecting locally via IP instead. Same issue.
Info snapshot from one of the cameras is here. Happy to help debug.
{
"producers": [
{
"type": "RTSP source",
"url": "<snip>",
"remote_addr": "<snip>",
"user_agent": "go2rtc/1.2.0",
"medias": [
"audio, sendonly, 96 MPEG4-GENERIC/48000",
"audio, sendonly, 96 OPUS/48000/2",
"video, sendonly, 97 H264/90000"
],
"tracks": [
"97 H264/90000, sinks=1",
"96 OPUS/48000/2, sinks=1"
],
"recv": 468796
}
],
"consumers": [
{
"type": "WebRTC client",
"user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36",
"send": 472116
}
]
}
Solved this problem by updating HA and WebRTC to the latest versions. Works like a charm now