Wyze sense sensor integrations

I have not experienced this at all on the Wyze sensors…but I have with my Xiaomi Smart Door Windows Sensor. Which is unfortunate, because it gives a battery indication without having to activate the sensor. The Wyze sense units are on my doors, so they update about 15 times a day…and have not experienced any issues. Maybe there is a proximity issue…? If you are attached directly to your server USB port, I heard that you should use a USB extension cable to get the receiver up and away from the PC’s ports due to RF noise at the server. I have not had to do this yet, but I am planning on it. Also, I am running ProxMox on a i5 with 16gb of ram and a 1 TB SSD…and my HASSIO is running virtualized with no issues whatsoever.

Hope this is helpful.

I have had it plugged directly into the USB port, and currently have it on a extension cable. One of the sensors that give me issues is only about 6ft away.

@thychubbz That automation won’t fire unless the entity’s state actually changes to below 98. As in, if it were at 98 and then went to 97, it would fire. If it was already below 98 when you created the automation it won’t fire.

Struggling with this and really hoping for some insight.

I recently made the jump from Hassbian to Hassio via HassOS running in an Oracle Virtualbox on a Windows 10 machine. I was able to set everything up from scratch but seemingly fell out of love with z-wave pretty quickly. I saw these Wyze sensors and the integration and thought, why not.

Long story short, I cannot get HassOS to recognize the device. It sees my Aeotec stick, but will not pickup the Wyze hub. I’ve found running the log info that it was on /hiddev96/hidraw1 but that obviously didn’t do anything in the configuration as Hassio or HassOS isn’t recognizing the device.

I’ve allowed USB pathrough in oracle and filtered out the Wyze sensor which showed up as “some chinese name”. My only thought left is HassOS doesn’t play well with hidraw?

Any help is greatly appreciated!

Edit:
I should mention the custom component was installed via HACS with no issues for clarity.

you could try running the gosense app and then use mqtt to get the data into hass

Thanks Glenn,

The gosense app is on the list to try, but i’d like to exhaust efforts into this integration first however.

I was working remote last night, but I’m seeing this “BrokenPipeError” if anyone has any insight?

This was recorded leaving the binary sensor device as “/dev/hidraw0” for reference.

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 82, in setup_platform
    ws = beginConn()
  File "</usr/local/lib/python3.7/site-packages/decorator.py:decorator-gen-2>", line 2, in beginConn
  File "/usr/local/lib/python3.7/site-packages/retry/api.py", line 74, in retry_decorator
    logger)
  File "/usr/local/lib/python3.7/site-packages/retry/api.py", line 33, in __retry_internal
    return f()
  File "/config/custom_components/wyzesense/binary_sensor.py", line 80, in beginConn
    return Open(config[CONF_DEVICE], on_event)
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 561, in Open
    return Dongle(device, event_handler)
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 297, in __init__
    self._Start()
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 492, in _Start
    self._Inquiry()
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 398, in _Inquiry
    resp = self._DoSimpleCommand(Packet.Inquiry())
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 393, in _DoSimpleCommand
    self._DoCommand(pkt, cmd_handler, timeout)
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 379, in _DoCommand
    self._SendPacket(pkt)
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 331, in _SendPacket
    pkt.Send(self.__fd)
  File "/config/custom_components/wyzesense/wyzesense_custom.py", line 106, in Send
    ss = os.write(fd, pkt)
BrokenPipeError: [Errno 32] Broken pipe

Got this one figured out for anyone having similar issues.

Ended up being windows drivers for CH341, once installed the Virtualbox was able to pass the info through to Hassio no problem.

1 Like

Have retired all my zigbee sensors for these. They work great. Thanks for all the hard work on this integration.

Was wondering if anyone knows of a way to disable the led on the door sensors. Its not a huge deal just wondering if it was possible.

On the ones that I don’t want to see…I used a small piece of white electrical tape. Unless you are wanting to remove them to lower the power requirement…that is a different story with a very small soldering iron. :slight_smile:

Yeah i don’t want to crack them open. I figure desoldering was probably the only way just thought I would ask. :slight_smile:

The one at the front door is the only one that is even noticeable so not a big deal.

This is really incredible/awesome! Sensors respond incredibly fast and accurately. Was also really easy to set up!

I just did a new install of Hassio and when installing wyze sense I get Platform error binary_sensor.wyzesense - No module named ‘retry’
I saw in the troubleshooting to do the following:
Create / Modify the file /etc/udev/rules.d/99-com.rules on your machine and insert `KERNEL==“hidraw*”, SUBSYSTEM==“hidraw”, MODE=“0664”, GROUP=“homeassistant”
Where is the location of this file?
I did an uninstall, manual install then a new install. Working now. Not sure what the issue was.

Had an issue with my VM updating to 101.2 so had to restore off a backup. Now all my Wyze sense devices are gone. Is this normal? Anyway to retrieve them or do I just need to repair everything. Never experienced this before. I have had to restore off a snapshot before and never had an issue.

Might have to unplug and re-plug in the dongle (see comments above).

I’m also running a VM and have to do the same if the PC reboots, it does the same thing and shows the sensors are not connected until I unplug/re-plug and restart Home assistant.

I know you may not have restarted the host PC, but throwing out ideas based on the wonky update (I’ve held off on the latest as I think it’ll break my android actionable notifications too).

Let us know if you figure out the issue.

Just wanted to say thanks again for this integration!
I have been replacing the reed switches with little membrane buttons glued to the outside and now have HA enabled wireless buttons all over my house.

Hi

Anyone knows how to pass the bridge to a Unraid VM? I see it as hidraw0, i can pass it to a docker, but not a VM.

Also, when I plug/unplug, my unraid GUI freezes until I reboot the server. Weird.

Thank you!

Yes make sure its selected in the usb options in the VM. Hit edit and scroll to the bottom. Mine comes up as QinHeng Electronics and I had to use hidraw1.

Hmmm, mine doesnt show up at all. :frowning:

try another usb port sometimes the ports are on different buses. My Unraid doesn’t like my Usb3 ports for some reason.

I am getting this error since the 101.2 update…Blegh I have submitted it to github but we will see looks like something with python.