Has anyone noticed this entity being created along with the ha-wyzesense integration?
I found it in an integration called met.no: Home.
I have no idea what this could be. This is on a clean installation of Home Assistant (f.k.a Hassio) 104.3 on an RPi3.
Unrelated to my previous post -
If anyone is curious about moving your Wyzesense sensor and devices from one HA instance to another, I stumbled upon how to do it.
Simply install the Wyzesense integration on the new HA instance, then move your existing sensor to the new instance. Assuming the integration is configured correctly on the new instance, all of your devices should simply show up.
Like I said, I merely stumbled upon this process. I still have test functionality and clean up the old instance. But the fact that each device already shows a history (motion sensors are reporting motion detection), the end results seem promising.
Anyway, thought this would be helpful for others.
Also now having Wyze sense stop reporting issue. Twice in 24 hours. No error reports I can find at my skill level. Resets on reboot of HA. This is after a month or so of near perfect performance with about 25 sensors. Unsure if it’s related, but started after upgrade to hass-io 3.9 and 0.105.2. Noticed this also appears to be an issue using the Wyze software (Wyze forums).
I see the same behaviour
mine seems working fine, i’m on Home Assistant 0.104.3
I’m on 105.3 now and Wyze has been working great for me with no issues. Sorry you are seeing issues.
Having issues on 105.3. All sensors unavailable, only message I am seeing is:
2020-02-12 15:31:26 WARNING (SyncWorker_1) [custom_components.wyzesense.binary_sensor] _DoCommand, retrying in 1 seconds…
I’ve tried reinstalling, tried rebooting, tried retriggering the sensors, nothing seems to work.
Hello! I was wondering whether, or not, we need to update firmware for the wyze hub/sensors to get them working? Or would that may break the integration? Or that would not have any impact at all?
For those having issues, what is your Home Assistant install like? I’m running on a Raspberry Pi 3B, HassOS 3.10, Home Assistant Core 0.105.3, and Supervisor 200. At the moment, I have the hub connected directly to the USB port on the back of the Rpi. I bought an extension cable, but I’m getting a 250ft+ radius of connection around my house, so interference from the Pi seems to not be an issue for me.
I installed the integration via HACS and have this in my binary_sensor.yaml file:
#====================================
# Wyze Sense Component
#====================================
- platform: wyzesense
device: auto
I saw that _DoCommand warning once while upgrading from .104 to .105, but after a reboot, it was rock solid again.
I have mostly wired sensors, but these have been a fantastic supplement to my sensors, and I hope they continue to work reliably.
The _DoCommand seemed to be because my vm was not detecting the hub, could not get a blue light on the hub at all. I unplugged the hub for about 2 minutes, plugged it in, restarted the vm and it saw and now all is working. Although it seems my one motion sensor is stuck in an On state. I’ll have to check that out when I get home
Glad you got it working again, alextripp1. It seems like USB disconnects may be the most common issue.
the usb hub sometimes show up as hidraw0 and sometimes hidraw1 or hidraw2 etc.
is there a way to make it fixed?
What ever it was, it is now rock solid again. There have been a few releases since the issue so perhaps something was fixed. Love it, works for me.
The sensor disconnect problem is still happening to me. The problem usually resurfaces 1-3 days after the most recent reboot. I don’t recall this being a problem until the Auto detection feature was introduced. I may try to hard code the sensor path if I can figure out how to pull that data from Home Assistant (fka Hassio).
Here is my experience with Wyze Sensors.
I’ve mostly had no problems other than occasionally after a HA restart that none of the sensors are found. Sometimes another restart addressed this but the most reliable solution was power cycling my RPi (My Wyze USB hub is connected directly to the RPI).
Sometimes after .105 and with 0.7 of the wyzesese Wyze sensors completely stopped working with HA. Restarting HA did not change this; powercycling RPi and Wyze Hub made no difference. I even updated the FW on the hub though one of my Wyze camera but still no luck. Uninstalling Wyze 0.7 and reinstalling made no difference either! I finally ran the wyzescan service and my on/off sensor started wot work again (at least the first 2). My Wyze motion sensors however did not appear to recover from a similar session. On my motion sensor I had to remove them first - then rescan and now they appear to be working again. Properly not relevant but I have ~30 Wyze sensors on my Hub.
I finally had to update the firmware on my bridge from .30 to .33, re-scan in all of my sensors (20) and it’s been flawless since no data mismatch errors or the often unresponsive bridge.
For any users running in Virtualbox having disconnect issues, you may want to check out this issue (and more specifically, this comment) on the github page: https://github.com/kevinvincent/ha-wyzesense/issues/84#issuecomment-587435580
I switched my VM to use XHCI USB drivers a few days ago and I have had no disconnects since. Worth a shot.
Anyone get this working when running HA in a freenas jail?
Getting (Thread-2) [custom_components.wyzesense.wyzesense_custom] [Errno 5] Input/output error and then timeouts on _DoCommand when I try.
I’ve followed the steps to get a USB working in a jail as well and that part looks ok. The device is /dev/uhid0. Updated my config for that as well.
MC,
How did you pull up the file version of your Docker Configuration? I am fairly new to unriad and docker systems.
Mine has been working perfectly for quite some time but all sensors stopped working since yesterday, no symptom no error in the logging. reboot HASS fixed the issue.
Anyone know what could be the cause? And more importantly how can I actively monitoring if it is working or not?