@nayelyz I found a potential bug in the firmware health check which is causing it to prematurely mark devices offline before the health check interval expires. I’ve sent the build team the logs, memory dumps and debug details of the related firmware code so you can analyze it.
To summarize, if the health check interval is set to 6 hours, the hub is marking the device offline between 2 and <6 hours. So what I see is that often the device does report back within the configured 6 hours but since the hub marked it offline prematurely, when the report comes in the firmware not marks it online. So it’s basically stuck in a loop of offline and online. It’s not limited to Schlage locks but other devices also.