-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support for Protobuf decoding of payloads #196
Comments
Don't you need the actual schema for each model to be able to decode Protobuf messages? |
https://stackoverflow.com/questions/35049657/how-to-decode-binary-raw-google-protobuf-data |
I would really like this feature. Would it be possible to select/import a proto file for a given topic ? |
Sorry late response on this :D |
Would love to see this too. Moving to protobuf as standard for all of our payloads |
@thomasnordquist, are you happy for a PR? If so, is there any thing you would like us to consider? cheers |
I have a working proof of concept that I could share. Any suggestions how to integrate this feature in the UI? |
Here it is: #532 |
I was kind of stunned to see this tool (which is pretty slick!) doesn't support sparkplug B protobuf decoding, I would think this would at a minimum would make sense given it is a popular industry standard. Proto file details located here. |
it is, but MQTT has so much more than just industrial control, and i would
imagine that the use of sparkplug doesnt even register on the use of MQTT.
But very cool that someone has implemented protobuf de-serialisation. my
next issue is that we Gzip our payloads prior to sending to reduce the size.
…On Fri, Apr 23, 2021 at 1:33 AM Ben Becker ***@***.***> wrote:
I was kind of stunned to see this tool (which is pretty slick!) doesn't
support sparkplug B protobuf decoding, I would think this would at a
minimum would make sense given it is a popular industry standard. Proto
file details located here
<https://github.com/Cirrus-Link/Sparkplug/blob/master/sparkplug_b/sparkplug_b.proto>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#196 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABST2IBTRW4QAD3ARLKYVJ3TKBMV3ANCNFSM4IOUEBLQ>
.
|
@thomasnordquist - curious to see what kind of help you'd need on your end - this would be a great add to an already helpful tool! |
No description provided.
The text was updated successfully, but these errors were encountered: