FWIW, I believe that same community member posted that very screenshot to the Forum a couple of months ago:
I wish I could use the sensors with the security kit, right now they are a $100 paper weight.
Some of us can/have used the Wyze sensors directly in home assistant locally.
The easiest way is to get an old Wyze sense v1 USB bridge. That is the thing that the original V1 sensors used to connect to which plugged into the back of either the V2 camera or the pan V1 camera. Then, you could take that and plug it into a USB port connected to your home assistant node, and run a HACS integration that lets that bridge work in home assistant instead of through Wyze. Then you just sync the sensors to the bridge and voila! Now they work locally on home assistant. Both the old v1 and new V2 sensors, both contact and motion sensors. (Note that the original Wyze sense integration That changed the way. Some kind of variable worked, but people found an easy update to fix that, I just haven’t bothered to apply the update yet, but I was using the old integration for a long time, and it’s on my list of things to update so it’ll go back to working again with all my sensors).
You can sometimes buy those old things on eBay.
I’m sure it’s possible to use any other 915mHz bridge to do the same thing.
They actually work extremely well with this integration and connect totally locally. They’re fast, they have a very long distance with no interference issues, the battery lasts forever, etc. Great sensors. It may or may not be worth the effort for you, but they don’t have to be paperweights.
Alternatively, you could try to resell them. Wyze products typically hold their value really well because they already sell with extremely low profit margins.
(edit: I may have misunderstood the comment. I was talking about the standalone Contact and motion sensors…if by sensors the user means the camera sensors, then yeah, those would be nice to have. You can get SOME camera sensors through the HACS Wyze Integration, such as toggle power, siren, motion detection capability, notifications, floodlight, etc)
I’m not a long term customer, just a couple to 3 years. Have about 15 various cameras. They’ve operated well enough, when AWS isn’t wacky etc.
The Wyze RTSP is not useful to me to just display display live views in HAOS via the camera integration and how I use cameras. Perhaps for others that’s useful.
Without the sensors, person, animal etc., useless to me.
I tried hard, installed Frigate in Docker Linked to HAOS. Never had anything in Frigate logs except lots of Wyze RTSP errors. Months of frustration. They always streamed, buggy, but logs filled with errors, irritate me. Sorta gave up.
Reo WiFi cams aren’t perfect in Frigate either,.So far.
What does work well as mentioned above is the Reo WiFi 4ks and HAOS integration, Better still would be POE cameras and Frigate.
With those and the Reo Platinum HAOS integration, snaps shots, very accurate, few to NO false positives for person, which is most important to me, in close especially.
I’m still a Wyze customer, I like the OGs window mounts, the V4s outside, Pan V3s in basement and garage. App usage only though.
But as to Wyze cams ever being useful to “me” in HAOS? I don’t see that happening near term, or probably at all.
But, they have new inside window mount cams, those I’ll use if OGs ever take a hit for general security.
I don’t use Tinycam anymore, bought it, tried it, but not useful for me and my usage.
If I can’t tie them into HAOS with sensors, not useful to me personally.
I did subscibe to Frigate+. Might add some POE someday. But for now, all wifi at the moment. TBD.
The Reo’s expose person animal and vehicle in HAOS which is enough for me.
They will probably…replace any indoor/outdoor Wyze cams down the road. 4k, Pan V3s, rtsp, onvif, etc., fully enough HAOS integration.
They’re (Reo) ai detection isn’t perfect either. Thinks me on a lawn tractor is an animal or a 4 wheeler in the farm lane is animal. lol Person is very accurate so far in my testing.
Wyze detections V4 etc., are not useful for security alarms, person can be rain splatter shadows, etc. which would just be false alarms and sirens. Neighbor might complain. lol
No, I won’t tweak settings forever for either or any brand. But, useful for open the Wyze app, see what it is. Which is pretty accurate, person is “usually” a person in nice sunny weather.
But I can’t have sirens screaming because of shadows or cars going by and an OG says person. Doubt Wyze OG can see inside a car at 40-50 yards.
Cheap cams ai is just not deadly accurate. Cheap as in under $100 each to $250 for Pans, Zoom, or Floods.
So still a customer of sorts, like my Wyze cams, but all brands so far, leave a lot to be desired in modern security, like using in HAOS and Alarmo security etc.
Cheap cams may never have accurate ai for my use purposes. POE might.
Dang… I adopted Wyze locks and cameras years ago based on their suggestion that this was in the works. I would need it when I eventually rebuilt my system around HA. Now that I’m actually doing that, I see Wyze is a dead end.
I was in the market to buy a bunch more Wyze gear but now I’ll just have to sell what I have and move on.
Who gave you a suggestion that home assistant was in the works?
Lots of us have been pushing and hoping and potentially optimistic they will eventually give in. Still nothing official yet though.
They did recently say they in an AMA are RESEARCHING the viability of Matter. I’m hopeful they will give in to make a legacy matter bridge for most of their devices. But for now the only access we’ve had is through the 3rd party home assistant HACS Wyze integration. I know some of the locks are supported on there. They even did an interesting update to apparently support controlling the Bluetooth only Lock bolt v1. I haven’t checked if it supports the palm lock or lock bolt V2 yet though. If not I may get around to pointing Claude code at the repository and telling it to add that for me.
But I agree with the point that Wyze should spend the time to do their own official integration now. There really aren’t a lot of excuses nowadays since a lot of the work is already done for them, and open source and they can have Claude code and a developer overseeing it full in the rest of the gaps pretty easily. I’m hopeful this could happen within the next couple of years. 
It’s almost becoming a basic requirement for companies to have API and MCP access now. That’s only going to increase.
Sadly, I’m also considering switching out my Wyze cameras because of the lack of home assistant integration – such a bummer because I have so many. I also manage 12 Airbnb properties and have integrated a lot of Wyze cameras, but it’s not really manageable at scale without something like home assistant.
Wyze HAOS integration seems broken again. Appears related to a bad Wyze cert. at Github issues reports for Seckatie integration. I’m tired of it personally.
I only have Wyze bulbs on it, so they’re gone soon and so is the integration.
Zigbee bulbs are here, Hue. SMH 
No more cloud stuff, ever again. They’re all alike.
This has been reported to Wyze.
The problem is that Wyze’s API server (api.wyzecam.com) is currently using an older SSL certificate chain rooted at DigiCert Global Root CA (G1). The major tech platforms (Mozilla, Chrome, Microsoft) announced a long time ago that they were distrusting this specific root on April 15, 2026. Because of this, standard security libraries across the internet (like Python’s certifi) have officially removed the root from their trusted bundles.
Now, when clients try to connect to the Wyze API, the TLS handshake fails because the certificate chain can no longer be validated.
It’s an easy fix on Wyze’s end. The dev team just needs to reissue the server certificate through a currently-trusted intermediate root that DigiCert already has widely deployed (like Global Root G2, G3, or Trusted Root G4).
So hopefully they just do that.
But yes, it is a very solid example of why all smart home devices should be able to connect and run locally and not be cloud dependent. This kind of thing will continue to happen because industry standards change over time.
I am also slowly switching a lot of critical smart home stuff to things which will also function locally. I don’t mind cloud cloud connectivity. In some ways. I really like it for certain things. I just don’t think most things should be cloud dependent. There’s a difference between cloud enhanced and cloud dependent. Dependency is not good, cloud enhancement is totally okay with me.
Sadly, I’ve pushed everyone that I had previously suggested Wyze to onto other brands by now. I really do like the form factor and simplicity of installation that the Wyze products offer but the lack of local support really breaks things.
I have family that has very slow internet (DSL/traditional satellite) and the cloud options just don’t cut it. My mother has been a bit of a guinea pig as well as she was in that same boat but thank god she now has Starlink.
My only issue with that though is still having to send data to the cloud via low earth orbit back down to us. Seems like a giant waste even if it seems easy if you don’t think about it.
For me, right now, everyone has switched to either Ubiquiti or Reolink/Onvif so the RTSP firmwares are a little late in the game. I am still willing to try some devices when they do offer Matter support though.
Hopefully they will be working on that in the coming months and can bring their devices into 2026’s standards for the local smart home.
Yea, I’m about to move over to Reolink. Wyze has been too inconsistent/delayed over wifi for security usage & lacks access to logs/info the customer can use to self diagnose. As @carverofchoice said, web enhancement & not dependancy. …I need local first, cloud second. Clearly Wyze has no intersest in local-first, Home Assistant support, so I’m out. I’m slowly moving away from any company that does not have Home Assistant interoperability. When you buy a faucet, a light switch, a door hinge, etc, it makes sense because you don’t need a Lutron/Phillips/Leviton brand house to use it. You only need some basic adapters or common connection points. Wyze & every other Tech Bro need to start thinking the same way. Home Assistant IS that connection point. Budding standards like Matter or Zigbee prove this to be true. The vender lock-in model is trash for consumers. @WyzeDave You need to read this.
Yes, that’s what I gathered from Github issues posts. For me it doesn’t matter anymore, I switched all Wyze bulbs to Hue Essential ZigBee and added them to Z2m. All good now. I’ll give the Wyze bukbs to a newbie if opportunity arises.
Deleted the Wyze integration in HAOS the next day after my previous post. It happens too often and is a hassle, regardless of who is at fault.
Neices, Nephews, Grandkids, etc LOVE getting a smart color bulb for their room. That’s actually how we got our first color bulb. My daughter’s grandma gave her one for her birthday. She loved it. Just sayin’.
I heard Home Assistant is expected to push an update to add back support for these certificates because there were a few other integrations that broke that people were upset about.
Truthfully, while the primary accountability is on the heads of the companies that still use the deprecated certificates (including Wyze), an open platform like Home Assistant should give users the option of whether they personally want to allow their Home Assistant instance to accept the older certificates or not. Home Assistant shouldn’t necessarily be making decisions about what’s an acceptable certificate or not. I should even be able to submit and approve my own personal certificates if I want to, including for my various systems that I self host. They probably shouldn’t be forcing/telling Homelabbers what counts as a valid certificate or not. If someone wants to use a different kind of certificate on opensource home lab equipment like Home Assistant, that should 100% be their choice…but I agree the primary fault is on the enterprises not keeping up to date with industry standards. Hopefully Wyze adds the update soon…but even if they don’t, the rumor is that Home Assistant is going to add support back for those deprecated certificates if someone wants to use them.
That’s cruel! Why would you subject someone to all the headaches that come with it? Year or so ago I would have recommended Wyze to anyone in a heartbeat. Not anymore. When they come and ask, I tell them do you own research and take it from there. Don’t go by what I have cause I’m not happy anymore.
I may keep a bunch off Wyze cameras that I use just like baby monitors for our licensed daycare during business hours. If I replace the main outdoor cameras with something like Reolink Then I can cancel all my Wyze services and have more local control through HA. I already have a bunch of Zigbee sensors, so I don’t really need the Wyze ones if I cancel Home Monitoring. I’ll just have to figure out which locks and doorbell to go with that I can control in HA.
In the dedicated thread about the certificate issue, I posted an interesting discussion about the importance of Home Assistant that the execs are overlooking for why their lack on supporting is severely hurting them. Anyone interested should read it and I encourage you to add your own voice (here or there, or in the wishlist) about why things like Home Assistant are more important than they realize.
They do recognize and respond to community engagement oftentimes. It is literally the only reason they finally gave in to start working on Dark Mode and RTSP…but as engagement on important topics wane, so does their priority on such things.
Selling my Wyze Color bulbs. Tired of waiting to if Certificate issue breaking Home Assistant integration will ever be fixed. Oh well…I really did like them for a while.
I have roughly 15 cameras and a bunch of switches.. Will be selling and canceling all subs. What a POS company. Get your S together. Lies and run arounds. USESLESS.
I just got a firmware update version 4.52.17.10 and it has an option to enable RTSP. I’m using a Wyze Cam v4.
Yep. Wyze now supports RTSP officially for the:
- V3
- V4
- Pan V3
Hopefully more on the way, and hopefully more than just RTSP in the future, but it’s a good start. 