Jt Whissel

Even after 0.9 still have the same issues as before

It starts working again after a good old fashion reboot

I'm running 0.33 and was running fine for about 3 hours then stoped updating.

Here is a the messages up to the point it stopped working. custom_components.wyzesense.wyzesense_custom] Sending: Packet: Cmd=53FF, Payload=ACK(5332) 2020-04-01 03:54:15 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] Sending: b'aa555332ff0283' 2020-04-01 03:54:15 DEBUG (Thread-2) [custom_components.wyzesense.wyzesense_custom] ===>...

@kevinvincent debugged it further, called wyzesense.scan when it stopped working and got this error. Logger: homeassistant.components.websocket_api.http.connection.1814187792 Source: custom_components/wyzesense/wyzesense_custom.py:106 Integration: websocket_api (documentation, issues) First occurred: 10:46:02 PM (2 occurrences) Last logged:...

@VarenDerpsAround all battery levels are over 90% and rssi is above -93 which is good enough for the receiver to receive. So not the issue. (Also RF engineer here for...

Got an error running on master custom_components.wyzesense.wyzesense_custom] Invalid packet: b'55aa5319' 2020-05-05 21:11:07 ERROR (Thread-2) [custom_components.wyzesense.wyzesense_custom] Invalid packet length: 4

Are you hard set on the deadline for today? I was planning on having mine by the end of the weekend. Pretty sure I have the fastest web framework on...

I have the same issue, I got about 70 devices (13 wled devices various esp32 and ezp8266) on my network the only things that disconnect are WLED and it's even...

> Figured someone would say that even though no other ESP related devices on my network has these issues, so I tried it with another wireless router thats not mesh...