@roberdlv I updated version 0.6.4-beta with code that checks to see if all HCIdump threads have completed before processing received data and starting the next data collection cycle. If HCIdump thread does not complete in 10 seconds, then the component leaves for the next period
(in the hope that during this time the HCIdump thread will finish, and it will be possible to process the received data), what will the corresponding HA journal entry be made about.
I doubt that this could lead to the behavior you described, but Iām the same person as everyone, and I can be mistaken.
Try, suddenly it will solve your problem (and indicate the need to look for the reason why the thread does not finish when it should).