search

kevinvincent / ha-wyzesense

A Home Assistant Component to interface with the WYZE Sense hub and sensor system
368 stars 97 forks source link

Sensors stop working after random periods of time. #119

Open Phara0h opened 4 years ago

Phara0h commented 4 years ago

Here is the chunk of logs when it stopped working. It stopped working when wyzesense started to log out that it was in the past 1969-12-31T19:00:00 https://gist.github.com/Phara0h/b36ee1463f7417a3d8def48765abdbbd

RoldyBuffalo commented 4 years ago

https://github.com/kevinvincent/ha-wyzesense/issues/121#issuecomment-610958312

I think I may have figured it out? Perhaps, this is some valuable information. I had a sensor that was showing up as -110rssi, this meant that sensor was dead/battery was dead/out of range. So once I removed that faulty sensor the entire stack came to life like that particular entity was holding up pretty much all of home assistant. Once I removed the sensor that was faulty (checking rssi in entity list) everything returned to normal, after a full host reboot for good measure of course.

Phara0h commented 4 years ago

@VarenDerpsAround all battery levels are over 90% and rssi is above -93 which is good enough for the receiver to receive. So not the issue. (Also RF engineer here for context)

zachsteffens commented 4 years ago

I'm having the same issue. Can't find any logs to assist in debugging. It's happened in the past and it was fixed by a reboot but that't not working any longer

Erdcgh commented 4 years ago

I too am having the same issue. as zachsteffens stated "It's happened in the past and it was fixed by a reboot but that't not working any longer".

But I just tried now a homeassistant.restart instead of a reboot and that fix the problem.

Good thing too, since I just ordered four more of the contact sensors.

UPDATE: Well that only worked for a couple of hours, now the WYZE receiver is just flashing the two colors at me and so the sensors have stop working again.

cjsteward commented 4 years ago

Same thing just happened to me. Sensors have been rock solid for months then all of the sudden they all stopped updating on the front end. I rebooted hass as well as the host, I uninstalled the wyze component, I downgraded the wyze component, and I rolled back to a previous snapshot. Nothing worked. I noticed that the wyze sensor hub was showing a solid blue light and I was able to actually pair devices, but they weren't updating their state on the front end. The only thing that fixed it for me was to manually re-pair all of my sensors. Once I did that they started updating in the FE correctly. I did notice that a couple of my sensors were blinking, which I believe indicates a low battery.

jmoery commented 4 years ago

I too am having this issue. I just installed everything for the first time last not. Everything paired just fine. The sensors were updating for a while, but now haven't updated in the past 7 hours. My main hub is currently solid blue so assuming it is still connected. This happened almost immediately when I first installed everything. Had to reboot home assistant and re-add all the sensors. Not sure what is happening here.

Phara0h commented 4 years ago

Got an error running on master

custom_components.wyzesense.wyzesense_custom] Invalid packet: b'55aa5319' 2020-05-05 21:11:07 ERROR (Thread-2) [custom_components.wyzesense.wyzesense_custom] Invalid packet length: 4

jamman9000 commented 4 years ago

Same issue. Sometimes a normal HA restart works, sometimes I have to reboot supervisor (I'm guessing this is the HA docker container), sometimes I have to reboot the proxmox vm, and sometimes I have to reboot the entire physical server. Happens once or twice a week, and you never know if it's completely fixed because some sensors will start working and others will stay stuck in whatever state they were last seen in.

jamman9000 commented 4 years ago

Now happening within 12 hours and have to take the most drastic action of pulling the USB cable and rebooting the physical server proxmox is on. Automations are basically broken until motion/door sensors get working again.

jmoery commented 4 years ago

I switched to the usb3 drivers on my Debian VM and that seems to have stopped the failures. Unfortunately my ZWave USB hub has issues on the usb3 drivers, just not as often. Catch-22

On Wed, May 13, 2020, 7:34 PM Jason notifications@github.com wrote:

Now happening within 12 hours and have to take the most drastic action of pulling the USB cable and rebooting the physical server proxmox is on. Automations are basically broken until motion/door sensors get working again.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kevinvincent/ha-wyzesense/issues/119#issuecomment-628349434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYU4ML5OE33BFVX2SAVVTDRRNKB5ANCNFSM4L3IZ6SQ .