API certificate issue - Breaks HomeAssistant - please fix your CERT!

Wyze’s API server (api.wyzecam.com) presents a certificate chain rooted at “DigiCert Global Root CA” (G1). Mozilla’s trust program (and Chrome/most platforms) began distrusting this root on April 15, 2026 — it’s an industry-wide, publicly announced distrust event (Microsoft had to migrate M365/Entra off the same root for the same reason). certifi removed the root from its bundle in the 2026.06.17 release. Any client relying on certifi’s CA bundle (rather than an OS-level trust store) — which is what wyzeapy/aiohttp uses by default — will now fail to validate Wyze’s chain.

This is confirmed with openssl against api.wyzecam.com:443 — depth=1 verify error num=20 “unable to get local issuer certificate”, issuer resolves to “DigiCert Global Root CA” which is absent from current certifi.

This is not a client-side bug — Wyze needs to reissue their server certificate through a currently-trusted intermediate (DigiCert offers several: Global Root G2/G3, Trusted Root G4, all already widely deployed). Flagging here so:

I really appreciate you tracking down the root cause and posting this detailed breakdown.

A friend recently warned me that updating Home Assistant would break the Wyze integration, so I’ve been holding off on the update. I was wondering if this was a case of Home Assistant making breaking architectural changes or if the fault lay elsewhere. Thanks to your clarification and the openssl output, it’s clear this is entirely on Wyze for failing to migrate away from a deprecated root certificate ahead of a major, industry-wide distrust event.

Because Home Assistant and its underlying libraries (like aiohttp via certifi) rightly enforce modern security standards, they are just doing their job by dropping the DigiCert G1 root.
I am going to pass this technical breakdown along to some employees at Wyze to ensure it gets flagged internally.

Your conclusion is completely sound: Wyze needs to update their endpoint’s certificate chain to a modern, trusted root (like G2 or G4) to fix this for everyone. Thanks again for the clear summary and posting in here.

I hope Wyze is listenig/reading. I’m on the same predicament. Please take action or at least let us know you are aware and working on it. Thx

This was meant for support. Not the moderator who gave a great reply.

Bump.

It’s a easy fix and would only take a few minutes to deal with but this is wyze.

Not know for responding to the public or fixing bugs when there no profit in it.

Been moving away from them given this behavior as it shows a fundamental disconnect between the users and them.

They don’t seem to understand that just selling the product is only half the equation.

Companies like aqara and reolink get this and work with the buyers which is why people keep buying their products. They get this a long term investment that pays back big for them.

Fingers crossed

One more bump. My giant list of Wyze devices are all offline. I’ve owned Wyze devices since the very first camera. Now none of them are available in Home Assistant. My pages and automations are filled with “Entity not found” and it’s frustrating me into thinking it’s maybe time to cancel my subscriptions and move off Wyze altogether.

Wyze people, if you don’t know how to fix this, let me know. I do know how to fix it and will show you how. It doesn’t take 3 weeks to address it, that’s for sure.

Unfortunately it looks like this is not going to get fixed as they been actively moving to block access from other platforms.

They been trying to force everything behind a pay wall and there a stunning lack of transparency about recurring privacy incidents.

If you go to the wyze integration github and read issues 870 there are instructions for a workaround that should get you devices back up.

Frankly i had enough of wyze behavior and replaced most of their devices and stopped recommending them.

Greed clearly overriding anything resembling common sense or they realize this is going to do major long term damage to the company as word of mouth is god in this business.

I was able to put them back online after downgrading the HA core from 2026.7.1 to 2026.6.4 using my backups.

Read release announcement

Temporary fix here:

Same as @magnusman60@magnusman60. But careful. Read it. Any new update to fix issue you need to go back and remove it. A temporary bandaid. Thank you.

Home assistant people are aware as it affected a few other thing like google total connect.

Those would be updated eventually by the companies because security is serious for them but tell then it looks like the home assistant guys/gals have made a fix for now in the next release.

Long term this wont address the wyze issue tough.

It’s the enshittification of the Internet. I found and used the github fix and things are working. I’ve also placed a note on my calendar to cancel Wyze when my yearly subscription comes due in a couple months. I was one of the early adopters and convinced many people to use their products. Like every other company out there, they appear to have switched their real customers to being their VC and investors. Those must be serviced first. Community goodwill and profitability 4 quarters from now be damned. You’re only as good as your last quarter’s numbers. It’s killed many good companies.

I will no longer buy or recommend Wyze products and as I replace my current ones they’ll be sent to the recyclers to prevent anyone else getting and using them in the future. Will they care? Likely not in the slightest.

They will care eventually as this may get them short term profit it’s at the cost of long term survival.

When there are companies like Aqara and Reolink to name a few that see the huge benefit of working with the smart home community you can bet people wont be buying their products.

Yep.. this is an issue I’m having as well. I will try the temporary fix, but I have already canceled my plan. I thought Wyze was a pro-consumer company when I bought 4 cameras, 1 doorbell, and their lock. No more. I am now saving money to buy ReoLink or another company that hopefully won’t abandon their users.