dct-syrus

The protocol for Syrus GPS tracking devices.

Below is the list of parameters that can appear in the messages received by the channel via dct-syrus 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
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
event.seqnum number Unique event sequence number
ident string Device unique identificator and optional password
peer string IP:port from which device connecting to the channel
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
protocol.id number ID of protocol
server.timestamp number seconds Timestamp when server received a message
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 flespi.io account.

Title Name Description Properties
Custom command custom Send custom command to device payload: Command text