Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RuntimeError: Request failed, error 3005:UnauthorizedOperation #25

Open
backslashV opened this issue Aug 3, 2021 · 6 comments
Open

Comments

@backslashV
Copy link

I am unable to push the firmware to my cam v3. Current firmware version: 4.36.0.280

@krhainos
Copy link

krhainos commented Aug 4, 2021

Are you experiencing the same problem from this post? HclX/WyzeHacks#132

Wyze recently changed the API and now compares the firmware upgrade against a list of approved URL's. While this doesn't make installing WyzeHacks or WyzeCameraLiveStream impossible, it does make it a lot more challenging. My unit initially shipped with 4.36.0.280 and I was able to install successfully on a Wyze Cam V3 by altering the url and spoofing the dns reply as described in this reply from that same issue.

I had downgraded mine to 4.36.0.228, but I'm not completely sure if that was necessary for a successful installation.

Good luck, and let us know if you're able to install on 4.36.0.280 without downgrading first.

@backslashV
Copy link
Author

Thank you for your response. Yes, it's the same issue. I didn't really understand anything from the response you linked. Not sure what steps to follow here for DNS spoofing. Also, I don't have physical access to the camera so downgrading the firmware, if it's thru an SD card, is not an option for me.

@krhainos
Copy link

krhainos commented Aug 4, 2021

The process to install WyzeHacks and/or WyzeCameraLiveStream, as I understand it, involves interacting with Wyze's API servers to instruct the camera to download a firmware image. Previously, the API processed requests to have cameras download firmware images hosted anywhere, such as from the HTTP instance the scripts starts up (which would be located at say, http://192.168.1.3/firmware.bin).

Recently, Wyze's API will now only process firmware download requests where the URL matches real locations where they keep them (such as http://d1fk93tz4plczb.cloudfront.net/wuv2/upgrade/WLPP1/firmware/1.2.0.80a.bin). To get past this hurdle, wyze_updater.py needs to be modified, and the DNS server upstream from your Wyze camera needs to be reconfigured so d1fk93tz4plczb.cloudfront.net resolves to the computer you're running remote_install.sh from.

The issue is still open in WyzeHacks, and there's people looking at it that understand it better than I do. I'd expect an update once this new development is fully understood.

@krhainos
Copy link

I'd like to add that I installed this on the rest of my cameras, and forgot to downgrade from 4.36.0.280. The hack appears to install fine without downgrading to 4.36.0.228, and can confirm at least the H.264 stream on port 12345 and telnetd are operational.

@davidfrankks
Copy link

Anyone have a link to a working firmware, i rolled all the way back to 4.36.0.125 and still get the same error. Guessing they patched it out.

@alexqzd
Copy link

alexqzd commented Sep 20, 2021

This worked for me HclX/WyzeHacks#132 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants