MQTT TPMS data — published to your platform, not into our box

How the path looks

sensors → receiver → CAN → 4G gateway → MQTT broker → your platform.

The receiver side is described on the CAN integration page. The gateway side is what this page is about.

What the gateway does

Item	Value
Transport	MQTT over TLS (mutual authentication), or HTTP posting to an endpoint you control
Uplink	Change-triggered — unchanged values are not sent, so you are not paying for a constant stream
Buffering	local buffer while coverage drops; history is forwarded when the link returns
Connectivity	4G CAT.1, with fallback to 2G/3G where a network requires it
Field update	A/B dual-partition FOTA with resume and automatic rollback
Positioning	GPS / BeiDou dual-mode, optional
Protocol ownership	Your CAN protocol stays with you — we deliver an agreed payload, not a request for your protocol document

Works with the broker you already run

Because the transport is standard MQTT, the broker can be a hosted service your team already uses — including flespi, AWS IoT, or a broker you run yourself. That matters when your platform is the place where decisions are made, and you would rather not have a second dashboard.

What we need from you

• Broker host, port and topic convention (upstream and downstream), and the credential model you use.
• Which values you actually want, and how often you need them.
• Whether you also need to send commands back to the unit (the gateway relays; the behaviour stays in your controller).

What this is not

It is not an OBD replacement and it does not require you to hand over your CAN protocol. We publish the values you asked for; your definitions stay yours.

Send us the application

Leave this field empty

Name *

Company *

Business email *

Country

What you need *

Send