Not sure if this is specific to the streaming library but I've noticed that if I prevent the V3 from accessing the internet after about an hour the stream stops and I can no longer connect to it.

I can still ping the camera and it seems to continue to record to the SD card. If instead I allow the V3 to access the internet the stream seems to work indefinitely.

Is it possible to use the live stream and also keep the V3 off the internet?

Been trying to install this onto my v3 cam but it doesnt seem to work. I never hear the camera say "installation begins" like the directions say. After i click yes on my camera it just presents a bunch of dots .............. and my camera blinks blue/red/purple until i press CTRL+C. Ive left it in this state for about 30m and it still never did anything. Any help?

Trying to install this on a WyzeCam3 [wyze_hacks_0_5_06.zip] Ubuntu 18.04 Made sure Python3 installed Made sure python-pip installed

When I try to run ./remote_install.sh I get this.

Found local config file, including into firmware update archive... Upgrade/config.inc /usr/bin/python3: No module named pip Traceback (most recent call last): File "./wyze_updater.py", line 294, in help='Supported actions') File "/usr/lib/python3.6/argparse.py", line 1716, in add_subparsers action = parsers_class(option_strings=[], **kwargs) TypeError: init() got an unexpected keyword argument 'required'

Help would be appreicated

I have no issues viewing the feed in VLC with "vlc http://192.168.0.225:12345 --demux h264" However BlueIris doesn't seem to play well with the stream

This is my configuration:

192.168.0.202 - BlueIris 4.8.4.7 x64 192.168.0.225 - Wyze Cam v3

BlueIris says "No signal"

the stream_hack.log is looping with this:

CRB: Waiting... CRB: Accept... CRB: New client: 192.168.0.202 CRB: read failed, stopping client CRB: New client finished. CRB: Waiting... CRB: Accept... CRB: New client: 192.168.0.202 CRB: read failed, stopping client CRB: New client finished. CRB: Waiting... CRB: Accept... CRB: New client: 192.168.0.202 CRB: read failed, stopping client CRB: New client finished. CRB: Waiting... CRB: Accept... CRB: New client: 192.168.0.202 CRB: read failed, stopping client CRB: New client finished. CRB: Waiting... CRB: Accept... CRB: New client: 192.168.0.202 CRB: read failed, stopping client CRB: New client finished. CRB: Waiting...

Howdy, and thanks for this software. I'm trying to install this on my v3 with 4.36.3.19 installed. I don't think it's able to install over newer firmware (the dots just keep running in the installer ......, after 20 minutes I thought it was safe to ctrl + C out). The wyze app shows the camera working, and showed a firmware update - from 4.36.2.5 to 4.36.3.18.

No ports appeared open on the camera (no TCP ports, there were about 8 UDP ports open - definitely no 23 Telnet, no 12345 either) so I'm guessing the camera just rolled back to it's default firmware - or am I doing something wrong, or I'm not installing it correctly? Do I need an sd card installed in the camera perhaps? Thanks for any advice offered.

I then stupidly completed the Wyze firmware update 4.36.2.5 to 4.36.3.18, which then prompted to install 4.36.3.19, which I did. Attempting to install your custom firmware results in the firmware now staying at 4.36.3.19. I believe the newer firmware is locked down and denies 'rolling back' to custom firmware. Perhaps I need to try an SD card update?

Hi Charlie, I noticed the wyze app was saying that the camera did not have an SD card installed, and was able to confirmed that nothing was being mounted to /media/mmc.

I can see my SD card in /dev/mmcblk0p1 and was able to manually mount it to /media/mmc, but it still doesn’t get notice by the app or persist on reboot.

SD card does get mounted/recognized on the latest vanilla wyze_hacks. Same issue on two cams with the stream_hack installed.

Camera firmware: 4.9.6.241 No Wyze Cam Plus subscription.

Direct stream from camera and live view on the Wyze app work great, but motion tagging (green box around motion) is not working and motion events are not getting uploaded to the Wyze cloud when the hack is enabled.

Disabling the hack by commenting out the LD_LIBRARY_PATH in /system/init/app_init.sh restores the motion tagging and Wyze cloud events.

Hello and thanks for putting this thing together!

I'm having some trouble installing the new hack.

I believe the install.sh from sonic.net is trying to pull the libimp.so from GitHub so it fails since wget on the camera doesn't support https.

I commented out the GitHub link and it seems to install, but then the camera doesn't come back up after a reboot (solid orange light).

Here's the install log:

