Tacho Bridge App
Make your Tacho Bridge App devices a part of any infrastructure by connecting them via flespi telematics hub. Manage the
device settings using flespi device
management platform. Learn how
to configure Tacho Bridge App with flespi.
Usage specifics
Parameters (11)
Settings (4)
Commands (1)
Tacho Bridge App
Flespi parses telemetry data from your Tacho Bridge App into a standardized JSON and
lets you send commands to Tacho Bridge App 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": "Tacho Bridge App",
"channel.id": 1111,
"protocol.id": "tacho-bridge"
"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'
How to send commands to Tacho Bridge App?
You can send a specific command.
Show all commands
You can use pre-defined settings to send instructions more conveniently.
Show all settings
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 channel.id
number
ID of channel that received a message
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
ident
string
Device unique identifier like serial number, IMEI, etc
media
boolean
Message contain media file
media.video
object
Video file in media storage
peer
string
IP:port from which device connecting to the channel
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
Properties
Server address
server
Address of the MQTT server the application connects to with every connection it opens (the application itself and its cards),
reported by the application on connection. Changing it moves the application to another server: the result comes back on the
current connection, then the application reconnects everything to the new address.
host: Host
Extended debug log
debug_log
Extended application debug log: raises the verbosity of the application log for a window of time, so the next
'Fetch application logs' command carries the details the server-side traffic dump does not have. The log stays on
the application side. The state is also reported by the application on every connection.
window: Enable extended debug log
Authentication
authentication
MQTT credentials the application presents on every connection it opens (the application itself and its cards).
The server checks them against the 'credentials' username and password of the channel configuration, so set them there first:
without explicit values the setting pushes the channel pair.
credentials: Enable authentication
Application Information
app_info
Tacho Bridge App instance information, reported by the application on connection. Read-only.
os: Operating system
arch: CPU architecture
version: Application version
os_release: Operating system release
Properties
Fetch application logs
fetch_logs
Fetch the application log file for the given period; the zipped log is attached to the command result
period: Log period
More devices from N/A (3)
Tags
