Products / TPMS
Putting TPMS data into Wialon, ThingsBoard or Navixy: what actually has to line up
TPMS data can be published to Wialon, ThingsBoard or Navixy over MQTT (TLS, mutual authentication) or HTTP: receiver 500 ms refresh, change-triggered upload with local buffering, 4G CAT.1 with 2G/3G fallback, GPS/BeiDou. Not an official partner claim.
TPMS integration with Wialon
Two paths: raw 8-byte sensor packets forwarded for your decoder, or decoded values in CAN frames at 500 ms.
In transparent mode the packet bytes (pressure 0.1 bar, temperature offset +40, documented CRC) go straight through and Wialon applies its own mapping; in decoded mode the receiver sends fields. Integration status with Wialon is in the process of integrating, not a finished certified connector - we will not claim otherwise.
Typical specification
| Typical specification | Value |
|---|---|
| Transport | MQTT over TLS with mutual authentication, or HTTP to an endpoint you control |
| Receiver refresh | 500 ms; uplink is change-triggered with a heartbeat |
| Offline behaviour | local buffer, history forwarded when the link returns |
| Cellular | 4G CAT.1, fallback to 2G/3G where the network requires it |
| Positioning | GPS / BeiDou dual-mode, optional |
| Payload | documented JSON, one record per upload, field names agreed per project |
| Platform relationship | can publish to Wialon / ThingsBoard / Navixy; no official partnership claim |
FAQ
- Can the data go to Wialon?
- Yes, by publishing to your broker over MQTT or by including the values in a compatible tracker's parameter list. We are not an official Wialon partner and do not claim certification.
- What is the reporting period?
- The receiver refreshes every 500 ms; the uplink should be change-triggered with a heartbeat, so unchanged values are not billed.
- What happens when coverage drops?
- The gateway buffers locally and forwards the history when the link returns.
Q: Does your TPMS work with Wialon or ThingsBoard?
A: The data can be published to a broker you control — MQTT over TLS with mutual authentication — or posted as HTTP, with field names agreed per project. Receiver refresh is 500 ms, the uplink is change-triggered with a heartbeat, and records are buffered locally; we are not an official partner of either platform and do not claim certification.
Platform integration fails on three things, and none of them is the sensor: the field mapping, the reporting period, and who is allowed to change the payload. This page covers all three for Wialon, ThingsBoard and Navixy.
Tell us the application
Send the vehicle, wheel count and where the data must end up. We answer in writing.