+ STREAM_HACK_OUTPUT=/tmp/stream_hack.log
+ [ -z  ]
+ WYZE_APP_OUTPUT=/dev/null
+ [ -z /tmp/stream_hack.log ]
+ [ -z  ]
+ STREAM_HACK_VERSION=current
+ [ -z  ]
+ STREAM_HACK_LIB=crb.users.sonic.net/current/libimp.so
+ dir=/configs/stream_hack
+ rm -rf /configs/stream_hack
+ mkdir /configs/stream_hack
+ wget -O /configs/stream_hack/libimp.so crb.users.sonic.net/current/libimp.so
Connecting to crb.users.sonic.net (209.204.190.65:80)
libimp.so            100% |****************************************************************************************************************************| 27780   0:00:00 ETA
+ [ -w /configs/wyze_hack.sh ]
+ wrap /configs/wyze_hack.sh
+ grep stream_hack /configs/wyze_hack.sh
+ echo #!/bin/sh
+ echo export LD_LIBRARY_PATH=/configs/stream_hack:$LD_LIBRARY_PATH
+ echo export STREAM_HACK_PORT=
+ echo export STREAM_HACK_P2P=
+ echo export STREAM_HACK_OUTPUT=/tmp/stream_hack.log
+ echo /configs/wyze_hack.sh.orig >& /dev/null &
+ chmod +x /configs/wyze_hack.sh /configs/wyze_hack.sh.orig
chmod: /configs/wyze_hack.sh.orig: No such file or directory
+ grep -w -c ro
+ grep -w /system /proc/mounts
+ system_read_only=0
+ [ -w /system/init/app_init.sh ]
+ [ 0 == 0 ]
+ wrap /system/init/app_init.sh
+ grep stream_hack /system/init/app_init.sh
+ echo #!/bin/sh
+ echo export LD_LIBRARY_PATH=/configs/stream_hack:$LD_LIBRARY_PATH
+ echo export STREAM_HACK_PORT=
+ echo export STREAM_HACK_P2P=
+ echo export STREAM_HACK_OUTPUT=/tmp/stream_hack.log
+ echo /system/init/app_init.sh.orig >& /dev/null &
+ chmod +x /system/init/app_init.sh /system/init/app_init.sh.orig
chmod: /system/init/app_init.sh.orig: No such file or directory
+ echo Stream hack installed.
Stream hack installed.

Hey there, thank you for this wonderful work!

While testing this out with VLC, it appears to have about 1s latency from camera to VLC.

Do you happen to know the cause of this? The IMP_Encoder_GetStream -> crb_tcp_hook path seems reasonable to me and I don't see any buffers there (and it seems to run off the encoder thread?). I am suspicious that this is VLC buffering things too aggressively, as the app-based streaming seems faster.

I had this working before, but today I wanted to add this to 2 more cameras and I'm getting these errors below, ending in Broken Pipe....

Can someone tell me what could be the issue with this?

Thanks for putting this together!

Not really an issue, more of a question.
I got the stream working on a v3 with both vlc and mpv. Now trying to feed the stream into Blue Iris. Any idea how to configure a BI camera to accept the h264 stream?

Just tested the new wz_mini_hack and it works great, you can get SSH root access on latest FW. https://github.com/gtxaspec/wz_mini_hacks but the original installation is not working cd /configs wget crb.users.sonic.net/current/install.sh chmod +x install.sh ./install.sh

With Wyze forcing all cams to update to the latest firmware by end of January, I went ahead and bit the bullet and am updating to 4.36.8.15 on my V3 cams. The good news is that WyzeCameraLiveStream still works with it, sometimes. There are a few things that can happen when you enable the hack:

1. The cam will refuse it and might go into a boot loop until you disable it
2. Sometimes the cam does not reboot, and so using VLC will allow me to see the video feed as usual, except now you can't view it on the Wyze app

I believe the rootfs is updated from when this hack was created so that may or may not have something to do with it.

As of December 28 2021 the WyzeCameraLiveStream still works

just downgraded from RTSP firmare to 4.36.0.228

installed DNS server using Dnsmasq following this guide: dnsmasq spoofing

my dns server: 192.168.1.245 ( raspberry pi 4 using raspbian lite ) running script: 192.168.1.143 ( Ubuntu in VM ) here I installed wyze_hacks_0_5_08.zip

run dnsmasq or some other DNS server and spoof s3-us-west-2.amazonaws.com to the computer you will run the script from. In my case, I used a rasbperry pi for dns serving. This involved (1) adding a line to hosts of s3-us-west-2.amazonaws.com 192.168.11.4 (2) changing the DNS server choice on the DHCP server to the ip of your spoofing DNS server (in my case 192.168.11.11)

Manually set the url inside the to http://s3-us-west-2.amazonaws.com/wuv2/upgrade/WLPP1/firmware/1.2.0.80a.bin

The port used must be port 80 (since it's checking urls I doubt it will work with another port). Note that the default port if you use remote_install.sh is not 80 On OSX, I had to use sudo to avoid getting "PermissionError: [Errno 13] Permission Denied"

Flashing command: sudo python3 ./wyze_updater.py --token ~/.wyze_token --debug update -m WYZEC1-JZ -m WYZECP1_JEF -m WYZE_CAKP2JFUS -m WYZEDB3 -f ./firmware.bin -p 80

WYZE blocked wyze_hack scripts (read about it here) and made getting the wyze_hack fw much difficult (you need DNS spoofing). I was able to get the wyze_hack fw on my V3 camera and I can telnet to the camera. Can I manually install using the new install script? on my camera running system_read_only=$(grep -w /system /proc/mounts | grep -w -c to)
gets system_read_only= 1 so I need only to wrap /configs/wyze_hack.sh and get the new libimp.so

Is that correct?