Hello from Wyze and changes from wyze login APIs

[xcz011]

I’m an engineer at Wyze, and I wanted to inform you about some important updates to our Wyze Login API that may affect the docker-wyze-bridge project. As detailed in our recent forum post (Important Wyze App Information - 4/26/24), we will soon be shutting down the v2 and v3 APIs. This decision was made to enhance security and prevent credential stuffing attacks.

We encourage developers to transition to our supported Developer API for login processes. This change will ensure continued compatibility and enhance the security of integrations.

We appreciate the effort you have put into supporting Wyze and our ecosystem through your project. If you have any questions or need further details about the Developer API and how to transition, please feel free to reach out.

Thank you for your understanding and support.

[industrial64]

Can confirm, all Wyze cams and this project are now KIA. Time to ditch Wyze and buy RTSP (Reolink) cameras.
Thanks for the heads up Wyze, but no native RTSP support is the end of you.

[letrain02]

I’m an engineer at Wyze, and I wanted to inform you about some important updates to our Wyze Login API that may affect the docker-wyze-bridge project. As detailed in our recent forum post (Important Wyze App Information - 4/26/24), we will soon be shutting down the v2 and v3 APIs. This decision was made to enhance security and prevent credential stuffing attacks.

We encourage developers to transition to our supported Developer API for login processes. This change will ensure continued compatibility and enhance the security of integrations.

We appreciate the effort you have put into supporting Wyze and our ecosystem through your project. If you have any questions or need further details about the Developer API and how to transition, please feel free to reach out.

Thank you for your understanding and support.

If this makes wyze incompatible with this bridge I will be dumping wyze. Wyze has always been great. Sd card local storage. No requirements for paid monitoring. Security is important however wyze itself even had an rtsp firmware at one time. The ability to see stuff on my phone through an app is a perk. But local streaming to my own display is essential. As long as wyze plays nice with their API I don't see how this could be an issue. I'm more than happy to pay this developer for his services since wyze does not offer this ability itself.

Edit: after reading your post you specifically mention home assistant which uses this bridge for integration. I'm more than happy to donate another $15 to @mrlt8 to get this updated. Which your post has a link to. I use the hls streams for a grafana dashboard which greatly helps checking on things during a typical mid West Winter

[mr-bobdobalina]

Can confirm, all Wyze cams and this project are now KIA. Time to ditch Wyze and buy RTSP (Reolink) cameras. Thanks for the heads up Wyze, but no native RTSP support is the end of you.

