Skip to content

Collect machine and sensor messages with MQTT

Qynetic Edge subscribes to MQTT 3.1.1 topics at QoS 1. It can map JSON fields to measurements or counters and plain-text messages to state changes.

Agree on the message with the publisher

A gateway, sensor or existing integration publishes messages to a broker. Edge subscribes with its own client ID. Obtain a real example message and identify the topic, machine ID, field names and units. A topic can establish which press sent a message while separate fields describe its temperature and part count.

For JSON measurements and counters, the publisher must include a source timestamp and a stable message ID that remains unique after a restart. A plain-text message can express a change, such as a transition from RUNNING to IDLE. The adapter expects ordinary JSON or text payloads. Sparkplug B uses a different payload format.

What QoS 1 means for a production count

Both publisher and broker must support delivery at QoS 1. The broker can resend a message if an acknowledgement is lost. Edge uses a persistent session and acknowledges the message after local processing has been committed. Stable source IDs allow it to recognise repeated deliveries.

During commissioning, check whether the broker retains outstanding messages across a restart. Confirm the measurement and count locally, then follow the same event through to the registered machine in Qynetic.

Book a call about your factory

Tell us what you make and which machines you run, and we will walk through how Qynetic fits. If you would rather get news and early access, join the waitlist.