My hub was back at it tonight. It coincided with a driver update from another dev being installed (automatically, not through CLI), so I’m pretty certain that was the cause.
2022-06-16T21:47:05 - Timestamp on the new version of the driver
2022-06-16T22:03:20 - Hub event - disconnected (begins cycling offline/online)
2022-06-16T22:10:19 - Hub event - HubUpdated (presumably indicating the driver install)
2022-06-16T23:24:49 - Hub stops cycling and remains online. Querying installed drivers shows the driver in question has the new timestamp. Logcat connects, and logs are going absolutely crazy, processing the backlog from the past hour. The commands below are usually generated by the device several (I think about 5) seconds apart:
2022-06-16T23:28:12.191489442+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,02,1C08,08,00,****DISARMED**** Ready to Arm $
2022-06-16T23:28:12.231722215+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,01,1C08,08,00,****DISARMED**** Ready to Arm $
2022-06-16T23:28:12.286172427+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,02,1C08,08,00,****DISARMED**** Ready to Arm $
2022-06-16T23:28:12.327514421+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,01,1C08,08,00,****DISARMED**** Ready to Arm $
2022-06-16T23:35:03 - Hub event - disconnected (begins cycling offline/online). Logcat remains connected, but processing slows to a crawl. Same device for comparison, now showing at 15s intervals:
2022-06-16T23:59:30.385576465+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,02,1C08,08,00,****DISARMED**** Ready to Arm $
2022-06-16T23:59:44.024288471+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,01,1C08,08,00,****DISARMED**** Ready to Arm $
2022-06-17T00:00:05.042289481+00:00 TRACE Honeywell-Ademco Envisalink RX < %00,02,1C08,08,00,****DISARMED**** Ready to Arm $
@nayelyz Was there any resolution to this issue which seems related?