I've been testing TP-Link Tapo cameras. They're Wyze-like in that the cameras have local storage and/or cloud storage. They have RTSP built-in (needs to be enabled per camera and you lose cloud saving--no big deal to me) and they're cheap ($15.99 on Amazon right now for the C100 indoor model). I'd say video quality is on par with V3 Wyzecams. Their outdoor model (C120) is a little bulkier than Wyze but still fairly cheap at $29 and it is 2K video (I don't really notice a big difference from 1080p).

Video fed to my Blue Iris server has been SOLID. No drops or connection issues ever so far. Only downside I've found is the indoor models use an old school barrel connector power adapter. I've been thinking of getting a barrel->USB-A cable to see if that would work. The C120 does use USB-C however.

[xcz011]

This project already support newer developer login api and this change is only to retire legacy login api to enhance security.

So this won't break this project in any way.

Thanks

[letrain02]

This project already support newer developer login api and this change is only to retire legacy login api to enhance security.

So this won't break this project in any way.

Thanks

I figured but you never know. Reddit screwed everyone with their API, and many companies do.

I was a lucky one a couple days ago that decided to update which required a restart. Which then required API login. As long as wyze continues this way I will continue to place wyze cameras all over my 30 acres and recommend them to everyone I know.

Like I stated if wyze offered this feature I would use it. And honestly the fact the community is able to develop anything related to it is why wyze is so well used.

API login is easy to use in a docker. @mrlt8 would just have to change his documentation to state that it is required. I'd rather have an API exclusively than a password, but both are fine.

[anthonyjesmok]

I can confirm that the Wyze bridge is working once again with the new Developer API in place. Instructions are located at https://github.com/mrlt8/docker-wyze-bridge/wiki/Two-Factor-Authentication#wyze-api-keyid.

Thank you to the Wyze team for engaging with this project and allowing the developer community to continue creating great additions for their awesome products!

[mathiar86]

Perhaps I’m doing this wrong so could someone please walk me through it. I’ve generated an API key on Wyze but maybe I’m putting the information in the wrong spot.
I keep getting the same 400 client error https://github.com/mrlt8/docker-wyze-bridge/issues/1164

I put the API key into the yaml on the webUI from the add on in HA as per the instructions but no matter what I do it won’t work. I don’t see any cameras (I’ve got 4) and the log keeps showing errors.

Should I be putting the API key somewhere else? I don’t have 2FA set up and my password is simple upper/lowercase and numbers. No special chars or spaces/dashes.

Cameras working fine in Wyze app.

[mr-bobdobalina]

I can confirm that the Wyze bridge is working once again with the new Developer API in place. Instructions are located at https://github.com/mrlt8/docker-wyze-bridge/wiki/Two-Factor-Authentication#wyze-api-keyid.

Thank you to the Wyze team for engaging with this project and allowing the developer community to continue creating great additions for their awesome products!

Got mine working as well, thank you for the link!

[mike2246]

Working too, Thanks!

[mrlt8]

Thank you for the heads up @xcz011! I noticed the official app switched to oauth back in September so figured this would eventually happen.

I'll update the documentation to indicate that the API key and ID are no longer optional but required now.

Several users have also noticed some issues connecting to cameras when on a separate network. Can you confirm if the p2p and relay mode for tutk have been disabled on all 2024 firmware?

[cheme75]

Just curious if the keys/IDs are required if not using 2FA for wyze?

I doubt I'll use my v2 cams at new house. I only have the original db setup right now. Anyway seems like a big hassle just for one db.

[mike2246]

Yes, I got api only. No 2fa

[cheesegrits]

@xcz011 thank you for reaching out. It's good to see Wyze engaging with third party projects like this.

[vitosans]

I’m an engineer at Wyze, and I wanted to inform you about some important updates to our Wyze Login API that may affect the docker-wyze-bridge project. As detailed in our recent forum post (Important Wyze App Information - 4/26/24), we will soon be shutting down the v2 and v3 APIs. This decision was made to enhance security and prevent credential stuffing attacks.

We encourage developers to transition to our supported Developer API for login processes. This change will ensure continued compatibility and enhance the security of integrations.

We appreciate the effort you have put into supporting Wyze and our ecosystem through your project. If you have any questions or need further details about the Developer API and how to transition, please feel free to reach out.

Thank you for your understanding and support.

Thanks for popping in and giving us the heads-up. RTSP might be out of your control, but it's appreciated that you help us navigate issues you might see.

[xcz011]

@mrlt8 I am not aware p2p relay change from my understanding, I will double check on that.
@cheme75 my understanding is keys/ID will be required no matter of 2FA or not.

And appricated all of you to understanding of this.
Feel free to close this issue whenever, Thanks again !!

[mrlt8]

Thank you @xcz011, I believe the connection issue may be related to B-44285 since we're still able to connect when on the same LAN.

B-44285: Unable to connect to live stream when not on local Wi-Fi

However, connecting from another network or without a VPN will result in:

OTC_Connect_ByUIDEx[-42]... "IOTC_ER_FAIL_SETUP_RELAY"

It seems to be firmware related since downgrading the cameras seems to fix the issue for most people.

[awilbourn]

My question is, why does the docker image still want the WZYE_EMAIL and WZYE_PASSWORD if we set the API_ID and API_KEY, seems like it would not be needed, but not able to get in without it.

[xcz011]

My question is, why does the docker image still want the WZYE_EMAIL and WZYE_PASSWORD if we set the API_ID and API_KEY, seems like it would not be needed, but not able to get in without it.

@awilbourn https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key wyze developer login api require to pass username, password, Keyid, Apikey. So docker image is correct