HclX / WyzeHacks

Hacks I discovered allowing Wyze camera owners to do customizations
MIT License
789 stars 75 forks source link

Unable to get hacks to install. remote_installer.sh confirms firmware bin was pushed, but no change from cam #39

Closed cr08 closed 3 years ago

cr08 commented 3 years ago

So I have a few v2's in my house, about half have SD cards, the others do not. So far tested on 2 cams with no SD cards installed (one cannot due to, I assume, a failed SD card slot or connecting hardware. The rest of the cam is fully functional). After doing some trial and error I have come as far as having the remote_installer script work and confirming the cam has pulled the firmware from the local server but the camera doesn't reboot, no audible announcements, and the live feed from the Wyze app continues to run.

Currently operating from an Ubuntu WSL install on my Windows 10 v2004 machine. All dependencies properly installed, python 3.8.2.

I started with the most recent FW version, 4.9.6.199 for the v2's but even downgraded to the noted last confirmed working version on the README page of 4.9.6.156 just to rule things out. Both do the same. Even tried rebooting the cams amidst all this. Here's a snippet below of the script on one cam I have attempted to hack.

Device type: Camera (WYZEC1-JZ) Device name: Kitchen Firmware version: 4.9.6.156 IP Address: 192.168.1.167

Pushing firmware to this device? [y/N]:y INFO:root:Serving firmware file './firmware.bin' as 'http://192.168.1.107:11808/firmware.bin', md5=68e279ca2d3208bbb55111ac6d38c432 192.168.1.167 - - [24/Oct/2020 15:31:51] "GET /firmware.bin HTTP/1.1" 200 - INFO:root:Checking device, mac=XXXXXXXXXX

Any thoughts on where I should look next or additional troubleshooting steps I can try? Ultimately I'd like to remove the SD cards altogether and just have everything fed over NFS and leave it at that.

cr08 commented 3 years ago

Never mind. Closing this out. PEBKAC error. I'm so used to cloning repos directly especially if no binaries are involved. Grabbed the zipped release linked on the front page and utilized it and it is fine. Apparently there's enough different between that and the full repo clone to cause issues despite it looking like it completed everything ok.