Troubleshooting Sparkplug Edge Nodes
Sparkplug is a trademark of Eclipse Foundation, Inc. "MQTT" is a trademark of the OASIS Open standards consortium. Other related terms are trademarks of their respective owners. Any use of these terms on this site is for descriptive purposes only and does not imply any sponsorship, endorsement or affiliation.
Introduction
This article discusses issues specific to troubleshooting Sparkplug edge nodes. For information that is common to any troubleshooting in Sparkplug, see Sparkplug Troubleshooting.
Common issues
Primary host application not online
If your edge node connects to the MQTT broker, but it somehow "refuses" to publish any data, check whether the edge node is configured to use a primary host application (has non-empty primary host application ID). If so, the edge node will - correctly - not publish any data until it can positively verify that the configured primary host application is online.
In this case, you need to
- check whether the configured ID of the primary host application in the edge node matches the ID that the host application actually uses,
- check that the host application is running, and
- check that the host application can successfully connect and publish to the MQTT broker.
If you are unsure whether this problem can be causing the issue, you can temporarily set the primary host application ID in the edge node to an empty string. This will cause the edge node to publish data regardless of the status of any host application.
