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. A toast with the code and its meaning appears when the fault first shows up; red toasts mark critical faults, orange ones non-critical. The full list:

What to do, by group:

• Temperature protection (B1–B4, B6, B8): 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.
• Cell under-voltage (B11): charge the battery fully and try again. If the message persists, the battery needs a workshop.
• Any other voltage, current, or wiring fault (B5, B9, B12–B14): don't keep using or charging the battery as a test – with a short circuit in particular, stop immediately. Get the battery assessed by a workshop or via the Discord.
• Communication or NFC errors (B32–B35): 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.

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. A toast with the code appears when the fault shows up; all E-series faults are critical (red toast) except E14.

What to do, by group:

• Battery-voltage problems (E1, E2): usually fixed by charging and trying again. If the error persists, a workshop inspection is in order.
• Motor or sensor errors (E3–E7, E10, E16, E20): often not fixable without a workshop. Park the scooter safely and describe the problem on Discord or to a partner workshop.
• Throttle problems (E12, E14): release the throttle completely, wait briefly, then apply throttle again. E14 simply means the throttle was held while the scooter powered up and clears by itself. If E12 keeps coming back, the throttle or its wiring may be defective.
• Overheating (E11, E13): 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

Not every problem shows up as an error code. Two channels report problems while the scooter is running: the telltale card at the bottom left of the display and colored toasts at the top. Toast colors are described on The display.

Telltale card

The card shows up only when at least one icon is active:

• Motor warning (yellow): an error in the motor or motor controller, or an interrupted connection between the scooter's computers (see the red USB toast below).
• Hazard triangle (red, blinking): the hazard lights are on.
• Parking brake (P) (red): the scooter is in park mode.
• Turtle (orange): an installed, active battery is at 20% charge or below; motor power is capped until it is charged again.

Toast messages

These messages can appear over the normal display:

Apart from toasts, the status bar shows a seat icon while the seat is open; it clears when you close it.

Fault history

The fault history has been part of Librescoot since the first release. 1.3+ Under Librescoot 1.3 and newer you find it under Menu → Info → Faults; in older versions it sits directly in the root menu.

It shows both active faults and cleared history. Each entry identifies the reporting source and fault code, along with timestamps and the number of times it was recorded. When any fault is active, Faults also appears directly in the root menu.

This record is useful when asking the community or a workshop for help. Note the source, code, and timing rather than guessing at a remedy for a newly logged internal fault.

Clearing Bluetooth connections

1.3+ If a device won't pair any more, or you're handing the scooter on and don't want to leave your devices paired to it, use Menu → Settings → System → Clear Bluetooth Connections…. This clears all BLE pairings stored by the scooter. The entry is only offered while the scooter is parked, and the action is all or nothing. Pair your devices again afterwards; for a phone, the display shows the PIN to enter.

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.

Emergency start (display unavailable)

If the display is unavailable or stuck on the "Trying to connect to vehicle system..." screen, the scooter can still be put into drive mode: fold in the side stand, hold both brake levers, and press the seatbox button at the same time.

Be careful: this bypasses the display entirely. The scooter can move immediately, and you'll have no speedometer, no warning icons, and no error messages. Use this only to move the scooter a short distance on safe, level ground – for example onto a charger or out of the way – never for a normal ride. Fix the underlying problem first (see the sections above); the scooter powers down normally afterwards.

When nothing helps

Librescoot is a community project, run by volunteers. There are two main places to get help:

• The Discord server has a support forum plus channels around Librescoot itself – including release announcements and development – and channels for hardware questions. Describe the problem as concretely as possible – ideally with a photo and the 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.