Yes true. Please read it again. There are at least two different pieces of RTSP firmware available. The Wyze branded one would phone home. The Dafang Hacks version I mentioned would not. (Where would it be phoning?)
Oh didnāt notice that. But who is going to put a 4rd party software on their cam. Who knows whatās in the program unless it is open source
It is open source. Itās hosted on GitHub.
Iād like this too. Iām running a Synology mesh network and. Synology diskstation. I donāt think Synology is that great, but I know the respective devices well now and will stay until theyāve peeved me off for the last time.
OP in iiib t
Well, a spirited discussion at least.
The latest RTSP-enabled firmware for the WyzeCam v2 (4.28.4.49) seems pretty solid so far (only released on Nov 20). Audio now included! OK, maybe Iāve been away from Wyze RTSP for a whileā¦ In my testing the camera continued to function and was accessible over RTSP even when its access to the Internet was blocked. But without the ability to address it through an API or console thereās no way to configure it. The phone app is the only way to do that, and it is dependent on Internet access. Iāve got my cameras on their own VLAN, isolated from the main VLAN where all our computers, printers, etc live ā but thatās mostly for local network performance reasons. I do regularly access the RTSP cameras from my laptops or desktops, either directly with VLC or smplayer, or through a management app like Shinobi (if you go there, use the premade docker container ā believe me, youāll be glad you did).
As for the Dafang Hacks, I just spent most of today trying to get that solution to work ā without success. The process required downgrading the firmware to a really old version that had to be retrieved with the help of the WayBack Machine, because Wyze (wisely) doesnāt make anything that old available. After that, thereās a bootloader firmware that had to be installed, which took a couple of tries. Finally, you have to copy the Hacks firmware onto an SDCard and reboot the camera into it by simply inserting and restarting. Got as far as the camera grabbing a (DHCP reserved) IP address and opening up port 80 for the admin web server. But in the end the web server displayed just a blank page and no other ports were opened (in particular, port 22 for the ssh console). So, no joy. But hey, itās third party firmware created by a guy to scratch an itch a few years ago, so thatās sometimes how it goes.
There are a lot of relatively inexpensive wifi cameras on the market. Although the price of a Wyze v2 still has them all beat, even some of the cheaper ones (in both price and build quality) have many of the features many of us have been looking for: like RTSP and web guis for admin and user access. Some even have an ssh console, I donāt see this as a failing on Wyzeās part. Theyāre providing products and services that work just fine for most of their customers (including limited cloud storage for event recordings ā which comes in handy if the camera breaks or disappears). Although I donāt recommend going out and trying to roll your own with a Pi (hard to cost justify), anyone who needs more should probably look into some of those other products.
1 Like
Null route amazon s3 in /hosts. From there install custom firmware or build your own. I wont go into that here. But a more simplified version of the firmware without bloating it more is just setting east2/east s3.amazon.com in hosts to localhost there you go. Now setup tcpdump and run it long enough to capture the packets that has the sekret api key and answer. Now you have a bug bounty. OOPS!
Edit: I left out you will need a linux box with a .so kernel runtime injection listing on SSL. =)
What diskstation you running. I am running ds918+ 40tb/ 16gb ram. I couldnt run 2 cams without it lagging the box down, Upgrading the ram did it. Out of the box they claim it can support 40 cams. Which is just absurdā¦ Just sayingā¦