search

kevinvincent / ha-wyzesense

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

Wyze Sense sensors stopped working #84

Open damato300x7 opened 4 years ago

damato300x7 commented 4 years ago

I woke up today and none of my sensors are working. Here is a link to my log.

https://pastebin.com/uvvGftVJ

Hope someone can help.

bseishen commented 4 years ago

Same issue, I think my home assistant docker was updated that broke this. 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

damato300x7 commented 4 years ago

i uninstalled wyze sense component and then re-installed it and all is well again. Although I had to go around and reset each sensor. But it is working again.

papacrown commented 4 years ago

Getting the same issue, I have lots of sensors so I'm going to hold out for a fix on this before having to go around and reseting them.

yukdumboobumm commented 4 years ago

+1

A restart of HA worked for me, but this is the third time in two days this has occurred. Not finding much useful in my logs though.

damato300x7 commented 4 years ago

Mine just quit working again.

Pelphry17 commented 4 years ago

My sensors seem to stop reporting after roughly a day or so of working fine. A restart of the Homeassistant server fixes it every time. No need to re-add them just a reboot and they will report fine. I am running HassIO in a Virtual Box machine. Will keep checking logs for any issues I can find.

kevinvincent commented 4 years ago

Can all of you please try updating to version 0.0.7. Please make sure to follow the update instructions where you must retrigger each sensor once updating the component for the sensor to show up in Home Assistant (it's only a one-time thing). After you do that it should solve the error that @bseishen and @damato300x7 posted above.

badrobit commented 4 years ago

@kevinvincent could you explain what you mean by "retrigger"? Thanks!

photinus commented 4 years ago

If you go and open each door/window/contact sensor and trigger each motion sensor, that is what is intended. They will show up as missing entities until you do thay

On Sat, Jan 18, 2020, 6:56 AM Mat notifications@github.com wrote:

@kevinvincent https://github.com/kevinvincent could you explain what you mean by "retrigger"? Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kevinvincent/ha-wyzesense/issues/84?email_source=notifications&email_token=AC362MJRSGPAOGAFEV6WKDLQ6MKBHA5CNFSM4KFGKUZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJJ2BFQ#issuecomment-575905942, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC362MMVQGI4POS5EEYOLILQ6MKBHANCNFSM4KFGKUZQ .

Pelphry17 commented 4 years ago

Mine have been solid since the update. Thank You.

broyuken commented 4 years ago

Mine have been worse since the update. Not sure if it was this update or updating HA, but I have to uninstall/reinstall this addon then restart HA to get them back.

peterpme commented 4 years ago

I recently started having this issue soon. For what it's worth, I didn't update for awhile. Thanks for your help!

damato300x7 commented 4 years ago

The last time I had this issue I switched to the master instead of the .6 or .7 and I have had 0 issues in 12 days. I dont know the difference between the versions but no issues so far so I am going to leave it as is for now.

kevinvincent commented 4 years ago

@damato300x7 master is actually now the same as 0.0.7 (it was ahead of 0.0.6 a couple of weeks ago).

javand commented 4 years ago

I also have this issue...I been on 0.0.7, I would uninstall then reinstall - retrigger all the sensors and everything would be working fine for a day or two then....nothing. The sensors will just stop working.

photinus commented 4 years ago

@javand Can you put your logs for the wyze component into debug and share a full run from start to not working?

javand commented 4 years ago

@javand Can you put your logs for the wyze component into debug and share a full run from start to not working?

Sure but it may take a few days. I just restarted HA and afterwards all the sensors started working again. Duplicating the issue seems to take a few days - I'll turn on debug again and attach them.

kevinvincent commented 4 years ago

@javand Whenever the issue appears again can you also ssh into the box and run dmesg and post the output as well? It will let us see if theres any issues going on with usb disconnects and reconnects (which this component does not handle at all and is the next area of improvement).

javand commented 4 years ago

@javand Whenever the issue appears again can you also ssh into the box and run dmesg and post the output as well? It will let us see if theres any issues going on with usb disconnects and reconnects (which this component does not handle at all and is the next area of improvement).

Will do

biga888 commented 4 years ago

Hi Kevin, I am having the same symptoms. Do you want the dmesg from the host machine or HA?

here is my host system. https://pastebin.com/qLDAjGXC

javand commented 4 years ago

As promised @kevinvincent @photinus

Took a few lines out the ha log to get under the pastebin limit but as you can see - the sensors stop working sometime on 1/31.

ha log: https://pastebin.com/KsTUjP8u dmesg log: https://pastebin.com/UeiFNYUz

javand commented 4 years ago

I think my issue could be related to this: https://github.com/home-assistant/home-assistant/issues/21291 . Took a look at my latest logs from dmesg and noticed a usb disconnect. Not sure if this is a bug related to the Ubuntu kernel I'm running but going to attempt to update to the latest patch.

yukdumboobumm commented 4 years ago

Just throwing this out there in case it sparks any aha-moments: I'm running on a raspberry pi 4 with up-to-date Buster, and I can confirm that every time my sensors stop working my wifi also cuts out. The wifi is a known issue in the kernel, see (https://github.com/raspberrypi/firmware/issues/1196) This affects 3 of the Pi's I'm running at home (but not all of them).

I can't say yet for certain that the issue are related. I'll keep trying to break things and report back with any new information.

javand commented 4 years ago

Update: Even though I updated to the latest Ubuntu kernel I still experienced the issue of the usb disconnects via ohci drivers. Since I'm running this in a VM I then installed new usb card to attempt run the wyze hub via Ubuntu's usb 3 xhci drivers. I can report this has been stable for 5 days now, where as in the past it would barely make it past 24hrs - if you can use xhci drivers I would attempt doing so.

gterpstra75 commented 4 years ago

I have been having what sounds like the same problem for several months now. My wyze sensors stop reporting usually within 24-hrs but sometimes they will last for a few days after a reboot. A reboot will always fix the problem. When my wyze sensors stop working, the wyse hub still has a blue light. I am running HA in docker on a ubuntu-18.04 LTS machine.

@javand, did ubuntu's usb 3 xhci drives fix your issue?

bschatzow commented 4 years ago

I am in the process of moving from a Pi to a windows VM. I do I configure the USB on the windows machine to look the same to this sensor?

javand commented 4 years ago

@gterpstra75 yes I had the same symptoms. I moved the hub to a USB 3 port and used the xhci drivers. It's been running great for over a week now.

peterpme commented 4 years ago

Hey @javand I'm running Ubuntu and I have my wyze plugged into a USB3 port. How do I switch to the XHCI drivers? I tried googling around but it doesn't seem as easy as it looks?

Thanks!

javand commented 4 years ago

@peterpme I’m using virtualbox so it’s just a simple setting: https://www.virtualbox.org/manual/ch03.html#settings-usb

gterpstra75 commented 4 years ago

Thanks @javand for the information. I am running hass.io in docker under ubuntu 18.04 LTS machine. I just installed an UBS 3.0 pci card in the base machine. Of course, I moved the wyze hub to the card but don't expect any difference. Once it fails (as I expect anyways) I will reconfigure my setup with virtualbox. Thanks for your help.

RonSpawnson commented 4 years ago

Also having this issue :(

gterpstra75 commented 4 years ago

Update: I did try virtualbox running under ubuntu 18.04 LTS machine. I tried all 3 USB drivers (OHCI, EHCI & xHCI). I actually had a faster failure rate with this setup. I am currently running with the following setup: Docker under ubuntu 19.10 machine USB 3.0 PCI card with power connected.

So far after 4 days, I haven't had any failures. But actually, it is still a little too early to tell because I have rebooted HA a couple of times to install updates over the past four days. But, this has been so far the most reliable setup for me. I need WyzeSense to work because I have 10 door and 15 motion sensors.

drewh1991 commented 4 years ago

@javand thanks for the tip, switching to XHCI seems to have resolved the issue for me as well. Currently running for a few days without disconnects. I'll report back if this doesn't do the trick.

Edit: It's been about 30 days and I've had zero disconnect issues since making this change. I'd say this solved the problem.

hack2spider commented 4 years ago

I thought I`m the only one I think I spent 5 days trouble shooting this ...

Im running my hassio under poxmox and I cant seem to pass-through the USB anymore this was after 0.109.2 update ?

the proxmox setup is as follows 👍

root@pve:~# lusb -bash: lusb: command not found root@pve:~# lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1a86:e024 QinHeng Electronics Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@pve:~# dmesg | grep hidraw [ 1.711037] hidraw: raw HID events driver (C) Jiri Kosina [ 1.712287] hid-generic 0003:1A86:E024.0001: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [ 13.634923] hid-generic 0003:1A86:E024.0002: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [ 17.947228] hid-generic 0003:1A86:E024.0003: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [ 18.522724] hid-generic 0003:1A86:E024.0004: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [ 19.482384] hid-generic 0003:1A86:E024.0005: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [ 20.223582] hid-generic 0003:1A86:E024.0006: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [ 22.335565] hid-generic 0003:1A86:E024.0007: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257259.345169] hid-generic 0003:1A86:E024.0008: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257259.896521] hid-generic 0003:1A86:E024.0009: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257260.748569] hid-generic 0003:1A86:E024.000A: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257261.853362] hid-generic 0003:1A86:E024.000B: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257262.728236] hid-generic 0003:1A86:E024.000C: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257267.860145] hid-generic 0003:1A86:E024.000D: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257268.437071] hid-generic 0003:1A86:E024.000E: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257269.383774] hid-generic 0003:1A86:E024.000F: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257270.128906] hid-generic 0003:1A86:E024.0010: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257272.248621] hid-generic 0003:1A86:E024.0011: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257444.330744] hid-generic 0003:1A86:E024.0012: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257444.883025] hid-generic 0003:1A86:E024.0013: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257445.734927] hid-generic 0003:1A86:E024.0014: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257446.838821] hid-generic 0003:1A86:E024.0015: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257447.713816] hid-generic 0003:1A86:E024.0016: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257452.842635] hid-generic 0003:1A86:E024.0017: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257453.418912] hid-generic 0003:1A86:E024.0018: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257454.365397] hid-generic 0003:1A86:E024.0019: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257455.109833] hid-generic 0003:1A86:E024.001A: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [257457.222442] hid-generic 0003:1A86:E024.001B: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258088.008143] hid-generic 0003:1A86:E024.001C: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258092.134055] hid-generic 0003:1A86:E024.001D: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258555.685770] hid-generic 0003:1A86:E024.001E: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258556.237786] hid-generic 0003:1A86:E024.001F: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258557.097555] hid-generic 0003:1A86:E024.0020: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258558.205953] hid-generic 0003:1A86:E024.0021: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258559.081580] hid-generic 0003:1A86:E024.0022: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258564.217883] hid-generic 0003:1A86:E024.0023: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258564.793495] hid-generic 0003:1A86:E024.0024: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258565.736281] hid-generic 0003:1A86:E024.0025: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258566.477995] hid-generic 0003:1A86:E024.0026: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 [258568.589370] hid-generic 0003:1A86:E024.0027: hiddev0,hidraw0: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:14.0-1/input0 root@pve:~# qm set 100 -usb2 host=1a86:e024 update VM 100: -usb2 host=1a86:e024 root@pve:~# cat /etc/pve/qemu-server/100.conf | grep usb usb0: host=1a86:e024 usb1: host=1a86:e024 usb2: host=1a86:e024 root@pve:~#

home assistant VM 100 shows the following :

➜ /workspace lsusb
zsh: corrupt history file /root/.zsh_history ➜ /workspace lsusb Bus 005 Device 001: ID 1d6b:0001 Bus 003 Device 001: ID 1d6b:0001 Bus 002 Device 002: ID 0627:0001 Bus 001 Device 001: ID 1d6b:0002 Bus 003 Device 003: ID 1a86:e024 Bus 004 Device 001: ID 1d6b:0001 Bus 002 Device 001: ID 1d6b:0001 Bus 003 Device 002: ID 1a86:e024 ➜ /workspace dmesg | grep hidraw [ 1.745842] hidraw: raw HID events driver (C) Jiri Kosina [ 2.683429] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Mouse [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0 [ 3.157849] hid-generic 0003:1A86:E024.0002: hiddev96,hidraw1: USB HID v1.00 Device [HID 1a86:e024] on usb-0000:00:1d.0-1/input0 ➜ /workspace

so home assistant config should look for hidraw1 which I have set but no luck ...

any help appreciated.

1337derpdaderp commented 4 years ago

I am also having this problem. I've had it for a variety of HA versions, (i should have never upgraded in the begining). Wyze sensors just stop responding on HA side randomly (could be a day or longer sometimes). They still flash red when you walk by them but HA doesn't recognize any change in their status.

Any update to this? Wishing I just had xiaomi motion sensors. Those seem to be flawless...

Running HA on raspi4.

gterpstra75 commented 4 years ago

I am also having this problem.

Have you upgraded to the latest version?

damato300x7 commented 4 years ago

I’ve had 0 issues since upgrading 0.0.7

1337derpdaderp commented 4 years ago

I’ve had 0 issues since upgrading 0.0.7

What HA version?

1337derpdaderp commented 4 years ago

I am also having this problem.

Have you upgraded to the latest version?

for HACS Wyze? yes.

bseishen commented 4 years ago

Zero issues with latest 0.0.7 with running it in an unraid docker. It's been stable. One thing that has helped me a lot is creating a udev rule to create a device at /dev/wyzesense

-- Ben S. Eishen On 5/22/2020 8:23:17 AM, 1337derp notifications@github.com wrote: I am also having this problem. Have you upgraded to the latest version? for HACS Wyze? yes. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [https://github.com/kevinvincent/ha-wyzesense/issues/84#issuecomment-632688216], or unsubscribe [https://github.com/notifications/unsubscribe-auth/AAHXJJYE3ZRWS55S4G2M3K3RSZ4ELANCNFSM4KFGKUZQ].

atechnical commented 4 years ago

I am having this issue. I'm running HA on a virtualbox on a windows 10 pc. Everything was working fine until I added 8 more sensors mostly door/window sensors. Now I would have to restart the VM multiple times a day to keep it running.

gterpstra75 commented 4 years ago

I am having this issue. I'm running HA on a virtualbox on a windows 10 pc. Everything was working fine until I added 8 more sensors mostly door/window sensors. Now I would have to restart the VM multiple times a day to keep it running.

Which version of Wyzesense are you running? (0.8?)

atechnical commented 4 years ago

Yes version 0.8. I'm not even sure it's the add on, there are threads in the Wyze forums for the same issue and the users are not using HA. . Thanks

On Thu, Jun 4, 2020, 1:10 PM gterpstra75 notifications@github.com wrote:

I am having this issue. I'm running HA on a virtualbox on a windows 10 pc. Everything was working fine until I added 8 more sensors mostly door/window sensors. Now I would have to restart the VM multiple times a day to keep it running.

Which version of Wyzesense are you running? (0.8?)

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

gterpstra75 commented 4 years ago

Yes version 0.8. I'm not even sure it's the add on, there are threads in the Wyze forums for the same issue and the users are not using HA. . Thanks

Good. I know that I have issues for several months with wyzesense stopping to work. I have 25 motion and 11 door sensors now. So I need this to work. I have been running consistently for over a month now w/o any errors. You may want to look at:

https://github.com/kevinvincent/ha-wyzesense/issues/141#issue-622707767 https://github.com/kevinvincent/ha-wyzesense/issues/114#issuecomment-619629898

There are also comments on virtualbox setup: I can not find the link now but basically it stated success with using USB 3.0 drivers. I didn't have success but worth a try.

kzaoaai commented 4 years ago

back when I was using virtualbox, switching to usb 1.1 (OHCI) fixed my issues, so you might want to try that if switching to 3.0 doesn't work.

atechnical commented 4 years ago

Thanks for the replies. I recently upgraded to the latest edition of Virtual Box.not sure the sensors stopped working directly after but I've rolled it back to 6.1.4 along with the corresponding Expansion pack that impacts the USB connections. I'll see if that works and update this thread. 12 hours and it's been fine so far.

atechnical commented 4 years ago

Well..it didn't last long. Some sensors would work while others stopped again. I've moved onto changing to USB 3.0 settings as suggested in the comment you suggested. https://github.com/kevinvincent/ha-wyzesense/issues/20#issuecomment-595829838

atechnical commented 4 years ago

Rolling back to a previous Virtual Box version and switching to USB 3.0 didn't work. I've had to reinstall the add-on to get back the sensors. This time it lasted about 9-10 hours. The following is the log when it stopped working today. The last successful sensor notification occurred at 15:02.

2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa532319000001729f9a5f70ab373737413436413002000005000205000000020900590006e7' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa532319000001729f9a5f70ab373737413436413002000005000205000000020900590006e7' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9a5f70ab3737374134364130020000050002050000000209005900' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa532319000001729f9a5f70ab373737413436413002000005000205000000020900590006e7' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa532319000001729f9a5f70ab373737413436413002000005000205000000020900590006e7' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9a5f70ab3737374134364130020000050002050000000209005900' 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:00:19 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9acf4da1373737453846414401145700010000c64c085d' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9acf4da1373737453846414401145700010000c64c085d' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9acf4da1373737453846414401145700010000c64c' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9acf4da1373737453846414401145700010000c64c085d' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9acf4da1373737453846414401145700010000c64c085d' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9acf4da1373737453846414401145700010000c64c' 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:00:49 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:01:33 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9b7389a1373737413436413002175f00010034d458086c' 2020-06-10 15:01:33 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9b7389a1373737413436413002175f00010034d458086c' 2020-06-10 15:01:33 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9b7389a1373737413436413002175f00010034d458' 2020-06-10 15:01:33 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:01:33 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531935000001729f9bac850ea2373737414334323002011763076a' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531935000001729f9bac850ea2373737414334323002011763076a' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5335, Payload=b'000001729f9bac850ea2373737414334323002011763' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5335) 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555335ff0286' 2020-06-10 15:01:48 INFO (Thread-2) [custom_components.wyzesense.wyzesense_custom] LOG: time=2020-06-10T15:01:19.109000, data=b'a2373737414334323002011763' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9bac9da2373737414334323002176000010117634f0823' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9bac9da2373737414334323002176000010117634f0823' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9bac9da2373737414334323002176000010117634f' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:01:48 DEBUG (Thread-2) [custom_components.wyzesense.binary_sensor] {'available': True, 'mac': '777AC420', 'state': 1, 'device_class': 'motion', 'timestamp': '2020-06-10T15:01:19.133000', 'rssi': -79, 'battery_level': 96} 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531935000001729f9bbcfe0ea23737374134364130020134d50884' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531935000001729f9bbcfe0ea23737374134364130020134d50884' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5335, Payload=b'000001729f9bbcfe0ea23737374134364130020134d5' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5335) 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555335ff0286' 2020-06-10 15:01:53 INFO (Thread-2) [custom_components.wyzesense.wyzesense_custom] LOG: time=2020-06-10T15:01:23.326000, data=b'a23737374134364130020134d5' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9bbd10a2373737413436413002175f00010134d5580840' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9bbd10a2373737413436413002175f00010134d5580840' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9bbd10a2373737413436413002175f00010134d558' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:01:53 DEBUG (Thread-2) [custom_components.wyzesense.binary_sensor] {'available': True, 'mac': '777A46A0', 'state': 1, 'device_class': 'motion', 'timestamp': '2020-06-10T15:01:23.344000', 'rssi': -88, 'battery_level': 95} 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531935000001729f9bdf900ea2373741354631343702013ddd084f' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531935000001729f9bdf900ea2373741354631343702013ddd084f' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5335, Payload=b'000001729f9bdf900ea2373741354631343702013ddd' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5335) 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555335ff0286' 2020-06-10 15:02:02 INFO (Thread-2) [custom_components.wyzesense.wyzesense_custom] LOG: time=2020-06-10T15:01:32.176000, data=b'a2373741354631343702013ddd' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9bdfaaa23737413546313437021b610001013ddd4d090d' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9bdfaaa23737413546313437021b610001013ddd4d090d' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9bdfaaa23737413546313437021b610001013ddd4d' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:02:02 DEBUG (Thread-2) [custom_components.wyzesense.binary_sensor] {'available': True, 'mac': '77A5F147', 'state': 1, 'device_class': 'motion', 'timestamp': '2020-06-10T15:01:32.202000', 'rssi': -77, 'battery_level': 97} 2020-06-10 15:02:02 DEBUG (MainThread) [custom_components.lutron_caseta_pro.light] Writing light OUTPUT value: 3 1 0 None 2020-06-10 15:02:02 DEBUG (MainThread) [custom_components.lutron_caseta_pro] Read value for host 192.168.1.188: OUTPUT 3 1 0.000000 2020-06-10 15:02:02 DEBUG (MainThread) [custom_components.lutron_caseta_pro.light] Got light OUTPUT value: OUTPUT 3 1 0.000000 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531935000001729f9c41920ea2373737414334323002001764070d' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531935000001729f9c41920ea2373737414334323002001764070d' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5335, Payload=b'000001729f9c41920ea2373737414334323002001764' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5335) 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555335ff0286' 2020-06-10 15:02:28 INFO (Thread-2) [custom_components.wyzesense.wyzesense_custom] LOG: time=2020-06-10T15:01:57.266000, data=b'a2373737414334323002001764' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9c41aba2373737414334323002176000010017644f07c7' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9c41aba2373737414334323002176000010017644f07c7' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9c41aba2373737414334323002176000010017644f' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:02:28 DEBUG (Thread-2) [custom_components.wyzesense.binary_sensor] {'available': True, 'mac': '777AC420', 'state': 0, 'device_class': 'motion', 'timestamp': '2020-06-10T15:01:57.291000', 'rssi': -79, 'battery_level': 96} 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa5303320187' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa5303320187' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5332, Payload= 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5332) 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555332ff0283' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=5333, Payload=b'000001729f9cf182' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa55530b33000001729f9cf18204b1' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531935000001729f9c749e0ea2373741354631343702003dde07f3' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531935000001729f9c749e0ea2373741354631343702003dde07f3' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5335, Payload=b'000001729f9c749e0ea2373741354631343702003dde' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5335) 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555335ff0286' 2020-06-10 15:02:42 INFO (Thread-2) [custom_components.wyzesense.wyzesense_custom] LOG: time=2020-06-10T15:02:10.334000, data=b'a2373741354631343702003dde' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9c74b8a23737413546313437021b610001003dde4c08b055aa5333ff0284' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9c74b8a23737413546313437021b610001003dde4c08b0' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9c74b8a23737413546313437021b610001003dde4c' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.binary_sensor] {'available': True, 'mac': '77A5F147', 'state': 0, 'device_class': 'motion', 'timestamp': '2020-06-10T15:02:10.360000', 'rssi': -76, 'battery_level': 97} 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa5333ff028455aa531d19000001729f9c74b8a23737413546313437021b610001003dde4c08b0' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa5333ff0284' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=53FF, Payload=ACK(5333) 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Trying to parse: b'55aa531d19000001729f9c74b8a23737413546313437021b610001003dde4c08b0' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Received: b'55aa531d19000001729f9c74b8a23737413546313437021b610001003dde4c08b0' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] <=== Received: Packet: Cmd=5319, Payload=b'000001729f9c74b8a23737413546313437021b610001003dde4c' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===> Sending: Packet: Cmd=53FF, Payload=ACK(5319) 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555319ff026a' 2020-06-10 15:02:42 DEBUG (Thread-2) [custom_components.wyzesense.binary_sensor] {'available': True, 'mac': '77A5F147', 'state': 0, 'device_class': 'motion', 'timestamp': '2020-06-10T15:02:10.360000', 'rssi': -76, 'battery_level': 97}

On Fri, Jun 5, 2020 at 2:35 AM kzaoaai notifications@github.com wrote:

back when I was using virtualbox, switching to usb 1.1 (OHCI) fixed my issues, so you might want to try that if switching to 3.0 doesn't work.

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

atechnical commented 4 years ago

This time I set the Virtual Box adapter to 1.0 and notifications worked for the shortest time period yet. I received the following erno110 error this morning when it stopped working.

Logger: custom_components.wyzesense.wyzesense_custom Source: custom_components/wyzesense/wyzesense_custom.py:373 Integration: wyzesense (documentation) First occurred: 8:51:41 AM (1 occurrences) Last logged: 8:51:41 AM

[Errno 110] Operation timed out

Troublebrewing commented 4 years ago

I think this may be the same as issue #153 and #157

I am running wyzesense as a component installed via HACS. Home Assistant Host OS: HassOS 4.11 (VirtualBox VM on Windows 10 host machine) HA version: 0.114.2 HACS: 1.3.3 Wyzesense: 0.0.9

Getting nearly the same error in system log as @atechnical My logs from 5 minutes leading up to error: https://pastebin.com/TJ1Y6izb

I have tried changing the USB controller in the VM to USB 1.0 and USB 2.0. I can try 3.0 tonight but this doesn't appear to solve the problem.