Twig Protector Pro

Twig Protector Pro is an emergency GPS tracker that includes an alarm button, automatic man-down function, Amber Alert, and optional TWIG Button wireless alarm. The predefined emergency protocol transmits the last known user position and opens a two-way voice connection to alarms receiving center (ARC). High-performance GPS receiver with turn-key AGPS feed is complemented with TWIG Beacon indoor location. Excellent operating times even in continuous GPS monitoring are achieved through advanced technology and large-capacity battery.



Usage specifics
Parameters (31)
Commands (1)
Twig Protector Pro
Flespi parses telemetry data from your Twig Protector Pro into a standardized JSON and lets you send commands to Twig Protector Pro 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": "Twig Protector Pro",
    "channel.id": 1111,
    "protocol.id": "twig"
    "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 Twig Protector Pro?

You can send a specific command. Show all commands

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
alarm.mode.status
boolean
Device alarm mode status
battery.level
number
percentage
Internal battery level
battery.temperature
number
celsius
Battery temperature
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
error.type
number
Protocol-specific error identification number
event.code
string
Protocol-specific event code string
event.enum
number
Protocol-specific event code
event.seqnum
number
Unique event sequence number
gnss.type
string
GNSS type: gps, glonass, etc...
ident
string
Device unique identifier like serial number, IMEI, etc
message.content
string
Message content
message.detail
string
Message detail
message.type
string
Message type
normal.mode.status
boolean
Normal mode status
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.hdop
number
Horizontal dilution of precision
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
protocol.id
number
ID of protocol
report.reason
number
Transmission reason code
send.timestamp
number
seconds
Message send timestamp
server.timestamp
number
seconds
Timestamp when server received a message
test.mode.status
boolean
Device is in test(diagnostic) mode
timestamp
number
seconds
Message timestamp
Properties
Custom MPTP command
custom
Send custom MPTP command from Central Station to Mobile Telematics Terminal
payload: Payload text
Request last known position. Response will be stored as message
{"payload":"?LOC_0"}
Request position: Attempt to acquire a fresh position fix. Response will be stored as message
{"payload":"?LOC_1"}