flespi telematics hub supports erm protocol. The list of supported devices is: StarLink Tracker StarLink Tracker3G StarLink TrackerGNSS StarLink AVL

We've added custom command to the erm protocol It allows you to send any command to StarLink devices connected to flespi. For example, To send command 23 - Request immobilizer rule #2 - use the following REST API request: curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: FlespiToken XXXX' -d '[{"address":{"ident":"123456789012345","type":"connection"},"name":"custom","properties":{"command":23,"payload":"2"},"ttl":86400}]' 'https://flespi.io/gw/channels/<channel_id>/commands-queue' just replace: XXXX - with your flespi token 123456789012345 - device ident <channel_id> - ID of flespi erm channel For more details read: How to send a command to the device over the channel’s connection?

We enhanced support of 02 - Error report messages for StarLink devices (up to Version 2.32, March, 2019). Descriptions for all 24 error types available at the moment are stored in error.type.description parameter.

02 - Error report : parsing of additional information added for Error number 20: Cellular signal degradation

Parameter renaming in erm protocol: vehicle.battery.health parameter is renamed into battery.health . Both parameters will be registered during one week. 17-Apr-2020 old parameter vehicle.battery.health will be removed.

Erm protocol is updated - new dynamic parameters are added: JAM (Jamming detection state) - parameter gsm.jamming.alarm.status LOCA (Location accuracy, meters) - parameter location.accuracy LOCS (Location source) - parameter location.source LOCF (Location filter reason) - parameter location.filter.reason NC (Network code) - parameters gsm.mcc and gsm.mnc

namo Erm protocol updated: old parameter vehicle.battery.health is removed after renaming

Announcement: Command get_location will be deleted from ERM protocol in a week, 25-Jun-2020. Please, use custom command instead, see examples here

Next Monday, 03-May-2021, message parameter "gsm.signal.level" parsed from the #CSS# dynamic tag will be renamed to "gsm.signal.dbm". Currently, we're registering the same value for both parameters, and in a week the old name "gsm.signal.level" will be removed.

We've added the read-only setting "Dynamic parameters" to all StarLink devices. That setting is used to preserve dynamic parameters format (parameter 177) between device connections, to correctly parse dynamic events. If you will change that parameter through the device configurator - please remove that setting in the flespi device Settings to trigger its re-reading. If you will not create a device (i.e. you're working on the channel-level only) - the command to read dynamic parameters format (parameter 177) will be sent to the device at the beginning of every connection.

[Changelog] erm protocol

kial

kial parameter "gsm.signal.level" renamed to "gsm.signal.dbm"

baja

Extra field for Event number 18 is stored as report.reason parameter

kial

Next Thursday, 23-Dec-2021, message parameter "location.accuracy" parsed from the #LOCA# dynamic tag will be renamed to "position.accuracy".
Currently, we're registering the same value for both parameters, and in a week the old name "location.accuracy" will be removed.

kial

kial Old parameter name removed

baja

The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

YuryAheichyk

ERM protocol has been changed. gsm. network.type parameter parsed from the #NT# dynamic tag was added.

YuryAheichyk

ERM protocol has been updated, added TrackerWi-Fi device

baja

parameter renaming announcement which will happen in a week (May 22):
parameter total.idle.seconds will be renamed to total.idle.time

YuryAheichyk

Added #FIX# and #CU# parameters parsing (flespi parameters: position.fix.type, transmition.channel)

baja

Fixed type 02 confirmation messages being incorrectly stored as empty telemetry messages

Added server ACK response for type 06 event messages, enabling bulk message delivery for devices configured to require acknowledgment

bird

New parameter gnss.jamming.status for EID=90 (GNSS Jamming detected) and EID=91 (GNSS Jamming ended) events
New parameter econnect.peer (object) for EID=3 (eConnect) events — contains peer device data: engine.ignition.status, speed.scale, position.direction, position.latitude, position.longitude, rssi, state, position.age, ident.type, ident
New parameter external.device.value for EDV1-4 and EDX1-4 dynamic fields

bird

Custom Events #1-#16 (EID 48-55, 60-67) are now supported — devices will no longer disconnect on custom event reports
New parameter immobilizer.override.mode for EID=77 (Override mode) events
New parameter external.device.firmware.version for EID=73 (Device added) and EID=74 (Device removed) events
EID=68 (Passenger ID) and EID=93 (Forced disarm) immobilizer events are now supported with immobilizer.state, immobilizer.rule, immobilizer.data parameters

bird

Fixed parsing of engine.ignition.status parameter — was incorrectly set to true for events without explicit ignition extra fields (events 14, 15, 18, 33, 44, 45, 48, 49, 50, 90, 91, etc.). Now correctly reflects actual engine state.

bird

New parameter engine.status added — engine running state from #ENG# dynamic field and Events 24/25 (Engine On/Off). Previously, #ENG# incorrectly wrote to engine.ignition.status, overwriting the correct ignition value from #IGN#. Now #ENG# and #IGN# produce independent parameters: engine.ignition.status for ignition state, engine.status for engine running state.