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 (38)
Settings (8)
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 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
alarm.mode.status
boolean
Device alarm mode status
anchor.distance
number
meters
Distance to anchor/area center
battery.level
number
percentage
Internal battery level
battery.temperature
number
celsius
Battery temperature
battery.voltage
number
volts
Internal battery voltage
ble.beacons
array
Standard parameter names used: *id* - beacon identification string. Usually it is beacon's UUID or MAC-address *local_name* - Beacons's Local Name *rssi* - BLE signal level. Units = dBm *battery.voltage* - Beacon's battery voltage. Units = volts *battery.level* - Beacon's battery level. Units = percentage *temperature* - Beacon's temperature. Units = celsius
channel.id
number
ID of channel that received a message
device.firmware.version
string
Firmware revision
device.id
number
ID of device that received a message
device.imei
string
IMEI of the device
device.model
string
Device model ID string
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...
gps.module.version
string
GPS module version
gsm.firmware.version
string
Mobile network (GSM, 3G, 4G, LTE, 5G, ...) module firmware version
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.accuracy
number
meters
Position data accuracy in meters
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.timestamp
number
seconds
Timestamp when coordinates where calculated
protocol.id
number
ID of protocol
report.reason
number
Transmission reason code
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
Beacon / Wi-Fi filter
beacon_wifi_filter
Beacon display, BLE/Wi-Fi filtering and TAG reading
wifi_scan: Wi-Fi AP scan
ble_filter: Filter BLE by beacon name
tag_reading: TAG reading
show_beacon_name: Show beacon name on display
BLE scanning
ble_scanning
BLE beacon scanning configuration
ble_scan: BLE beacon scan
preserve_time: Beacon data preserve time (seconds)
sort_and_send: Sort and send mode
beacon_location: Beacon location enabled
low_battery_warning: Low battery warning
GPS configuration
gps_configuration
GPS sleep time, search time, A-GPS, economy mode and position validity
agps_mode: A-GPS mode
sleep_time: Sleep time (seconds)
max_search_time: Max search time (seconds)
validity_period: Position validity period (seconds)
realtime_economy: Realtime economy mode
Motion detection
motion_detection
GPS motion sensor control and sensitivity (cannot be used simultaneously with ManDown)
enabled: Motion sensor
sensitivity: Sensitivity (mG)
On-screen message
on_screen_message
Show a text message on device display
message: Message text
Request location
request_location
Request GPS position from device. Response will be stored as LOC message
action: Action
Server connection
server_connection
GPRS connectivity, APN, server address and port
apn: APN
port: Server port
address: Server address
gprs_usage: GPRS usage
SRD transceiver
srd_transceiver
SRD transceiver sleep and beacon search time
sleep_time: Sleep time (minutes)
search_time: Beacon search time (seconds)
Properties
Custom command
custom
Send custom MPTP command from Central Station to Mobile Telematics Terminal
payload: Command payload
Stop simple tracking process started by TRC or TRS command
{"payload":"?STO"}
Request last known position. Response will be stored as message
{"payload":"?LOC_0"}
Request stored SRD beacon report from device memory. Response will be stored as LOB message
{"payload":"?LOB"}
Request position: Attempt to acquire a fresh position fix. Response will be stored as message
{"payload":"?LOC_1"}
Request device info (SW version, GPS version, IMEI, GSM module). Response will be stored as SIR message
{"payload":"?SIR"}