First, I am truly amazed at all the hard work people put into everything to make things work. Thank you.
Second, it seems like every 1 to 2 days Wyze Sense Component stops reading the sensors. A restart of Home Assistant always cures it, but I was wondering if everyone else experiences this? Do you simply have home assistant restart every 24 hours?
Thanks
having same issue too.
I started noticing the issue from yesterday. I couldn’t get it to work by restarting Hassio. I am running it as a VM on Unraid server. I had to restart the VM entirely for the adapter to start functioning again.
I lose my 2 door and 1 motion sensors on reboot of my Pi. A simple open/close or movement brings them back, but it’s annoying. Wondering if there is a solution or what would cause it to happen.
I noticed same, all sensors stopped update status.
My setup is HA on virtualbox ubuntu container, the bridge is plugged in the windows PC which hosting the virtualbox. so using usb passthrough.
What’s your the setup for those had this working and those had similar issue?
My setup is similar: Mac running Virtual Box. VM is Ubuntu 18.0.4.1 LTS. USB Passthrough.
I also seemed to have noticed if the sensors are triggered quickly in rapid succession (ie a child opens and closes door quickly many times) it seems to cause a lack of change state as well.
I’ve noticed the exact same behavior. I am running hassio in VirtualBox on a Windows machine. I have the bridge plugged in and forwarded to VirtualBox.
I had family over around the holidays and my sensors were getting triggered much more often than normal. While they were here I had to restart a couple of times to get the sensors “unstuck”. I have never lost them on a reboot though, I know that was an issue with an earlier version of the integration. Are you all the way up to date @Turbo4door?
i have the same problem like u guys so i deleted windows on my surface , set up ubuntu and hassio . since then, there is no more issue.
looks like issue is due to windows host?
I don’t think Windows is to blame here.
I’m running HA on a Raspberry Pi 3+ with the USB sense connected directly to the Pi.
I occasionally have the exact same issues as described above. Sometimes restarting HA is enough but most times I actually have to restart the Raspberry Pi.
My assumption is that the USB dongle somehow gets “messed up” and needs a good old hardware reset.
Thanks for the datapoint. In my case, restart HA container doesn’t help, I have to restart the ubuntu which is a pain since I have other containers running on it.
I’m running on mine on a RPi 4. It’s not like they really lose connection that requires a reboot for me, just report unavailable until the next state change after rebooting HA (i.e. for a config change). I rebooted several times last night working on some stuff and each time after the reboot they were unavailable until i manually forced a state change by opening or closing them, or introducing motion to the motion sensor. I had thought about trying to send a set state or update entity request on boot but since they aren’t available that isn’t an option.
I need to order a bunch more window/door sensors and I really want to use these (because of their range and cost), but they really aren’t of any use if this can’t be fixed.
Here’s what I’m seeing in log:
Fri Jan 10 2020 15:03:28 GMT-0500 (Eastern Standard Time)
Error while setting up platform wyzesense
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/wyzesense/binary_sensor.py", line 94, in setup_platform
result = ws.List()
File "/config/custom_components/wyzesense/wyzesense_custom.py", line 507, in List
sensors = self._GetSensors()
File "/config/custom_components/wyzesense/wyzesense_custom.py", line 479, in _GetSensors
self._DoCommand(Packet.GetSensorList(count), cmd_handler, timeout=self._CMD_TIMEOUT * count)
File "/config/custom_components/wyzesense/wyzesense_custom.py", line 384, in _DoCommand
raise TimeoutError("_DoCommand")
TimeoutError: _DoCommand
Weird… the sensors are working fine and have no errors in my setup. ubuntu 19.10 in a venv.
just added some new sensors today as well.
glad it works for you. for my case, it stops every 1-2 days, not just occasionally.
I was ready to order more contact/motion sensors but holding due to this.
I just got my Wyse Sense, setup thru HACS. used the auto device and it shows up when I reboot with no errors. Go to add a sensor run the wysesense.scan hold the pin down till the red light flashes 3 times and nothing, the blue light on the usb receiver keeps flashing. then I get a notification that nothing paired in the 30 seconds. Any one else having this issue. I am running on a RPi4 HassOS
Update:
I downloaded the latest from GitHub last night and it’s working now. Sensors come back on reboot and my WyzeSense services are back. Looks like there may be HACS update today that has the new version as well.
In one of the Facebook groups this was mentioned by me, and I was told to look here:
Same. Any chance you figured this out?
My motion sensor stopped updating status last night so I checked logs and saw a few errors, one of them being TimeoutError: _DoCommand so I updated to the latest version through HACS and now the motion sensor is stuck on “detected” and the two contact sensors I have are unavailable. I triggered the motion sensor and one of the contact sensors before rebooting multiple times but that didn’t fix it. I have one contact sensor in the mailbox so I haven’t been able to trigger that one yet. I’m running HassOS in a virtualbox and this has been working flawlessly for over two months up until now. How do I get this resolved? A lot of my automatons rely on these sensors and I still have more sensors waiting to be added.
Thank you @kevinvincent for this awesome integration. It is easy to setup and install and pair the sensors. You are the man!