I too suffered from the lost MAC address problem. 12 out of my 14 or 15 sensors all died on me during a move. I opened a ticket with Wyze support and since I didn’t have a camera to update the firmware on the gateway, they sent me a new gateway with the updated firmware.
I can confirm the updated firmware on the gateway resolve the lost MAC issue. Now all door contacts that previously had dead batteries are all importing as expected, binary_sensor.wyzesense_macaddy
So did the receiver die and as a result gave you the failed MAC address issue or did all the batteries die on the sensors? There is a big difference, when the batteries die the EPROM or whatever is storing the MAC address causes it to post all zero’s and to my knowledge there is no easy fix other than an extensive hack that requires soldering and re-flashing. Are you stating that there is a firmware update that corrects dead sensors, if so can you confirm the firmware version
@mrbilky The receiver did not die, the lost MAC address was caused because the batteries in the sensor itself died. With the old receiver, and new batteries, I could still import the sensor but it would show up as binary_sensor.wyzesense_ and thats it, no zero’s, nothing after the last underscore. Wyze sent me a new receiver that had a newer firmware on it (couldn’t update my old one because I do not have a Wyze Camera). I replaced the batteries in a couple dead sensors and using the new receiver the contacts imported as if the batteries had never died.
Im not sure what firmware version the bridge I received is on. If you know of a way to find that info I can certainly try looking it up.
Which receiver? do you mean a new model of Wyze bridge that plug into USB?
Wyze sent me the same model bridge, WHS81.
1 Like
Thanks. Seems like that a new firmware update on existing bridge should fix this, which not only saved dead ones and also prevent this happens again? Do you know what the firmware version is on your bridge?
If this is the case, that’s really a good news.
I also wanted to note that if you have already imported a sensor into HA and its registered as binary_sensor.wyzesense_ with nothing after the underscore, you MAY have to manually remove that device completely, (service > wyzesense: remove and make sure its removed from the entity_registry file). Then try scanning it in again, using a bridge with the new firmware of course.
Sorry I can’t provide the firmware version on my bridge since I dont have the camera. Not sure how else I’d be able to find it.
Sorry I’m not sure what version firmware the bridge I received is on since I dont have the camera. If you know of a way to find it I’d be happy to look.
I was very excited to see my dead sensors import with the MAC address included in the name. I thought for sure a new bridge would not fix the issue and they were just skipping around sending me 12 new door contacts.
I would be very interested if this works. I currently have 5 non working sensors, and one still working. I have switched to RF 433 but there is an issue if there is too much metal near one, and they are much bigger than the wyze sensors. I am actually trying to remove the “old” sensors but every time I put the Mac address in I get an error of * [140170742306176] Error handling message: expected dict for dictionary value @ data[‘service_data’]. Got ‘77902e1b’
I’d sure like to hear more people confirm this, anyone else? Does Wyze have any documentation explaining this I’m sure they would like to get this out to resolve this terrible issue that they created
The motion sensors do infact have an issue. When they batteries die in them, for at least a day, they will no longer turn back on with new batteries, Just had this happen. I was under the impressioin that they didnt have the problem, however after some searching around I found others with the same issue.
So a new firmware on the bridge might fix the contact sensors. Ive got about 8 dead ones, half of which were warrenty replacments that arrived dead. (lol, 
)? Searching for information now…
I tried cheap RF 433MHz sensors. They fail to report about every 10 or 11 open/closes. The Wyze never failed to report, and had better range, and are smaller. I so wish these were capable of battery replacements. But honestly just buying new ones isn’t that awfully expensive. What to do, what to do.
Does anyone still using this integration for v1 contact sensors GitHub - kevinvincent/ha-wyzesense: A Home Assistant Component to interface with the WYZE Sense hub and sensor system? Recently I found that the battery % was gone from home assistant integration, not sure what changed. I am relying on this integration to monitor the battery %, whenever it falls 85% I need to replace the battery.
Thanks.
https://github.com/kevinvincent/ha-wyzesense/pull/218#issuecomment-1075906873
Gives how to fix the issue.
Thanks @bschatzow!
I modified the file binary_sensor.py as in the commit, rebooted HASS. However the battery status is still not showing up. Is there anything else needs to be done?
That is all I did and it worked on mine and many others. Are you seeing any errors in the logs? I did prior to the change.
I’ve turned the debugging on, no error in the log.
I unplugged the bridge and plugged in again, remove the HASS container and recreate it. Now the battery status shows up. 
Thanks.