UMKa301

UMKa301 is an innovative GPS/GLONASS tracking device working over the new wialon-combine protocol and featuring dual-SIM support over GSM 900/1800, GPRS Multi-slot Class 12, voice communication, and IoT connectivity. The terminal features a 3-axis accelerometer, RS-485 and 1-Wire interfaces (+ optional RS-232 and CAN), 4 inputs and 1 output, built-in battery, FOTA, Bluetooth, built-in antennas, optional SD card, optional extension slot, and more.

UMKa301 supports the new wialon_combine protocol.

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

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
ain
number
volts
Voltage on the analog input
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
din
number
Digital inputs bitmask
dout
number
Digital outputs bitmask
driver.message
string
Driver text message content
gsm.cellid
number
Mobile network (GSM, 3G, 4G, LTE, 5G, ...) base station ID
gsm.lac
number
Mobile network (GSM, 3G, 4G, LTE, 5G, ...) location area code
gsm.mcc
number
Mobile network (GSM, 3G, 4G, LTE, 5G, ...) country code
gsm.mnc
number
Mobile network (GSM, 3G, 4G, LTE, 5G, ...) code
gsm.signal.dbm
number
dbm
Strength of the Mobile network (GSM, 3G, 4G, LTE, 5G, ...) signal
gsm.timing.advance
number
Mobile network (GSM, 3G, 4G, LTE, 5G, ...) timing advance
ibutton.code
string
Hexadecimal code of connected iButton
ident
string
Device unique identifier like serial number, IMEI, etc
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.satellites
number
Quantity of satellites used to calculate coordinates for given position information
position.speed
number
km/h
Instant speed at position detection moment
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
wifi.mac.address
string
WiFi MAC address
wifi.signal.strength
number
WiFi signal strength, RSSI
Properties
Custom command
custom
Send custom command to device
hex: Payload is encoded as HEX string
payload: Text or hex data to send
Send string 1234
{"payload":"1234"}
Send string 1234 in hex
{"hex":true,"payload":"31323334"}