Unbricking Wyze Contact Sensor - pcb reset pin

yes, it is inevitable that you will miss the window eventually. As things stand everyones wyze contact sensors are destined for the dumpster.

But the Texas Instruments advisory doesnt conclude that a “brown out” means the product is dead, it is only hung & needs a reset. Maybe some brainstorming here ( & some help from Wyze labs) might lead to a hack that can get them working again.


I don’t think this is hanging since it does work in Home Assistant, except all the bad ones have the same null mac address. It sounds like a corrupt flash memory, and these will likely need to be reprogrammed somehow to re-write their address.

I think a reset would be the same as turning it off then on, and so it would be the same as removing the battery and putting in a new one.

There are JTag pins but no Wyze firmware.

thanks null for that bit of info. it might be that the hung sensor is not replying properly to home assistant, possibly the address (does it need a mac address? this is a zigbee variant of network, not a TCPIP over wifi network) is still there . These are items that Wyze labs could confirm for us easily.

Possibly the bridge firmware could be updated to compensate for this?

firmware as in pins to a seperate firmware chip?

the chip is a CC1310 model F128 with 128kb memory , i would imagine that holds the wyze firmware

So somebody with a programmer has a chance?

the “programmer” is free to download from Texas instruments

one of its the features is MAC address reprogramming.

Customer, even without delving into chip programming, you could help by going over past posts on this forum or the TI forum on the subject, you might notice something
i overlooked. this chip is used in many other devices, I doubt all these consumers happily accepted that when the battery runs out the device can be thrown away.
you can also help by asking Wyze Labs to give this importance. thanks


Wow so you’re saying it just uses whatever micro-USB or similar port that is on the device. Nice.

It’s not universal that they hang or brick due to low voltage though. I have some sensors that have gone through a few battery changes after going dead. Maybe it’s a certain sequence of events or what state the sensors happen to be in at the time the battery drops to a certain level.

yes that could possibly be the key, the state the sensor was in when battery dropped.
the Advisory mentions something on these lines.

What i noticed as well as the bricked sensors still give low battery flashes if you replace with a low battery instead of a fresh one. So something is running on the chip.

The advisory states that if you’re using a non-rechargeable battery (which I believe we all are) and the battery goes dead, simply replacing it will cause a POR eliminating the need for a workaround. Problem is, replacing the battery does not seem to resolve the issue so I don’t believe this advisory is relevant.

I would have thought Wyze had resolved this problem by now. I guess they aren’t focused on PR and quality nearly as much as introducing new products. But who’s going to buy them if they have a reputation for selling self-destructing products?


the flash on the contact sensors can be rewritten with a donor firmware via jtag. a guy on github has already done it successfully–do a search for ‘wyzeback’. aparently you need to reprogram the original mac or it won’t work.

bricked sensors continue to work in home assistant, but only as a group together–not distinguishable individually which is fine for my alarm system which sounds a siren with no regard to which sensor was tripped.


Ladies & gentlemen, I think a key piece of information has just been revealed:

btw HA - home assitant requires you add a laptop/tablet etc to your home Wyze setup to host the HA services

If a third party, HA, wrote code that can talk to these sensors, what is keeping Wyze from issuing an update so that we can keep using ours (grouped collectively in 1 sensor group per bridge) with the Wyze app ?

1 Like

That wyzeback looks really promising. I have a Launchpad (LM4F120XL), but not the same as the one he used. It looks like mine has an on-board jtag programmer too. Never used it though. Hmm…

If they did, I imagine that would be admitting that some of these sensors are defective and should have been recalled.

1 Like

Well, that, and he pretty clearly says they still don’t have unique MACs, so it wouldn’t help get them working properly again in the Wyze ecosystem.

to clarify, I have not unbricked my contact sensors. I continue to use them in home assistant with a null 00000000 mac address as a single group. I only pair 1 sensor and the rest of them can automatically communicate with the bridge. if a neighbor within radio range uses wyze sense it could be an issue.


Isn’t it possible to force a downgrade of the update on the bridge from version 0.33 back to 0.30? I mean, I had a new combo sensor set that came with two door sensors and a motion sensor. I bought it a year ago and just opened it last week and tried to hook it up. Nothing would work or light up. Checked the batteries and they were all dead. Seems kind of quick to die being that they were never used and sat in a box for almost 12 months. I ordered new ones from Amazon over night (love that). I reinstalled them and again tried to connect the motion sensor and it would not light up when resetting the pin and of course I tested the new batteries and they were full. Then tested the door sensors and they worked and blinked 3 times but still wouldn’t connect. I figured that it had to be the bridge that failed and wondered if it was the update for it that was the point of failure since I read on their update page that the only thing the update did was prevent the reset button on the back of the bridge to work. Why go thru the trouble of taking that off line, I don’t know. But, this problem isn’t isolated obviously so why hasn’t Wyze address this issue at all?

Well they “addressed” it by entirely dumping the product line and beginning to sell an entirely new series of sensors and bridge…

1 Like

This is an interesting point. If the bricking problem is partially the fault of the bridge firmware, then maybe the new Hub will allow some of the old “bricked” sensors to work again since the sensors will work on the hub which has different firmware.

I do feel for those who have bricked sensors, but I can’t exactly relate. I have had several sensors go “dead” and when I just put in a new battery, they start working again as normal. I am not sure why some get “bricked” and others are fine with it though (the only exception being the 1 sensor that went through the washing machine and came out with corrosion and rust throughout the entire thing afterward).