Waymark / Routes / sparkplug.eclipse.org Structure Sparkplug B MQTT topics and publish birth/death certificate messages for edge nodes and devices
domain: sparkplug.eclipse.org · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docs community attestations: 0✓ / 0✗
Verified steps Build topics as spBv1.0/{group_id}/{message_type}/{edge_node_id}/[{device_id}] per the Sparkplug B topic namespace On connect, register an NDEATH message (carrying a bdSeq number) as the MQTT Last Will and Testament for the edge node After connecting, publish NBIRTH for the edge node before any other node-level message Publish DBIRTH for each attached device only after the edge node has already sent NBIRTH When a device goes offline, proactively publish a DDEATH message for it (this is not an LWT, unlike NDEATH) Increment bdSeq each session so a stale or delayed NDEATH cannot invalidate a newer session Known gotchas DDEATH is application-published, not an MQTT LWT - only the node-level NDEATH uses the broker's LWT mechanism Devices must never publish DBIRTH before their edge node's NBIRTH Confirm sparkplug.eclipse.org is still the canonical spec host at time of use, since the specification has moved hosts before
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp