Twig One

TWIG One is a rugged wearable lone worker alarm for industrial environments. It features 2G/3G/4G and Wi‑Fi communication, loud hands-free speakerphone, configurable SOS and Mandown alerts, Amber alerts, and automatic man-down detection for falls, tilt, impact, and no movement. The device provides accurate indoor and outdoor positioning via multi-constellation GNSS, Wi‑Fi, SRD and BLE beacons, plus geofencing. It is IP67 water and dust proof, offers NFC-based attendance monitoring, remote configuration, FOTA updates, and integration with TWIG Point cloud and alarm receiving centre systems.

Usage specifics
Parameters (32)
Commands (1)
Twig One
Flespi parses telemetry data from your Twig One into a standardized JSON and lets you send commands to Twig One 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 One",
    "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 One?

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
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
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.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
Custom command
custom
Send custom MPTP command from Central Station to Mobile Telematics Terminal
payload: Command payload
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"}