Usage specifics
Parameters (20)
ScoutOpen
Flespi parses telemetry data from your ScoutOpen into a standardized JSON and
lets you send commands to ScoutOpen via API.
Here’s the like of JSON you get
{
"ident": "352625333222111",
"position.altitude": 273.61,
"position.hdop": 0.7,
"position.latitude": 49.069782,
"position.longitude": 28.632826,
"position.satellites": 18,
"server.timestamp": 1650636570.426424,
"timestamp": 1650636570.426424,
"device.type.id": "ScoutOpen",
"channel.id": 1111,
"protocol.id": "scout-open"
"engine.ignition.status": true
...
}
How to consume this nice JSON
The easiest way is to make a REST API request like this
curl -X GET --header 'Authorization: FlespiToken XXX' 'https://flespi.io/gw/devices/<device id>/messages'
You can also
Modify messages
Add or remove parameters, inject data from LBS and reverse-geocoding services, etc.
Learn what plugins can do
Aggregate data
Determine trips and stops, catch events, detect geofence ins/outs, and more.
Learn about flespi analytics capabilities ain
number
volts
Voltage on the analog input
channel.id
number
ID of channel that received a message
counter.impulses
number
Impulses counter
device.id
number
ID of device that received a message
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
din
number
Digital inputs bitmask
external.powersource.status
boolean
External power source connection status
ident
string
Device unique identifier like serial number, IMEI, etc
peer
string
IP:port from which device connecting to the channel
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.satellites
number
Quantity of satellites used to calculate coordinates for given position information
position.speed
number
km/h
Instant speed at position detection moment
position.valid
boolean
Is position information accurate and valid for given timestamp
protocol.id
number
ID of protocol
sensor.frequency
number
hz
Frequency sensor value
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp