Re: [mosquitto-dev] mosquitto-dev Digest, Vol 47, Issue 7

[Brandon Arrendondo <barrendo@xxxxxxxxx>]

I think piping the mosquitto_sub output to another tool is fine,
provided the tools themselves exist on the target machine.  For
embedded Linux installs (think busybox/DD-WRT) where tool support
(python, etc) is potentially lacking, having the base tools provided
by mosquitto provide the capability is a nice to have.

It isn't difficult otherwise to write a one-off embedded C client to
accomplish the same - I just think if binary payloads are a common
part of the MQTT protocol then mosquitto_sub should have some option
to support output of them in some way - the default of displaying the
characters as ASCII does not work well for binary payloads or
(depending on the terminal) unicode payloads.

Regards,
Brandon

On Wed, Nov 22, 2017 at 7:01 PM, Tatsuzo Osawa <tatsuzo.osawa@xxxxxxxxx> wrote:
> Hi there,
>
> There are many wishes for the output format of mosquitto_sub.
> I guess, for unix experts, the best way is supporting unix pipe for an
> output target of mosquitto_sub.
> You can combine any command or text processing with mosquitto_sub to
> get your favorite format.
>
> e.g.
> 1) msoqutto_sub -h localhost -t "#" | od -t x         (output binary by hex)
> 2) msoqutto_sub -h localhost -t "#" | python -m json.tool     (output
> pretty JSON format)
>
> What do you think about this idea?
>
> Regards,
> Tatsuzo
> _______________________________________________
> mosquitto-dev mailing list
> mosquitto-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/mosquitto-dev