smoke007

I got this error recently and found this thread. I found that after I restarted my Frigate server, the error was gone and Double Take started working again. - Update,...

I documented how to remove these contact sensors with all zero MAC, from the HA GUI at https://github.com/kevinvincent/ha-wyzesense/issues/130#issuecomment-624960162 I also confirmed in that post that this sensor no longer works...

@blulite My test Wyze contact sensor just ate a battery, while not being used... (Spoiler, I'm guessing that might have something to do with what's wrong with this sensor) Anyways,...

@P1X3 > I tried to remove this device using its actual mac address and the 00000000 mac. Neither produced anything. I was able to remove the sensor with all zero...

@WarbleSync Have you tried connecting your contact sensor back to the Wyze Bridge? I did and it would no longer work with Wyze hardware either. Wyze support warrantied it for...

@gullygossner @adtinnis I had the exact same issue with a contact sensor that was not being used, suddenly ate the battery. After replacing with a new battery, scanning for the...

@teslawave Yes, see my post here https://github.com/kevinvincent/ha-wyzesense/issues/130#issuecomment-624960162

@spike886 and @ajfriesen, This is a known issue that goes back to Jun 2019. See the common fixes in https://github.com/esphome/issues/issues/455. You're right, changing logging level sometimes fixes the corruption during...