-
Notifications
You must be signed in to change notification settings - Fork 17
Trying to work with a WyzeCam -- user/pass supported? #1
Comments
Hi, the RTSP protocol is not implemented in the same way in all the cameras, servers, etc, but it differs slightly, mainly in cameras, since cameras have very low computational power and must use lightweight implementations. Your camera probably uses a RTSP format that this library can't deal with yet, while VLC uses the LIVE555 library to open RTSP streams, that is more versatile and probably is able to communicate with your camera. To solve this problem, it would be helpful to have a network dump, that you can generate in this way:
Attach both files. Thanks |
Thank you, attached are the PCAP captures. One with VLC and two with rtsp-simple-proxy (one in UDP mode and one in TCP mode) Peeking in them a bit, it does look like Wyze is using LIVE555 library on the cameras to provide the stream -- and for some reason it really is 404'ing when trying to get the URI. |
Hi, this should be fixed in fa01182 and v0.2.11: the proxy was ignoring the |
Thank you, that's quite an extensive bit of hacking to churn out in such a short time, wow! It does get a bit farther but still fails with a RTSP code of 454. A PCAP is attached. |
Hi, this should be fixed in a4bd1df and v0.2.12: the problem was that the proxy didn't supported session headers with timeouts, like the one your camera was sending in the SETUP reply:
so the proxy was sending this wrong header in all subsequent requests:
while it now sends the correct one:
well, this is my job so i try to do it the best i can :) let me know if it finally works. |
It's.....WORKING! |
Trying to get this going with a Wyze Cam using their RTSP firmware.
Here is my conf:
And here is the ouput I get:
The same RTSP url works fine in VLC. I've also tried the URL without quotes and double-quotes. Also tried TCP mode.
Any tips?
The text was updated successfully, but these errors were encountered: