Yes, this worked for me last time… and again this time. For some reason, one of my contact sensors started causing the issue.
@mike.maxwell - This issue was caused by my Third Reality contact sensors on Generic Zigbee Contact Sensor (no temp) device type. It started throwing a 200 for battery level (we have discussed this before), which I’m assuming is what crapped out the HomeKit integration. I have moved all of my Third Reality motion and contact sensors to the Generic Zigbee drivers that are not the “(no temp)” type, and it brought my HomeKit integration back online. These drivers seem to be quite an issue. I’ll monitor using the other drivers and see what happens.
@gopher.ny - Is there a way to keep incorrect values from crashing the integration, or at least providing a report on what is causing the issue? I have Hubitat Homebridge v2 running on Homebridge in my other house and I have NEVER had these kinds of issues. There, I see errors for invalid values (like thermostat set temp too low) in the Homebridge logs, but it seems to filter them out so they don’t crash HomeKit.
