Xiamen-lenz protocol

Protocol used by GPS and MDVR devices manufactured by Xiamen Lenz headquartered in China.
flespi parses the Xiamen-lenz protocol messages into a JSON object with the fields listed below in the Parameters tab.

To connect your tracker using the Xiamen Lenz protocol, you need to have a xiamen-lenz channel created first.

Point your tracker to the channel's domain name:port via SMS or configuration tool provided by the vendor.

Then create a device instance for your tracker and use a 15-character IMEI (usually specified on the tracker casing) in the ident field.

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

bus.counter.passengers
number
Bus passengers counter
channel.id
number
ID of channel that received a message
device.id
number
ID of device that received a message
device.ip.address
string
Dynamic Terminal IP address
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
door.open.status
boolean
Door open status
driver.id
string
Driver identification card id
event.code
string
Protocol-specific event code string
event.enum
number
Protocol-specific event code
event.seqnum
number
Unique event sequence number
gsm.signal.dbm
number
dbm
Strength of the Mobile network (GSM, 3G, 4G, LTE, 5G, ...) signal
gsm.sim.imsi
string
IMSI of SIM card of the Mobile network (GSM, 3G, 4G, LTE, 5G, ...)
ident
string
Device unique identifier like serial number, IMEI, etc
passengers.in.count
number
The number of passengers who got in
passengers.out.count
number
The number of passengers who got out
payload.hex
string
HEX Payload received from device
payload.text
string
Text Payload received from device
peer
string
IP:port from which device connecting to the channel
position.altitude
number
meters
Altitude value for position
position.direction
number
degrees
Heading angle at position detection moment
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.valid
boolean
Is position information accurate and valid for given timestamp
previous.passengers.in.count
number
Number of people boarding at the previous stop
previous.passengers.out.count
number
Number of people getting off at the previous stop
previous.site.number
number
Previous site number
protocol.id
number
ID of protocol
route.number
string
Route Number
server.timestamp
number
seconds
Timestamp when server received a message
stations.distance
number
km
Distance between stations
timestamp
number
seconds
Message timestamp
vehicle.mileage
number
km
Total calculated mileage
vehicle.state.bitmask
number
Vehicle state flags bitmask
Properties
Custom command
custom
Send custom command
payload: Optional command payload HEX encoded
command_id: 1 byte command type id
0x0A Query vehicle device version
{"command_id":10}