Generic
MQTT Device
What You Need
Customer provides:
- MQTT device
- WiFi or Ethernet access
- Device documentation for topic/payload configuration
Physical Connection
- 1
Connect device to network
Connect the MQTT device to the plant network via WiFi or Ethernet. Ensure it can reach the MQTT broker (Flowstate hub or HiveMQ Cloud).
- 2
Configure broker connection
On the device, set the MQTT broker address to the Flowstate hub IP (10.0.100.10:1883 for local, or HiveMQ Cloud endpoint for cloud). Set client ID to a unique value.
- 3
Set TLS (if cloud broker)
For HiveMQ Cloud, enable TLS 1.2+ on the device. Port 8883. Provide username/password credentials.
Machine Configuration
- 1
Configure publish topic
Set the device to publish on a topic following the UNS pattern: spBv1.0/{GROUP_ID}/DDATA/{EDGE_NODE}/{DEVICE_ID} for Sparkplug B, or a custom JSON topic.
- 2
Set payload format
Sparkplug B (preferred): device publishes protobuf-encoded payloads. JSON (fallback): publish JSON objects with key-value metric pairs. The Flowstate hub auto-detects format.
- 3
Configure QoS and retain
Set QoS 1 (at-least-once) for telemetry data. Retain = false for live data, retain = true for status messages.
Verification
- 1
Check broker connection
On the Flowstate hub, run mosquitto_sub on the device's topic. Verify messages arrive at the expected interval.
- 2
Dashboard check
Device appears in Flowstate. If using Sparkplug B, auto-discovery creates the asset automatically on DBIRTH.
Available Metrics (4)
Don't have MQTT access?
The universal CT clamp works on any machine — 15 minutes, zero configuration.
CT Clamp Fallback GuideReady to Connect?
Calculate what downtime is costing you, then get started.