Neomatica protocol
Integration level: params + settings
Protocol used by GPS tracking devices manufactured by Neomatica headquartered in the Russian Federation.
flespi parses the Neomatica protocol messages into a JSON object with the
fields listed below in the Parameters tab.
absolute.acceleration
number
g
Module of accelerometer vector
ain
number
volts
Voltage on the analog input
alarm.event
boolean
Alarm event triggered
alarm.mode.status
boolean
Device alarm mode status
battery.low.alarm
boolean
Battery low alarm event
battery.voltage
number
volts
Internal battery voltage
can.tag.number
number
User defined can tag number
can.tag.value
number
Can tag value, merge by parameter index
case.status
boolean
Case opened status
channel.id
number
ID of channel that received a message
counter.impulses
number
Impulses counter
device.id
number
ID of device that received a message
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
din
number
Digital inputs bitmask
dout
number
Digital outputs bitmask
event.enum
number
Event code, full list of codes available at separate table
external.powersource.status
boolean
External power source connection status
external.powersource.voltage
number
volts
External power voltage
fuel.level
number
percentage
Fuel level percentage
glonass.position.satellites
number
Quantity of satellites from GLONASS used to calculate coordinates for given position information
gnss.vehicle.mileage
number
km
Vehicle mileage calculated by global navigation system (GNSS)
gps.position.satellites
number
Quantity of satellites from GPS used to calculate coordinates for given position information
gsm.sim.status
boolean
SIM card is active
ident
string
Device unique identifier like serial number, IMEI, etc
movement.status
boolean
Current movement state
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
position.valid
boolean
Is position information accurate and valid for given timestamp
protocol.id
number
ID of protocol
sensor.temperature
number
celsius
Temperature sensor value
server.timestamp
number
seconds
Timestamp when server received a message
software.version
string
Software version string
timestamp
number
seconds
Message timestamp
Properties
Custom command
Examples
custom
Send custom command to device
parameters: Optional parameters
command_name: Command name
Tags
To connect your tracker using the Neomatica protocol, you need to have a neomatica channel created first.
Point your tracker to the channel's domain name:port via SMS or configuration tool provided by the vendor.
Then create a device instance for your tracker and use a 15-character IMEI (usually specified on the tracker casing) in the ident field.
Use the Toolbox tab on the device screen to check if the messages are coming.
It is possible to configure Neomatica devices OTA using the flespi web-based configurator tool. To connect Neomatica to Wialon or another platform via flespi please read this article.