MQTT-Explorer icon indicating copy to clipboard operation
MQTT-Explorer copied to clipboard

Support for Decoding Sparkplug-B Payloads

Open AccuBytes-TimJ opened this issue 5 years ago • 3 comments

This is an essential feature for many IIoT devices as they use CirrusLink's Sparkplug-B specification. There is already a project for it: https://github.com/Cirrus-Link/Sparkplug/tree/master/client_libraries/javascript/sparkplug-payload

A selection of decoding options would be great, similar to MQTT.fx

AccuBytes-TimJ avatar Aug 27 '20 23:08 AccuBytes-TimJ

Yes, this would be a great thing to add, including support for sending sparkplug with a list of name and value pairs, birth, death and other certs too.

greggwon avatar Mar 30 '21 21:03 greggwon

I am sending a pull request to decode sparkplugb, I am a go developer not a js dev so this first change if accepted in the future I could try to add more support for sending.

https://github.com/thomasnordquist/MQTT-Explorer/pull/582

So this is about be able to see the sparkplug payload in the views and in the diff panels.

dubyte avatar Aug 08 '21 20:08 dubyte

There seems to be a serious bug with this implementation.

I have no idea what this "Sparkplug" format is, but MQTT Explorer is erroneously trying to use it to decode some topics that are plain text/floating point numbers. It appears to think any string of 5 characters that starts with "5" is Sparkplug, and only shows {} for the value (first noticed this with humidity sensors that report values like 55.49 but also confirmed the same thing happens with strings like 50000 5____ and 5abcd). I don't even see a way to force the decoding off and show the raw values, so the real content of these topics is basically invisible in MQTT Explorer.

kc2zgu avatar May 02 '24 20:05 kc2zgu

#792

bj00rn avatar May 14 '24 07:05 bj00rn