Fitrider protocol

Protocol used by electric scooters and bicycles manufactured by Fitrider headquartered in China.
flespi parses the Fitrider protocol messages into a JSON object with the fields listed below in the Parameters tab.

This protocol is used to connect and control Fitrider scooters in flespi.

Channel acts as an MQTT Broker to which you directly connect scooters.

To connect your scooter using the Fitrider protocol, you need to have a fitrider channel created first.

Point your scooter to the channel's domain name:port via SMS or configuration tool provided by the vendor. Use the same authorization (username and password) as you configured in the channel configuration.

Then create a device instance for your scooter and use its unique identifier in the ident field.

Use the Toolbox tab on the device screen to check if the messages are coming.

battery.level
number
percentage
Internal battery level
battery.voltage
number
volts
Internal battery voltage
channel.id
number
ID of channel that received a message
device.firmware.version
string
Firmware revision
device.id
number
ID of device that received a message
device.imei
string
IMEI of the device
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
error.type
number
Protocol-specific error identification number
event.enum
number
Protocol-specific event code
fall.alarm
boolean
Fall alarm event
hardware.version
string
Hardware version
ident
string
Device unique identifier like serial number, IMEI, etc
payload.text
string
Text Payload received from device
peer
string
IP:port from which device connecting to the channel
position.latitude
number
degrees
Latitude coordinate value
position.longitude
number
degrees
Longitude coordinate value
position.speed
number
km/h
Instant speed at position detection moment
position.timestamp
number
seconds
Timestamp when coordinates where calculated
power.on.status
boolean
Power-on device status
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
total.trip.duration
number
seconds
Total trips duration
trip.duration
number
seconds
Trip duration
trip.mileage
number
km
Distance driven since engine start
vehicle.mileage
number
km
Total calculated mileage