Sparkplug Primary Host STATE: Reject Old Offline Messages Before Broker Failover
How should a Sparkplug edge node decide whether an offline Primary Host STATE message belongs to the current host session before leaving a still-reachable MQTT broker?
Serial and industrial data integration, gateway protocols and application-level buffering. Evaluate data ordering, duplicates and recovery independently of whether a network connection has been restored.
How should a Sparkplug edge node decide whether an offline Primary Host STATE message belongs to the current host session before leaving a still-reachable MQTT broker?
Why can two distinct 64-bit counter values become identical after MQTT In, and where should the Node-RED flow preserve their exact representation?
Compare the actual optimized Modbus read span with the device map before changing OPC UA subscription settings.
Review PLC attribute inheritance, actual symbol artifact and filtered-import capability before accepting the exported OPC UA interface.
Retain the selected event-state identity from an operator dialog through acknowledgement or confirmation.
Reconcile retained SCADA alarm state using refresh start/end boundaries, preserving branch identity and live updates.
Inventory polling documents and separate views, aggregate counters and excluded custom-message paths.
Assess whether Sparkplug supplies the namespace, metric and state contract required between an industrial MQTT gateway and host.
Review industrial gateway interfaces, management paths and enforceable boundaries instead of treating a read-only collector as network isolation.
Plan SiteWise historian backfill around timestamp eligibility, bulk-import prerequisites, derived-output limits and overlapping live data.