LE Sparkplug Edge Node

introduction the le sparkplug edge node is a software application designed to run on litmus edge it enables the litmus edge instance to act as a compliant sparkplug edge of network (eon) node, bridging data between connected industrial devices and sparkplug aware host applications (like scada or iiot platforms) what is the sparkplug specification? the sparkplug specification https //sparkplug eclipse org/specification/ is an open source messaging protocol built upon mqtt, specifically tailored for industrial iot (iiot) systems its primary goals are efficient data exchange provides standardized topic namespaces and payload formats (using protocol buffers) for optimized data transmission real time communication leverages mqtt's publish/subscribe model for timely data updates state management defines clear mechanisms for devices (edge nodes) to report their status (online/offline) and data, ensuring host applications always know the state of the network standardized data modeling offers a structured way to represent device data and metrics auto discovery allows edge nodes and their connected devices/metrics to be automatically discovered by host applications secure communication inherits mqtt's security features (like tls) for encrypted data transport by standardizing these aspects, sparkplug simplifies the integration and interoperability of diverse devices and applications within an iiot environment how the le sparkplug edge node works the le sparkplug edge node application integrates seamlessly with litmus edge's underlying services connects to litmus edge it utilizes the litmus edge api to access configured devices, tags, and data streams transforms data it automatically transforms the data from litmus edge tags into the standardized sparkplug payload format manages state it handles sparkplug birth, death, and data messages according to the specification, ensuring proper state representation to the mqtt broker and connected host applications communicates via mqtt it connects to one or more configured mqtt brokers, publishing sparkplug messages under the defined topic structure ( spbv1 0/\<group id>/\<message type>/\<node id>/\[device id] ) this allows upstream applications that understand the sparkplug specification to easily consume data from devices connected to litmus edge, discover new devices and metrics automatically, and monitor the online/offline status of the edge node key features sparkplug b compliant implements the sparkplug b specification for edge of network (eon) nodes litmus edge integration automatically discovers and utilizes tags configured within litmus edge mqtt connectivity connects securely to mqtt brokers (versions 3 1 0 and 3 1 1 supported) with tls options store and forward optional capability to buffer data locally if the mqtt connection is temporarily lost (requires configuration) primary host support can optionally wait for a designated primary host application to be online before publishing data dockerized deployment runs as a containerized application within litmus edge next steps to deploy and configure the application, please refer to the deploying the solution docid\ derq8vikrcedo8sfwcpqs guide