ha-wyzesense
ha-wyzesense copied to clipboard
kevinvincent
Sensors all stopped working randomly
As title says, component was working flawlesssly. Then today it stopped reporting triggers. I have binary sensors setup—contact and motion sensors—and they just stopped firing. I’m using 0.0.8 because 0.0.9 wouldn’t find the sensors when setting them up.
I reset proxmox, HA, and eventually the whole bare metal server. Nothing fixed it.
Decided to call Wyzesense.scan and let it expire over 30 seconds. It did.
Now, the sensors work again.
Anyone have this issue or seen this before?
Couldn't find any mention of Wyze or the component in my logs either, so I'm totally confused.
I'm noticing this too. I had to do a wyzesense.scan and hold each reset button on each device in order to get them back the last time this happened...
Same here. Running a wyzesense.scan service call and letting it expire actually fixed the issue. So far so good. Will keep an eye on this thread for proper resolution
Is it safe to say that the downgrade to .8 did not fix the issue of sensors not working (don't have the issue number in front of me) or is this a separate problem?
Given they were working before and then suddenly stopped responding, but would not even show up with .9, I’d say separate issue On Sep 2, 2020, 4:36 PM -0400, James Cadd [email protected], wrote:
Is it safe to say that the downgrade to .8 did not fix the issue of sensors not working (don't have the issue number in front of me) or is this a separate problem? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
I have run into the same issue twice now. The first time, I did all kinds of things, including rebooting HASS, Proxmox container, Proxmox itself, disconnecting/reconnecting the dongle. Finally I reinstalled the Component, and that seemed to fix it. I don't recall, but I think that was on version 0.0.8.
I have since updated to 0.0.9 and it happened again this morning (or maybe late last night). Tried the reinstall of the Component and that didn't work. Tried downgrading to 0.0.8 with no luck. Rebooted everything again. Upgraded back to 0.0.9. Started searching, and found this thread. Performed a scan, and all is well again. The one thing that i didn't try this time was disconnecting/reconnecting the dongle.
I have since added to Node-RED a flow to perform a wyzesense.scan every 4 hours. Not sure if this is a good idea or not, so might not keep it.
I’ll be curious to hear how that regular scanning works out for you. Without pressing a sensor connect button though, would it even work? On Sep 9, 2020, 3:41 PM -0400, jasonmanderson1974 [email protected], wrote:
I have run into the same issue twice now. The first time, I did all kinds of things, including rebooting HASS, Proxmox container, Proxmox itself, disconnecting/reconnecting the dongle. Finally I reinstalled the Component, and that seemed to fix it. I don't recall, but I think that was on version 0.0.8. I have since updated to 0.0.9 and it happened again this morning (or maybe late last night). Tried the reinstall of the Component and that didn't work. Tried downgrading to 0.0.8 with no luck. Rebooted everything again. Upgraded back to 0.0.9. Started searching, and found this thread. Performed a scan, and all is well again. The one thing that i didn't try this time was disconnecting/reconnecting the dongle. I have since added to Node-RED a flow to perform a wyzesense.scan every 4 hours. Not sure if this is a good idea or not, so might not keep it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Interestingly, I didn't have to hit any buttons on any devices to get them working again. 2 motion and 4 door/window sensors. Granted, I did all the rebooting, uninstalling/reinstalling before the scan, so maybe some combination played into it.
Regardless, I'll post an update if I notice any issues.
I’ll be curious to hear how that regular scanning works out for you. Without pressing a sensor connect button though, would it even work?
Almost 48 hours in and no adverse affects that I have sen thus far regarding my scheduled scans every 4 hours. Unless you count the notifications that I need to clear, but that's it. Everything is staying connected.
Might disable my process, and see if/when the issue happens again, and then re-enable my process to confirm it clears it.
My setup has Motion and Door sensors with multiple automation's with alarms, lights on/off etc. all of the sensors and battery states were available in entity cards in HA running on a Rpi 4; with no automation's working or changing states. Wyze scan was not available in the drop down. Downgraded to .8, restarted and success, scan back as available, all sensors now triggering and activating - seems an issue in my environment with .9.
I'm also having this issue. Doing just a scan did not work for me. Strangely, it updated the "Off" times for all of my sensors in Node-Red but they still do not trigger on when motion is detected or a door is opened.
I restarted my HA container and the sensors came back online properly. I have a feeling it was the combination of these activities that fixes the problem.
By chance are you guys running HA on Linux>Docker>Home Assistant Supervised (Hassio)? The reason I ask is, I was having a similar issue where my sensors would randomly stop responding. I would need to remove the Wyze bridge, restart ha, and insert the bridge before it boots to bring them all back. Recently I installed a Z-Wave stick and it had this bit in the documents about disabling Modem Manager in ubuntu. It warned about zwave node random disconnects, unresponsive etc. Since I have disabled Modem Manager I am no longer having the issue with wyze. I'm wondering if the same issue applies to the wyze bridge as it does with zwave usb sticks.
This just started happening to me as well. Everything was working just fine ever since I switched to USB 3.0 in my VM many months ago. Now all of a sudden none of my automations are working with any of my Wyze sensors. I am not sure exactly when it started to happen as I just updated HA and WyzeSense about two days ago, at the same time, and that's around the time I started having these issues. I tried unplugging the hub and reconnecting it but now the light wont turn blue, even after several reboots of HA and even the OS itself. I am running HA in a Ubuntu VM using docker as well.
@mattyb8562 How did you disable Mode Manager?
@singhj0910 Connect to your host OS via SSH, then you can disable with "sudo systemctl disable ModemManager" and remove with "sudo apt-get purge modemmanager".
@singhj0910 Connect to your host OS via SSH, then you can disable with "sudo systemctl disable ModemManager" and remove with "sudo apt-get purge modemmanager".
Thank you. I assume this is safe to do? Will removing it affect anything else?
@singhj0910 It shouldn't have any negative effect as far as HA is concerned. I would clone or get a back up of your VM just to be safe though.
@mattyb8562 would this still apply if I'm running HassIO on a VM in ProxMox? Doesn't seem like it, when I run "systemctl status ModemManager" I get "ModemManager.service could not be found."
@jamescadd I would think so. Typically you would install docker on ubuntu (or other Linux distro) in a VM. Make sure you ssh to the OS, not Hassio.
@jamescadd did you use whiskers one line script to install? Pretty sure in that script it automatically removes modem manager
Just following up on my previous posts.
I had this happen again last night (about 3 weeks since the last). Not sure exactly when, but when I noticed, I was able to resolve with just a scan.
HASS v0.115.6 Wyze Sense v0.0.9
I did not try anything else in terms of reboots, reinstalls or anything else. Just the scan.
I'm going to reactivate my node-red flow to perform the rescan at some interval and see how that works for me.