Supported BMS
Ective
The protocol of the LC-BT range. Once notifications are subscribed, the module transmits once per second on its own — nothing is ever requested. That is why Ective comes first in detection: the attempt sends not a single byte to the device and cannot break anything.
- Type
- Passive — the battery transmits by itself
- Verification
- Verified against a real capture
- Sold as
- Ective · LC-BT range
- Bluetooth service
- ffe0 · Notify ffe4 · no write channel
What the app reads from it
- Pack voltage, current, remaining capacity, state of charge
- Cycles and temperature
- Cell voltages — with a caveat, see below
The cell voltages appear in no description of the protocol. They were found by a sum check: in a real capture the occupied slots added up to exactly the pack voltage. The decoder repeats that check on every frame — if the sum does not match it reports no cell voltages rather than wrong ones.
Ective batteries report no protection states. The app therefore shows "unknown" and not "OK". Unknown is not an all-clear.
My battery does not show up
- Is another app still connected?
- A BMS usually allows only one Bluetooth connection at a time. Close the manufacturer app completely, not just its window.
- Have the permissions been granted?
- From Android 12 the scan needs "Nearby devices". On Android 11 and earlier the system demands the location permission instead — that is a quirk of Android; MultiVolt evaluates no location.
- Is the battery in range and awake?
- Some modules power down the radio when no current has flowed for a while. Switching on a load for a moment wakes them up.
- Was a model pinned during pairing?
- If a specific protocol is set in a battery’s settings, the app tries only that one. Set it back to "automatic" and it will work through all three again.