elyorkhakimov

I'm having similar issues on gosense. Looks like the parser is unable to make sense of one of the three message types. (I've only seen three unique messages, not counting...

this is what the misinterpreted 39-byte long message looks like in Node-Red, where I've subscribed to mqtt topic from gosense 

thank you @raetha for the follow up. I have been working around this issue in ha-gosenseapp by filtering out messages that do not parse. I don't believe this is a...

OK, noticed some more nuances, let's look at two cases: 1. Motion is detected, and MQTT message with "state:1" is generated. Then, there is no motion happening anymore and 40...

and more debug level logs: 2020-06-19T19:24:55.501110026Z DEBU[0062] readRawHid: 62 bytes: [ 55aa53193500000172ce0a772f0ea2373741313742414202010051067155aa531d1900000172ce0a7732a2373741313742414202176400010100511706e1 ] 2020-06-19T19:24:55.501220514Z DEBU[0062] Trying to parse: 62 bytes: [ 55aa53193500000172ce0a772f0ea2373741313742414202010051067155aa531d1900000172ce0a7732a2373741313742414202176400010100511706e1 ] 2020-06-19T19:24:55.501246966Z DEBU[0062] ==> Sending ACK packet for...

looks like there is a potential workaround, as stated here : https://github.com/kevinvincent/ha-wyzesense/issues/114#issuecomment-641645831 At the moment, a dozen of these sensors are working fine for me, but I had to handle...