BMS Dash 1.2.1

Fix: the password prompt for protected packs never appeared

1.2.0 shipped support for password-protected Bluetooth modules, but with a
circular flaw: the unlock handshake only ran when a password was already
saved, and the password prompt was only triggered by a handshake failure.
So on first contact with a locked pack nothing probed it, nothing prompted,
and the pack looked dead — "Waiting for battery data...", then a disconnect
back to the connect screen. Thanks to the tester who reported exactly that.

The app now sends the harmless app-key probe on every connect, the same
frame the vendor app always sends. If the pack answers "password required",
you get the password dialog; packs that don't speak the auth protocol at
all (the normal, unprotected kind) simply don't answer and connect as
before, after a short 2-second probe.

Still to verify on real hardware

If your pack now prompts, accepts the password, but shows no readings,
please open an issue — that symptom points at one specific known-missing
step (the vendor's root handshake), which was left out on purpose because
it is factory-level access.

Safety

Unchanged: the unlock frames talk to the Bluetooth module, not the BMS
controller. They write no register, no EEPROM and no factory mode, so the
app still only ever writes register 0xE1 (volatile MOSFET on/off).

Install

Download bms-dash-1.2.1.apk below. You may need to allow installing from
unknown sources.