RTSP for V3

cpu utilization: 93%

That’s the reason I stopped using tinycam pro’s webserver.

Well I was streaming the baseball game and watching Netflix at the same time as running the Tinycam in the background and had no issues…

Good information. Thanks Captn.

FYI: TinyCam users. I believe this is correct. " Usually every modern cameras has at least two video profiles: main-stream profile (e.g. 1080p@30fps) and sub-stream profile (e.g. 720p@10fps). Main-stream is used when you need the highest stream quality, sub-stream when you need to lower bandwidth usage. If you use mobile data on the phone it is recommended to select sub-stream.

If auto-stream profile in the app selected, sub-stream will be used in multiple cameras layout, main-stream in single camera layout."

ANDROID Box CPU Power comparison. https://androidpctv.com/comparative-rockchip-rk3566/

I am using the S905X3, cpu that is a couple years old and have no issues running TinyCam server 24/7.

As I am looking into newer technology, the above comparison, does NOT rate the newer S905X4.

But, top of the line in cpu power seems to be the Tegra and S922 in comparison, and they are probably the higher-priced Android boxes. If you search Google for a ask S905 x 4 processor versus the two high-end processors above you may be able to get more bang for your buck.

The things that I look to have in a new Android box is a 1000 megabit per second network connection, 2.4/5Ghz wifi and Bluetooth connectivity in case you want to Bluetooth a keyboard or Mouse.

Compare cpu here Amlogic S905X4 vs Rockchip RK3566 - GadgetVersus

Thank Noel,
I tried out what you had described, but getting the following errors on startup:

rename your cams to one eight letter all small and try again, no spaces

Thanks CaptainKirk - renamed, and looks like a slightly different error, but eventually ends the same:

