The Victron SmartSolar Bluetooth Failure Pattern
Marine solar installers deal with Victron Bluetooth failures more than Victron likes to admit — there are five independent forum threads confirming the same failure mode after Android OS updates.
The pattern is consistent across threads: Bluetooth works fine at installation. An Android OS upgrade happens — often Android 13. The controller becomes undiscoverable. Power cycling provides a temporary fix. The problem recurs. Factory Bluetooth reset sometimes helps; sometimes it doesn't. The affected models are the 75/15, 100/20, and 100/30 — the three models that make up the bulk of professional marine installs.
Why This Matters for Installers
On a controller where Bluetooth is the primary (sometimes only) way to read live charge state and configure charge profiles, "Bluetooth not working" is not a minor inconvenience. It's a monitoring outage. If the controller is accessible, that means a laptop and a VE.Direct cable. If the controller is in a hard-to-reach position — inside a dock housing, behind a panel, up a mast — it means a site visit.
For a marine electrician, a site visit to fix a manufacturer firmware issue is a callback. You either absorb it or have a difficult conversation with the customer.
This failure is not a freak event. Five independent threads, across Victron Community (×3), Victron Community active discussions (×1), and DIY Solar Forum (×1), document the same failure mode, the same temporary fix behaviour, and the same models. A failure pattern that appears across five independent sources is not an outlier.
Why Bluetooth-Only Fails Here
The Victron SmartSolar uses Bluetooth Low Energy (BLE) as its sole wireless monitoring protocol. BLE is part of the Android BLE stack — and Android's BLE implementation has changed meaningfully between major versions, particularly in Android 12 and 13.
When the Android BLE stack changes and the controller firmware doesn't track it, the device can stop appearing in the Victron Connect app. The controller hasn't failed — the wireless stack has diverged from what the app and the controller's firmware expect.
This is a known problem with BLE-only implementations on Android. The solution is dual-mode Bluetooth: include both Bluetooth Classic (BR/EDR) with the Serial Port Profile (SPP), and BLE.
The Dual-Mode Approach
Bluetooth Classic SPP operates over the BR/EDR transport layer. This is the same transport that has been in Android since version 2.0. It does not change meaningfully between Android 8 and Android 14. A device that connects via SPP on Android 8 will connect the same way on Android 14.
BLE is the modern protocol — lower power, higher data throughput in some modes, better for mobile apps that want background operation. The right architecture is to use both: SPP for legacy workshop diagnostic tools that expect a serial port, BLE for modern mobile apps.
The CC2564MODA module implements both. One chip, dual-mode, no switching required. Monitoring works independently of which Android version the customer's phone is running when the OS auto-updates overnight.
The Cost of Not Doing This
A marine solar installer's callback is approximately 1–2 hours of labour at NZ marine electrician rates. One callback offsets the entire margin on the controller. Two callbacks exceed the cost of the controller itself. The Bluetooth failure pattern documented across those five threads is not a minor product deficiency — it is a callback generator, and the cost lands on the installer, not Victron.
A controller that does not generate Bluetooth callbacks is worth more to an installer than a cheaper controller that might. This is the value proposition that the dual-mode architecture enables — not a feature spec, but a reduction in a specific, documented, quantified cost.
MicroCore Systems is building a dual-mode Bluetooth (SPP + BLE) MPPT solar controller for marine installations. Build log on Hackaday.io. Contact: jonathan@microcoresystems.co.nz