Is there any word on plans for fixing the RTSP issues? This is still a beta firmwire right?
I really wish they’d respond about this particular issue. The RTSP feature was much requested and it’s not up to par in it’s current state. If lowering the frame rate would keep the stream from lagging behind and jumping around, I’d much rather have that as an option in the app, or they simply lower it until the camera can give a smooth stable framerate. From their forum posts, it sounds like they really tried to set it to the edge of the framerate and made the bad call of releasing it with lag and jitter.
I get the same when i try to open a stream from VLC … but when i use the rtsp-URL from a browser, my browser ask whether i want to open it in VLC and that works…
It’s in beta. Expecting perfection on the first try is a bit unreasonable don’t you think?
1 Like
Reading the title it’s launched - NOT beta.
There is a place for beta.
Perhaps it should be relegated back there.
RTSP is no longer beta. It was released last week.
Yeah, this is why I’m speaking up. If it was still in beta, then totally fine. They announced many times that they will not be updating the firmware, so given the information they’ve supplied this means this is it.
Fixed my issue. My Unifi AP went haywire and I had to reset it. Everything is working now, albeit quite slowly…
I’m always amazed at people who want to be early adopters, and then complain about being an early adopter… And in some cases, repeatedly complain about it.
2 Likes
Wyze has implemented RTSP control into the released versions of the app but, as far as I can tell, the RTSP firmware will always be beta.
1 Like
They download page used to have a big red label that said “Beta.” They removed that. At the top of this thread they said:
As of 4/24/19, RTSP has been launched!
Well then I guess your stuck with the released version as it is. 
Open source firmware may be a better solution. I haven’t tried it.
None of the open source stuff is good, unfortunately.
We are working on an update for RTSP to improve it from its current state. But I don’t have much information about that since I’m not very involved with feature development.
3 Likes
Just sharing some info on the Lag issue.
I received my 2nd wyze yesterday, installed the same RSTP firmware on the same SDcard as my first cam (did not re-download).
my 2nd camera has NO LAG, first one does.
the 2nd camera also has a crisper cleaner image.
the bit rate in the top of the image (and in BlueIris) show 130-170 kb/s for Camera 2
camera 1 has the lag, and a dirtier image
the bit rate in the top of the image (and in BlueIris) show 24-50 kb/s for Camera 1
wyze app camera settings > info > wifi signal 82% for BOTH CAMERAS
wyze app quality on HD (supposedly) for BOTH CAMERAS
BlueIris is also showing camera 1 max frame settings at 10 fps but struggles to do 8.5 frames incoming.
BlueIris shows camera 2 set for 10 and consistently receives 10 fps
hmmm…
mesh network. both cameras are close to access point. good signal.
When I use the Wyze app to change from HD to SD or 360P
NOTHING HAPPENS on camera 1 . No change to image quality…
I think this is broken, perhaps it does not change after flashing the RSTP firmware???
but works fine on camera 2… camera 2 is running perfect rstp.
confused.
I purchased 6 cameras and quickly realized that the issue here is 2.4ghz wifi. Our network becomes completely saturated (99% according to my AP) with MotionEye/Zoneminder watching every camera. Our only fix was to have our software only watch about 3 cameras total, then use the Wyze app for the rest. This seemed to alleviate the network issues. If these had USB ethernet support or 5ghz wifi chips there would be no issues.
2 Likes
Hi there. This is Arthur from Wyze.
Since its release, the RTSP firmware had been downloaded to more than 2000 devices. Thank you all for supporting this feature, and sincerely I am sorry for some ongoing issues that undermine its performance.
The current RTSP version is still the beta version. We received many valuable feedback, and we are working on fixes. The updated version is scheduled to release around May 8th.
Here is a list of what we know and what we are doing:
A. Connection drop:
- I received 16 reports on this issue, mostly with Blue Iris, iSpy and Motion Eye.
- Symptom: As the RTSP connection drops, Live View is still good, and the feed could be restored by turning off and on the RTSP toggle, or by rebooting the camera.
- I received error code 800274D from Blue Iris. Our engineer suspects it was caused by Router functions that limits local network data flow, such as Airtime Fairness, advanced setting for Netgear & Asus routers.
- We are currently testing a new version of firmware with all the mentioned players to see if we could prevent this issue.
- For some user, this issue was solved by:
(1). Adding the cameras (e.g. to Motion Eye) as RTSP/UDP camera
(2). Switch to RTSP over TCP
(3). Blue Iris settings example: https://global.discourse-cdn.com/wyze/original/2X/d/da2686bb28abfe958c6d95f539185a69ac753ea8.png
B. Other devices in the same network drop offline when RTSP is on:
- I received 5 reports on this issue. It does not always happen, and resolved automatically in the next day.
- All users stated that their network should have more than enough bandwidth.
- Our engineers suspect it could be caused by:
(1). Conflicting IP address or other router related settings
(2). Overall network usage is too high. - We are trying to reproduce this issue, but not yet achieved. If you are in similar situation, please send me the camera Mac address and the type of router you are using to hzuo@wyze.com. Thank you.
- For some user, this issue was solved by:
(1). Assign static IP or reserve DHCP for the camera to avoid possible conflicts.
(2). Change video resolution to SD or 360P
C. Frame Skip
- This issue refers to “stuttering” video that jumps every few seconds. This issue happens mostly to iSpy and PotPlayer, and in one case Omxplayer on Raspberry Pi.
- It happens when the player did not complete playing the 2 seconds of each video clip, before the new clip (i-frame) came in and refreshed the video, skipping several not-yet-played frames.
- Suspected causes:
(1). video player software limiting frame rate to lower than 15fps to preserve CPU usage, but this does not always produce the “stuttering” effect.
(2). Player or device issue causes decoding and playing to be slower than necessary.
(3). Connection not stable, bit rate fluctuated to lower than necessary level periodically. - We are testing some changes to improve this issue.
- For some user, this issue was solved by:
(1). Switching to other players (e.g. VLC)
(2). Increase buffer size / video caching time.
(3). Change video resolution to SD or 360P
D. Delay, comparing to Wyze App Live View
- I received many reports on this, but only less than 10 users reported longer than 5 second delay.
- According to our engineer, the implementation of RTSP data transmission would require it to buffer 2~3 video clips (2 second each) before sending one out. That is 4~6 seconds in buffering. Comparing to Wyze App Live View feed that sends out every frame and buffers less than 2s, RTSP would be 2~5 seconds behind.
- Currently we do not know how to reduce it beyond 2~5 seconds. We are collecting reports on longer than 5 seconds delays, and we should be able to fix that part.
- For some user, longer than 5 second delays was solved by:
(1). Changing video quality to SD or 360P, and reducing player caching time.
Thank you for reading through this. We are definitely working on improving the RTSP version of firmware, but it will take time, especially that the cause to some of the issues are unknown and we have not yet reproduced it in our office.
If you run into any of the above issues, or if you have experience solving any of them, please post it here.
If it involves personal or device information, please send it to hzuo@wyze.com.
Thank you.
Arthur.
14 Likes
Very happy to have RTSP available now! I put it on all 3 of my cameras. I was hoping still images would be enabled in a final release? Many users are resorting to crude methods like a script that uses ffmpeg to save a still to a local folder, or relying on MotionEye’s still images it produces.
1 Like
Thank you for the detailed explanation.
Why is it in “launched” status rather than still in under “testing”?