Starting rtsp-server …
Recreating wyze-bridge …
Recreating wyze-bridge … done
Starting rtsp-server … done
Attaching to wyze-bridge, rtsp-server
rtsp-server | 2021/07/12 19:13:14 I [0/0] rtsp-simple-server v0.16.4
rtsp-server | 2021/07/12 19:13:14 I [0/0] [RTSP] TCP listener opened on :8554
rtsp-server | 2021/07/12 19:13:14 I [0/0] [RTMP] listener opened on :1935
rtsp-server | 2021/07/12 19:13:14 I [0/0] [HLS] listener opened on :8888
wyze-bridge | STARTING DOCKER-WYZE-BRIDGE v0.3.1
wyze-bridge | Fetching user data from local cache…
wyze-bridge | Fetching auth data from local cache…
wyze-bridge | Fetching auth data from wyze…
wyze-bridge | Fetching user data from wyze…
wyze-bridge | Fetching cameras data from local cache…
wyze-bridge | Fetching cameras data from wyze…
wyze-bridge | STARTING ALL 2 CAMERAS
wyze-bridge | 2021/07/12 19:13:26 [drive#1] Starting HD 120kb/s Stream for WyzeCam V2 (WYZEC1-JZ) running FW: 4.9.6.241 from 10.0.0.124 (Wifi: -28 dBm)…
wyze-bridge | 2021/07/12 19:13:26 [doorbell] Starting HD 120kb/s Stream for WyzeCam DOORBELL (WYZEDB3) running FW: 4.25.0.244 from 10.0.0.188 (Wifi: -60 dBm)…
rtsp-server | 2021/07/12 19:13:30 I [0/0] [RTSP] [conn 172.18.0.2:34154] opened
rtsp-server | 2021/07/12 19:13:30 I [0/0] [RTSP] [conn 172.18.0.2:34154] ERR: invalid URL (rtsp://rtsp-server:8554/drive#1)
rtsp-server | 2021/07/12 19:13:30 I [0/0] [RTSP] [conn 172.18.0.2:34154] closed
wyze-bridge | 2021/07/12 19:13:30 [drive#1] [FFMPEG] [Errno 32] Broken pipe
wyze-bridge | 2021/07/12 19:13:30 [drive#1] Killing FFmpeg…
wyze-bridge | 2021/07/12 19:13:41 [drive#1] Starting HD 120kb/s Stream for WyzeCam V2 (WYZEC1-JZ) running FW: 4.9.6.241 from 10.0.0.124 (Wifi: -29 dBm)…
rtsp-server | 2021/07/12 19:13:46 I [0/0] [RTSP] [conn 172.18.0.2:34156] opened
rtsp-server | 2021/07/12 19:13:46 I [0/0] [RTSP] [conn 172.18.0.2:34156] ERR: invalid URL (rtsp://rtsp-server:8554/drive#1)
rtsp-server | 2021/07/12 19:13:46 I [0/0] [RTSP] [conn 172.18.0.2:34156] closed
wyze-bridge | 2021/07/12 19:13:46 [drive#1] [FFMPEG] [Errno 32] Broken pipe
wyze-bridge | 2021/07/12 19:13:46 [drive#1] Killing FFmpeg…
wyze-bridge | 2021/07/12 19:13:57 [drive#1] Starting HD 120kb/s Stream for WyzeCam V2 (WYZEC1-JZ) running FW: 4.9.6.241 from 10.0.0.124 (Wifi: -33 dBm)…
rtsp-server | 2021/07/12 19:14:03 I [0/0] [RTSP] [conn 172.18.0.2:34158] opened
rtsp-server | 2021/07/12 19:14:03 I [0/0] [RTSP] [conn 172.18.0.2:34158] ERR: invalid URL (rtsp://rtsp-server:8554/drive#1)
rtsp-server | 2021/07/12 19:14:03 I [0/0] [RTSP] [conn 172.18.0.2:34158] closed
wyze-bridge | 2021/07/12 19:14:03 [drive#1] [FFMPEG] [Errno 32] Broken pipe
wyze-bridge | 2021/07/12 19:14:03 [drive#1] Killing FFmpeg…
wyze-bridge | 2021/07/12 19:14:14 [drive#1] Starting HD 120kb/s Stream for WyzeCam V2 (WYZEC1-JZ) running FW: 4.9.6.241 from 10.0.0.124 (Wifi: -29 dBm)…
rtsp-server | 2021/07/12 19:14:19 I [0/0] [RTSP] [conn 172.18.0.2:34160] opened
rtsp-server | 2021/07/12 19:14:19 I [0/0] [RTSP] [conn 172.18.0.2:34160] ERR: invalid URL (rtsp://rtsp-server:8554/drive#1)
rtsp-server | 2021/07/12 19:14:19 I [0/0] [RTSP] [conn 172.18.0.2:34160] closed
wyze-bridge | 2021/07/12 19:14:19 [drive#1] [FFMPEG] [Errno 32] Broken pipe
wyze-bridge | 2021/07/12 19:14:19 [drive#1] Killing FFmpeg…
wyze-bridge | 2021/07/12 19:14:30 [drive#1] Starting HD 120kb/s Stream for WyzeCam V2 (WYZEC1-JZ) running FW: 4.9.6.241 from 10.0.0.124 (Wifi: -21 dBm)…
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [conn 172.18.0.1:57364] opened
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [conn 172.18.0.1:57364] ERR: no one is publishing to path ‘doorbell’
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [conn 172.18.0.1:57364] closed
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [conn 172.18.0.1:57370] opened
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [session 6308724] opened by 172.18.0.1:57370
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [conn 172.18.0.1:57370] ERR: path must end with a slash (doorbell)
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [conn 172.18.0.1:57370] closed
rtsp-server | 2021/07/12 19:14:34 I [0/0] [RTSP] [session 6308724] closed

They made revisions to the Git site. If you are using the old version you should re-clone the repository

This does not mention if the RTSP firmware will or will not be supported on V2 or V3 when it arrives… wondering if the TUTK protocol will also work following this “update” coming…

Starting on July 21st, 2021 , we will start gradually releasing camera firmware updates that will not be compatible with Wyze app versions 2.21 or lower but are important for keeping up with best security practices. Without updating, you will no longer be able to access your camera devices after they update to the newer versions.

We will be postponing the change to the minimum operating system (OS) versions until after the first 2.22 update due to feedback about needing more time to find compatible devices. In case you missed it, we announced that we will stop supporting older OS versions here and emailed folks that may be impacted. This change will still occur due to requirements for upcoming features and other important changes coming later.

Yes, while it is clear that retaining old firmware will probably allow continued use of old apps, what is NOT clear to me is whether the service itself will just stop working if you don’t update firmware.

It will happen eventually but I don’t know if this is that time.

Edit: Okay, upon reading the e-mail message it appears they are not going to ban old firmware from the network at present.

Starting on July 21st, 2021 , we will start gradually releasing camera firmware updates that will not be compatible with Wyze app versions 2.21 or lower but are important for keeping up with best security practices.

waiting… waiting… and keep on waiting for the past few months…

Coming in next 3-4 months per reddit AMA.

let’s hope so…

They litterally said that as I said “per reddit AMA”…

Where is the RTSP firmware for Version 3?

Wyze just KEEPS SAYING RTSP Firmware for v3 is coming in 3 months…thats what they said 6 months ago. I bot v3s in January and there is no RTSP as advertised and promised…NOTHING…NADA…I guess I will have to be giving my opinion on social media…and doing some youtube videos and Amazon reviews about this.

I sold all my junk to somebody else all but 1 camera. Let it all be someone else problem. It’s hilarious to still see no rtsp implementation. I wonder if enough people got burbed by this for a class action lawsuits. All of the products are complete fails. Scale doesn’t give the same result when you step on it and varies ±15lbs the “smartwatch” still doesn’t sync with google fit as far as I know making it pretty much useless not to mention the other stuff pro.ised that never came with the watch. The window/door sensors had a bug that caused the devices to stop working completely when the battery dies. The wyze cams were supposed to get rtsp firmware and months and months later everyone is still waiting.

The company is complete trash selling trash products with high failure rates, design flaws, missing features, and misleading advertising.

When I tried to place returns for all this junk either the website wouldn’t allow it, or support is down, or they aren’t taking returns, etc, etc.

This should honestly be a slam dunk for a decent lawyer.

1 Like

Well, all my reviews did do something.

I was an early adopter and purchased a couple of Cam V3. A nice upgrade from the Cam V2 except that there’s NO RTSP support. I had planned to purchase several more once it was added. However, like many others, my patience is running very thin and ready to give up and go another route.

1 Like