Open the window! But seriously, there is no other way, which is a huge oversight on Wyze’s part. The new ‘security’ rated sensors should be able to keep the battery level updated without having to activate the sensors. I know that doesn’t help you now, but that’s all Wyze is giving us.
got it, there is no pull, can only be triggered when state changes 
FYI, someone found a way to unbrick bricked sensors due to the low battery/MAC address loss issue.
2 Likes
great will try it out - will this solve the issue in future (not erase it again) or will the issue still stay and process needs to be repeated if it happens?
I have not tested so I don’t know for sure. I would imagine the issue would still persist.
good to know, not easy though, need some hardware/software to do this.
Tried to get this going on Ubuntu Server, so many fails.
What’s the best way to go with this integration hardware wise ? The Pi ?
1 Like
is it possible to get this local integration working on hassos 117, hass 118.4? i’m trying to run the 0.0.9/master repository in hacs and can’t even get the blue light on the bridge to register. I once had this working earlier when I was on hassos 114, but needed to upgrade. I’ve removed all previous wyze entities and rebooted the host, but I keep getting a _docommand timeout in the logs and the wyze component fails to initialize after 60secs. can someone else please confirm that it’s even possible to run the integration on hass 118.x?
According to his github kevinvincent is no longer maintaining this integration but I see no current reason you should not get this working but I like many others are quite pissed over the issue of sensors being bricked if the battery dies and since most of us have reported that battey levels don’t go below 70% before the damn things die its hard to manage and no longer advantageous to continue to integrate these sensors have you run the “dmesg | grep hidraw” to see your assigned bridge
1 Like
“dmesg | grep hidraw” indicates the bridge is consistently on /dev/hidraw0. i’ve tried both auto & “/dev/hidraw0” in my configuration.yaml. here’s the error I’m getting when the blue light fails to register:
Logger: homeassistant
Source: custom_components/wyzesense/wyzesense_custom.py:388
First occurred: 10:57:12 AM (1 occurrences)
Last logged: 10:57:12 AM
Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File “/usr/local/lib/python3.8/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/wyzesense/binary_sensor.py”, line 120, in setup_platform
ws = beginConn()
File “”, line 2, in beginConn
File “/usr/local/lib/python3.8/site-packages/retry/api.py”, line 73, in retry_decorator
return __retry_internal(partial(f, *args, **kwargs), exceptions, tries, delay, max_delay, backoff, jitter,
File “/usr/local/lib/python3.8/site-packages/retry/api.py”, line 33, in __retry_internal
return f()
File “/config/custom_components/wyzesense/binary_sensor.py”, line 118, in beginConn
return Open(config[CONF_DEVICE], on_event)
File “/config/custom_components/wyzesense/wyzesense_custom.py”, line 565, in Open
return Dongle(device, event_handler)
File “/config/custom_components/wyzesense/wyzesense_custom.py”, line 299, in init
self._Start()
File “/config/custom_components/wyzesense/wyzesense_custom.py”, line 505, in _Start
self._FinishAuth()
File “/config/custom_components/wyzesense/wyzesense_custom.py”, line 489, in _FinishAuth
resp = self._DoSimpleCommand(Packet.FinishAuth())
File “/config/custom_components/wyzesense/wyzesense_custom.py”, line 397, in _DoSimpleCommand
self._DoCommand(pkt, cmd_handler, timeout)
File “/config/custom_components/wyzesense/wyzesense_custom.py”, line 388, in _DoCommand
raise TimeoutError("_DoCommand")
TimeoutError: _DoCommand
yeah, wyze published this article acknowledging the battery defect: https://wyzelabs.zendesk.com/hc/en-us/articles/360047594431-Sensor-isn-t-connecting-anymore-after-changing-the-battery. even so, i can still probably use the sensors with a 0000000 mac together in a group as i don’t really need differentiation between them–5 trigger the exact same automation and i don’t need to know which one did it for my purposes. only issue i can’t control is if 1 of my immediate neighbors also uses the sensors then i’m in trouble.
well hell, it appears I have a hardware issue as I can’t get the bridge to initialize while connected to a wyze camera as well. i can see the bridge led flash periodically during the camera boot sequence while trying to communicate, but the light remains yellow and never turns blue.
I have a few contact sensor died due to low battery but they still appear in the HA entity list. I tried to select it and remove it from configuration->entities page and got below message:
Only 0 selected entities can be removed.
You can only remove 0 of the selected 1 entities. Entities can only be removed when the integration is no longer providing the entities. Sometimes you have to restart Home Assistant before you can remove the entities of a removed integration. Are you sure you want to remove the removable entities?
After click “remove” the entity is still there. How can I remove it from HA?
Thanks
I have a contact sensor showing battery of 92% but it flashes red 3 times every couple seconds, which I think it indicates low battery. I’ve read somewhere that in general we need to replace battery if it below 85%. I think I am going to replace this one to avoid brick.
Another is showing 86% and not flashing red.
I’ve had two cases where the sensors cease to respond when the battery is at 86%, I swapped them out and the sensor(s) started to respond again. Thankfully it takes them months to get to that level with normal daily use. I’ve set up a monitor to notify me when ever the level is 87% just to be on the safe side.
Is there any “official” statement regarding the battery level? I haven’t seen any of my sensors drop more than a few points in the last couple months of having them, but now I’m getting worried 
Hi
My home assistant was in unsupported environment (debian 9, docker18 etc) on Proxmox. My door sensor stopped working sometime back but i did not change the batteries and try till now where I have reinstalled Home Assistant from scratch on Proxmox on Debian 10, Docker 20 and the system fully supported/compliant. I installed Wyze sense from HACS (latest version).
I replaced the batteries of 4 door sensors and try to add them. Except one (other defective) other 2 does not get unique ID for the sensor and appear as “binary_sensor.wyzesense_”. with no unique ID for both sensors the status change in binary_sensor.wyzesense happen as if the two devices are one and the same. As such I cannot use them. The message I get in notification when adding these sensors are
“Sensor found and added as: binary_sensor.wyzesense_ (unless you have customized the entity ID prior).
To add more sensors, call wyzesense.scan again.
More Info: type=1, version=16”
As I mentioned my other door sensor got added with proper unique ID. I also added two new motion sensors and those also got their unique ID.
Not sure why this is happening. these two door sensors did get their unique IDs when I added them first 1.5 years ago and they worked well for over a year. Not that they are not working now but they do not get distinct binary sensor so one one can be used
Any help appreciated
Does anyone know if the motion sensor have this issue of brick with low battery?
Yes they do. It is unfortunate. I purchased a bunch of sense stuff, and I just removed it all to throw away.
It is happening because when the battery goes dead the mac addresses get erased, and they show up with the same MAC. This is why Wyze quietly discontinued the V1 sense stuff. You’ll have to throw them away(or figure out a way to program the MAC address, which I have no clue whether it is possible or not.)
1 Like
I have confirmed with Wyze support that the motion sensor can also get bricked