intermediate
Acton
Acton 2
Acton 3

Acton Scooter BLE Configuration

Configure Acton 2 (FEISHEN_A) and Acton 3 (AKD-Scooter 3.0) scooters to connect to Levy Fleets using the Omni BLE Tool app.

Levy Fleets TeamApril 9, 20265 min read

Acton Scooter BLE Configuration

This guide covers how to configure Acton scooters to connect to the Levy Fleets platform using the Omni BLE Tool app.

Levy Fleets Server Settings

Server IP: •••••sign in Port: •••••sign in APN: simbase

What You'll Need

  • An Android or iOS device
  • The scooter powered on with Bluetooth enabled
  • The Omni BLE Tool app installed

This app is only needed for initial device setup. Once configured, you won't need it again.


Step 1: Download the App

Download the Omni BLE Tool app on your Android device:

Android users: You may need to enable "Install from Unknown Sources" in your Android settings to install the APK.


Step 2: Login to the App

Open the Omni BLE Tool app and log in with these credentials:

FieldValue
Emaildemo@levyelectric.com
PasswordContact Levy support for the current operator credential

Step 3: Select Device Setting

After logging in, choose the setting option that matches your scooter model. Picking the wrong one will write the wrong configuration to the device — the BLE write may appear to succeed, but the scooter will not connect.

Acton ModelSetting OptionTypical Vehicle Number Prefix
Acton 2 (M-Pro and earlier)FEISHEN_A1999200xxx
Acton 3 (newest model)AKD-Scooter 3.019991210xxx, 250xxx

Not sure which model you have?

Check the vehicle number printed on the deck or in the Levy Fleets dashboard. If the leading digits are 19992, it's an Acton 2 — use FEISHEN_A. If they're 199912 or 250, it's an Acton 3 — use AKD-Scooter 3.0.


Step 4: Connect to the Scooter

1

Enable Bluetooth

Ensure Bluetooth is enabled on your phone

2

Power On Scooter

Make sure the scooter is powered on

3

Scan for Devices

In the app, scan for nearby Bluetooth devices. Stay within 10 meters of the scooter.

4

Connect

Tap on your scooter to establish a Bluetooth connection


Step 5: Configure Server IP, Port & APN

After connecting to the scooter:

1

Navigate to Server Settings

Go to the IP/Port configuration menu in the app

2

Enter Settings

Enter the following values:

ParameterValue
IP Address•••••sign in
Port•••••sign in
APNsimbase

APN is required

The APN must be set to simbase (lowercase, no spaces) for the SIM card to register on the cellular network. Leave APN username and password blank.

3

Save Settings

Tap Save or Apply to write the settings to the device

4

Reboot Device

Send a reboot command or power cycle the scooter for changes to take effect

Verify Connection

After rebooting, wait 2-3 minutes then check Levy Fleets Dashboard > IoT Devices to confirm your device appears online.


Troubleshooting

Device not appearing in scan?

  • Ensure you are within 10 meters of the scooter
  • Make sure the scooter has battery power
  • Check that Bluetooth and Location are enabled on your phone
  • Try power cycling the scooter

Device not connecting after configuration?

  • Verify you entered the correct IP: •••••sign in
  • Confirm the port is set to •••••sign in
  • Confirm the APN is set to simbase (lowercase, no spaces, no username/password)
  • Make sure to reboot the IoT after saving settings
  • Check that the SIM card has active data service
  • Wait 2-3 minutes after reboot for the device to connect

Verifying Connection

After configuration:

  1. Wait 2-3 minutes for the device to establish connection
  2. Go to Levy Fleets Dashboard > IoT Devices
  3. Search for your device by IMEI
  4. The device should show as "Online" with recent telemetry data

Server Configuration Reference

Device TypeIP AddressPortAPN
Acton•••••sign in•••••sign insimbase
Feishen (飞神)•••••sign in•••••sign insimbase
Segway / Omni•••••sign in•••••sign insimbase
OKAI•••••sign in•••••sign insimbase
Queclink•••••sign in•••••sign insimbase

Need Help?

Contact support@levyelectric.com with your device IMEI if you encounter issues. See also Omni IoT Integration for protocol details.