Troubleshooting

If the scooter doesn't react

If the scooter isn't responding to the keycard or to any other input, work through the following steps:

1. Try the brake-lever gesture: hold both brake levers at the same time, for about six seconds. If the scooter was in hibernation, this wakes it up. On success, the LED next to the display lights up briefly and the keycard works normally afterward.
2. Check the battery: open the seat and confirm that a charged battery is in the front slot. The button on the battery's handle shows the charge level on the LED ring.

If the scooter still doesn't react after this, it's almost always a hardware problem. A common case is a deeply discharged AUX battery: in that state the seatbox sensor can't be read and the main battery can't be activated, even when it's full. Issues like this can't be fixed in software. Get a diagnosis on the Discord or take the scooter to a workshop with unu experience.

Battery error codes (B-series)

When a main battery reports a problem, the display shows a code from the B-series. The exact codes come from inside the battery itself and match the ones used by the original unu firmware.

The codes break down into rough categories:

• Temperature protection (battery too hot or too cold to charge or discharge): let the battery come back to a normal temperature. On hot days, let it cool off in the shade; in the cold, bring it indoors. If the error keeps appearing after recovery, have a workshop check the battery.
• Voltage or current protection (over- or undervoltage, overcurrent on charge or discharge, short-circuit protection): charge the battery fully and try again. If the message persists, the battery needs a workshop.
• Communication or NFC errors: take the battery completely out of the scooter, wait a minute, and put it back. If that doesn't help, ask on the Discord or contact a workshop.
• Battery damage: get a replacement battery via the community. Don't keep using a damaged battery.

Motor and electronics errors (E-series)

E-series codes come from the motor controller (ECU) or other electronics on the scooter. These are also unchanged from the original firmware.

Rough categories:

• Battery-voltage problems as seen by the motor controller: usually fixed by charging and trying again. If the error persists, a workshop inspection is in order.
• Motor or sensor errors: often not fixable without a workshop. Park the scooter safely and describe the problem on Discord or to a partner workshop.
• Throttle problems: release the throttle completely, wait briefly, then apply throttle again. If the error keeps coming back, the throttle or its wiring may be defective.
• Overheating: stop the scooter and let the ECU or motor cool down. Repeated overheating without an obvious cause (normal temperatures, no sustained load) calls for a workshop visit.

Toasts and warning icons

Some problems show up as a colored toast at the top of the display rather than an error code. The colors are described on The display (currently only in German). Common cases:

• Seat open: an icon at the top of the status bar. Close the seat and the indicator clears.
• AUX battery weak or critical: a toast and a status-bar icon. Often appears when the scooter has been sitting without an active main battery for a long time. Insert a charged main battery and wait a while.
• USB connection interrupted: persistent red toast plus the motor warning icon. The link between MDB and DBC is broken. A full power-cycle (put the scooter into hibernation and wake it again) usually clears it.

If an update fails

The full procedure is on Updates. Short version: a failed automatic update leaves the old version active, and the scooter retries on the next check. A failed USB update can simply be retried from the start.

When nothing helps

Librescoot is a community project, not a commercial support contract. There are two main places to get help:

• The Discord server with channels for scooter support, hardware, and reverse engineering. Describe the problem as concretely as possible – ideally with a photo or version info from the version box.
• The issue tracker on GitHub for reproducible bugs and concrete improvement suggestions.

For hardware defects beyond the software side, you'll still need a workshop with unu experience.