The protocol for Neomatica GPS tracking devices.

Below is the list of parameters that can appear in the messages received by the channel via neomatica protocol. In most parameters, the name consists of tags split by dots: tag1.tag2.tag3.tag4... Each tag defines a certain area of an application, e.g. any parameter that contains mileage data has the 'mileage' tag in the name and any parameter related to fuel control contains the 'fuel' tag. By default JSON fields of the message received by a channel via this protocol can only contain the below-specified parameters. Any additional parameter will be prefixed by the "custom" tag, e.g. "custom.unspecified-name".

Name Type Unit Description
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 number ID of channel that received a message
counter.impulses number Impulses counter number ID of device that received a message
device.model string Device model ID string string Name of device that received a message 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 identificator and optional password
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 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

Below is the list of commands that can be sent to devices to change their configuration or to send signals to various outputs. When sending a command you can specify the transport type defining how the command will be delivered - the address parameter can take values connection (via network connection once the device goes online), sms (via SMS message), push (via PUSH notification). A comprehensive format of each command with all possible parameter values, parameter types, default values, etc. can be found in the REST API documentation in your account.

Title Name Description Properties
Custom command custom Send custom command to device parameters: Optional parameters

command_name: Command name
Reboot the device
Set period of tracking to 30 seconds in motion and 300 seconds without motion
Compose report message from the main data only. Do not include additional data