I do not currently care about the lag time because:
I am recording to an NVR
This is not a real time intrusion detection system
I have configured my system to be automated
There is no need for me to be notified of motion, but there is need for me to have good evidence of events
If the trade off is good video quality versus a few seconds in a buffer, I’ll take the good video quality.
Also, to @dusthead, using ffmpeg isn’t crude. It’s clever. My software of choice, Netcam Studio, can automatically take images and generate timelapse, but I’m testing the capabilities right now.
I’m almost certain I’m running into this same issue with 3 cameras. I already have a pretty well saturated 2.4 band with about 70 devices (echos, smart switches, lights, sensors, etc) connected at any given moment. Running motioneye with 2 wyze cameras (on 360p) and 1 IP cam was semi stable, but I noticed that Home Assistant wasn’t acting as snappy anymore and automation’s began failing sporadically. Asking alexa to turn on/off something would result in a 50/50 chance of getting “I’m sorry device name isn’t responding…”
My setup includes:
3 Wyze V2 Camera’s
Home Assistant and motionEyeOS running in docker on an i3 Nuc with 8GB of RAM
I was considering getting another AP. It looks like our Unifi AC Pro AP’s can be meshed together. I believe I could add 2 more, and they could each cover the other wifi channels. I was thinking about getting another one and running everything on another channel, but still this channel could get saturated as well… hard to say.
I have the delay, connection loss, and frame-skip issue. I’m using Blue Iris. unchecking “Skip initial HTTP DNS and reachability tests” in the Network IP configuration page of Blue Iris helped a bit, but not entirely.
It was the same as the beta but we have an update expected in the next week. I don’t know if there will be any feature changes but we do plan to have function improvements.
AlbanyHDTV, It varies depending on your router, but you have to go into the port forwarding section on your router settings. From there, you make the Wyze cameras static IP address so it never changes. Once you’ve done that, you forward the ports for each camera. The Wyze cameras use port 554 for RTSP. So for each cameras IP address you forward internal port 554 and make up an external port for each one such as 10554 11554, 12554, etc. For example say your first camera’s IP address is 192.168.1.110, on the router port forwarding section, you would forward external port 10554 and internal port 554. next camera would be external 11554 and internal 554, etc. Once all that is set up, you can use a camera viewing app to view the cameras using your home IP address instead of the internal 192.168.x.x address.
Just installed the 2.3.60 iOS beta. Updated 2 of my 4 WyzeCam 2’s to the latest firmware 4.19.4.48. All works well, and I have RTSP streaming to my AppleTV & iPhone with no issues. I love it! However, the camera that I didn’t upgrade the firmware on now won’t authenticate (tries 10 times & times out). That camera is running firmware version 4.9.4.37, which is the current production version. I’ll go ahead & upgrade the firmware to match the others (a little harder to do since it’s outdoors & up high). Just thought the team might want to know.
I do really appreciate Wyze listening to customers and implementing RTSP. I was able to get it to work with the IPcam Viewer Pro app on my iPhone, which was the goal so I could view the Wyze Pan in one place with my other cameras. However, for now, I reverted back to the standard firmware since it’s a bit too buggy. It drops frequently and has no pan and tilt controls, plus, although it’s compatible with Wyze Sense, I also get Wyze bridge drop outs. I may try again with the expected RTSP update, but for now, the standard firmware channel just seems much better.
The support for RTSP should enable more broad integration with the growing field of home automation. I have played around with many home automation devices and software since the early 1990’s. The WYZE product line is very promising and I am glad to see interest in this area.
Currently, I am working with Wyze, Insteon, Amazon Echo Devices, SONOS, SmartThings, ActiveTiles and TP-Link devices.
Please ensure a main stream and sub stream, so the WYZE cams can be used with Blue Iris which is an excellent pc based NVR: http://blueirissoftware.com
(FYI: I don’t work for or sell BI or have any connections to their company).
I just know it to be a well established and popular NVR solution for expensive CCTV cams such as Dahua, Hikvision etc over ethernet, although I believe there’s no reason it can’t use WiFi as well, and it would seem to offer an ideal low cost solution to Wyze owners without the need for an additional app.
I believe the current cost is $29 for a single cam version or $49 for multi-cam, with 1 yrs included support, and although continuing support costs $29.95 per year after the 1st year, you can use it unsupported so the initial cost is one off. The additional yearly costs are only payable if you either want their support or the latest version (without support you can’t get new versions).
From other CCTV forums, I know this to be one of the best off the shelf solutions for a lower budget and it may alleviate the need for Wyze to develop their own viewing app if the WYZE cams can be made BI compatible.
My software of choice, Netcam Studio, can automatically take images and generate timelapse, but I’m testing the capabilities right now.
