Had this exact faff with my SmartSolar 100/30 last winter — turned out the Bluetooth was essentially having a little kip whenever the battery voltage dropped too low overnight, which apparently is "by design" according to Victron's documentation if you squint at it hard enough.
Few things worth checking:
- VE.Direct cable instead of relying on Bluetooth — game changer for reliable logging, no more phantom disconnections
- Check your DVCC settings in VictronConnect, sometimes they get a bit argumentative with each other
- Make sure the controller itself isn't going into low-power mode — there's a setting buried somewhere that a lot of people miss on first setup
The Bluetooth dropout specifically tends to happen when the unit decides the battery is "resting" and throttles everything back. My Fogstar lithium setup sorted most of this because the voltage stays much more stable overnight compared to the old AGMs I was running, which would sag enough to trigger all sorts of dramatic behaviour from the Victron.
If you're monitoring via Cerbo GX rather than direct Bluetooth you'll probably find it's a lot more reliable — the dedicated data connection doesn't throw a wobbler the same way.
What firmware version are you on? There were a couple of updates last year that apparently addressed some of the sleep/wake nonsense, though Victron's changelog reads like it was written by someone actively trying to obscure information.
Anyone else found a fix for this that isn't just "buy a Cerbo"? Asking for my electricity bill.