Wirepas Gateway Protobuf MQTT Protocol. Wirepas protocol connects Wirepas mesh network gateways to flespi over MQTT using the standard protobuf-encoded gateway-to-backend API published by Wirepas. Any vendor's gateway implementing this API can stream mesh data to flespi without vendor lock-in. flespi decodes received packet events and Wirepas positioning application payloads, registering separate messages mesh assets (tags) and anchors with RSSI measurement arrays for indoor positioning, battery voltage, and mesh diagnostics such as hop count and travel time.
Messages are registered per mesh node, not per gateway: each node's message uses its Wirepas network address as the ident and carries the relaying gateway's identifier in the gateway.id parameter, while every anchor that saw the node additionally receives its own message with the observed asset and RSSI in the assets array. Nodes are automatically classified as assets (tags) or anchors by the type of RSSI measurement they report, and message timestamps come from the event generation time reported by the gateway.
anchors
array
Array of visible mesh anchors with RSSI
assets
array
Array of visible mesh 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.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
firmware.version
string
Firmware version
gateway.id
string
Identifier of the gateway that relayed the message from the device
ident
string
Device unique identifier like serial number, IMEI, etc
message.seqnum
number
Sequence number of the message
movement.status
boolean
Current movement state
peer
string
IP:port from which device connecting to the channel
protocol.id
number
ID of protocol
report.interval.time
number
Report interval time
server.timestamp
number
seconds
Timestamp when server received a message
signal.hop.count
number
Number of mesh network hops traversed by the message
signal.travel.time
number
seconds
Message transit duration through the mesh network
timestamp
number
seconds
Message timestamp
