
Why telemetry can differ between official and custom firmware
Firmware determines what the controller reports and how some values are scaled or filtered. A dashboard difference after a change may reflect the protocol, not a new physical condition.
Scooter Tools can show supported local Bluetooth telemetry and trip context. It does not flash firmware, bypass ownership, certify a repair or replace the scooter manufacturer’s safety instructions.
Record a before state
Save exact firmware versions and normal resting readings before any approved change. Without a baseline, it is difficult to distinguish protocol and vehicle effects.
Compare stable conditions
Use the same scooter state, charge level, temperature and application version. Do not compare one reading under acceleration with another at rest.
Expect field availability to change
A firmware may add, remove or reinterpret fields. Scooter Tools shows what the selected supported protocol exposes; it should not invent unavailable values.
Keep modification responsibility separate
Use official support for official firmware and the firmware project’s own documentation for custom configuration. Scooter Tools does not flash or tune either path.
Safe review checklist
- Record exact versions.
- Match the physical conditions.
- Compare raw availability before derived metrics.
- Report reproducible field differences.
Frequently asked questions
Does a changed value prove sensor damage?
No. Scaling, filtering or field mapping may have changed.
Can Scooter Tools restore old firmware?
No.
Should I share raw authentication data with a bug report?
No. Redact keys, tokens, addresses and serials.





