Teltonika-gateway-wifi-mqtt protocol

Protocol used by Gateway Wi-Fi Wirepass devices manufactured by Teltonika headquartered in Lithuania.
flespi parses the Teltonika-gateway-wifi-mqtt protocol messages into a JSON object with the fields listed below in the Parameters tab.

This MQTT-based protocol with JSON payload is used by Teltonika Gateway Wi-Fi devices to effectively parse the data about anchors and assets in Wirepas Mesh network.

To connect your Gateway Wi-Fi, you need to create teltonika-gateway-wifi-mqtt channel, and use its URI and port in the device's Config->MQTT set up and select JSON as Data encoding.

There are 3 device types available for the protocol:

Wi-Fi Gateway device type is identified by the serial number (e.g. BTGW-00000000deadbeef) and stores one valuable parameter event.payload: it is the copy of JSON object with all the data received as MQTT payload. It is used for debug purposes.

Asset device type is the virtual representation of the moving asset, it is identified by the 10 digit serial number (e.g. 1234567890) and stores the valuable array parameter "anchors" that looks like [{"id":"1234567","rssi":-104},{"id":"7654321","rssi":-73}] that displays the list of anchors seen by the asset and the signal strength to it. Asset data is transmitted to the gateway over the anchor's mesh network, thus the asset also has parameters the signal.hop.count (number of the nodes in the Mesh network used to transfer the signal to the gateway) and signal.travel.time, together with the standard parameters like message.seqnum and battery.voltage.

Anchor device type is used to track the anchor devices to effectively answer the question "which assets were seen by the specific anchor device". It is identified by the 7-digit identifier (e.g. 1234567) and it stores the array parameter "assets" that looks like [{"id":"1234567890","rssi":-104}]


anchors
array
Array of visible anchors with RSSI
assets
array
Array of visible assets with RSSI
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
event.payload
object
Raw Wirepas packet_received_event object from gateway
firmware.version
string
Firmware version
ident
string
Device unique identifier like serial number, IMEI, etc
message.seqnum
number
Sequence number of the message
peer
string
IP:port from which device connecting to the channel
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
signal.hop.count
number
Number of mesh network hops traversed
signal.travel.time
number
Message transit duration in seconds
timestamp
number
seconds
Message timestamp
Properties
Custom command
custom
Send custom command to device