For sure… nothing that can’t be done with an old phone either.
It had three things going for it:
I got a relative a very early version of that - not IP at all but a decent transistor radio in an old timey cabinet. He loved it. Crosley I think. (Might have had MP3 ability too.)
It never was about the battery being out of the device or being completely dead…in fact, the only known way to keep them from bricking themselves in the long run is to pull out the battery of a functional unit. The scenario that broke the sensors was not a dead battery, but a low battery. With a low battery, there was always a chance that the next motion event would cause data to be rewritten internally in a manner that permanently corrupted the on-device mac address…and so the longer the device was in the sate of low-battery, the greater the likelihood it would happen. Wyze never told users how low was too low (in fact, they never told users anything about the problem at all).
I think it only affected the contact sensors - at least that’s the only type that I experienced this problem with - of my original fleet of 2 motion sensors and 10 contact sensors, all but 2 of my contact sensors bit the dust, but both my motion sensors were still working right up until I abandoned wyze sense products in favor of something else.
yes, I meant low battery issue. I had a few contact sensors bricked due to this. The motion sensors are still good so far.
If it only happened to the contact sensors…
I would be soooo happy! Not.
Please let us know how you roll out Frigate. I’m still thinking that either a Jetson Nano or a Coral Dev Board would be a good way to have a single device capable of running it all well in one place - Home Assistant and MQTT and Frigate and TensorFlow. But from limited searching I don’t see anybody with really easy DIY hardware and software recipes (“here’s exactly what I built and it works”). My old PCs aren’t powerful and I don’t want a string of Pis and NAS accessories to do this.
This guy has good info and videos though (similar to the person you linked).
Thanks for the link Kiril Peyanski’s Blog. I expect this to be a steep learning curve for me. i.e. my progress will be slow 
I only check this thread periodically these days as I phased out all of my wyze gear. I check in occasionally hoping maybe there is some good news and perhaps I could give this company a second chance. However, the lack of response from anyone at wyze and the lack of movement on an API speaks volumes. Disappointed a bit, but I found alternative solutions. I’d recommend everyone that wants local control do the same.
I don’t expect purely local access for a while. They are slowly making some improvements, such as RTSP, and saying they’ll work with Joshua somewhat on his API workaround, but I am guessing we won’t see major changes at least before Matter is fairly well developed first. I am guessing that will understandably get the priority for now.
Out of curiosity, what did you go with for lighting, motion/contact sensors and what was the cost for them? What other devices did you get to go Local?
Also interested in what people are switching to for HA integration. My cameras and doorbell have become the weak link, once I find a replacement for them they are going on Craigslist.
I just purchased a Reolink camera and use the Blue Iris integration with Home Assistant. Works well for my needs.
Sadly both my motion sensors seem to have bitten the dust so it’s not limited to contact sensors. I like you had 2 motion and 8 contact. I have 3 contact sensors still in use till I swap for some zigbee ones like I have elsewhere.
I’d be happy to continue paying Cam Plus because I don’t want to run it locally at this point and want my events accessable outside the home in case I loose power after an event.
I have stopped buying wyze products for now. I love them, but now that I am running HA not having them integrate is just frustrating. I have already replaced all my sensors and just have cameras now. I like their cloud recording and AI features that I pay for, but would still like that info reported into HA to be used in automations. In the future I may move towards unifi if nothing changes on the wyze side of things. I also would be fine with cam plus for api access.
Same I gave up. I used to buy everything they released. I the the V1, V2, V3 and Pan, scale, outdoor, bulbs, plugs. vacuum, band…spent 100s of dollars on Wyze Stuff. I like their mission of trying to make smart homes more available to the masses but what I care about more is privacy and local control (I don’t really need want or need external facing APIs). I got some Unifi bullet cameras in every corner and some Amcrest Floodlights in a couple of areas and I couldn’t been happier. I also replaced most of my smart stuff with zigbee/zwave or wifi with Tasmota/ESPHome. Everything just works 100% of the time. I wish Wyze luck. I am going to keep following them just in case anything changes.
+1 for this. I was so excited for RTSP on V3 but… Turns out that it isn’t very stable and breaks Cam Plus. You almost had me as a paying subscriber for 6 cameras. If you did a good Home Assistant integration with live video, and triggers, I might reconsider.
I’ve been through this exact issue and it’s a simple fix. In order to get rtsp and cam plus working at the same time, all you need to do is downgrade the firware to the not current version, activate cam plus on any camera, then flash the rtsp firmware and it should work after that. it will not work the other way around. https://support.wyze.com/hc/en-us/articles/360024852172-Release-Notes-Firmware
The problem is that not all of their cameras are RSTP compatible. If they added that as part of their base camera firmware though they will loose people signing up for Cam Plus. I mean if your ok with relying on cloud based cams then go for the cam plus. Personally I’d rather keep my data local and run it to an NVR with my own offsite backup.
Wyze is quickly turning into a services paid company. They get you with cheap equipment that locks you into their ecosystem. And they are defending that pretty strongly.