MQTT: hack filename sends bytes rather than a string

It appears all the hack/METHOD payloads are send as strings, for example

However, hack/filename is sent as bytes making it difficult to parse. Any chance this can be changed to be a string like the rest?

added MQTT label

assigned to @rswindell

The action/hack/+ messages are all published in exactly the same manner, and all as strings.

Whatever you're using to view these topics is what is deciding that it is binary and not text. Did you try using mosquitto_sub instead (as a test)? Looking at the example, all those bytes are valid US-ASCII chars, so shouldn't be considered binary. There should be a corresponding log entry in your hack.log file (with the filename), does it look weird/binary?

Are you able to reproduce this problem yourself?

I'm not sure how I'd use mosquitto_sub to push past events. That said, I did figure it out eventually. It seems like auto detect was on and it was considered binary. I've now forced it to be a string and it looks much better. nodered uses some cached messages so I'm able to see how it looks. Thanks.

You'd use mosquitto_sub to read the message. Pretty much all the messages are pushed with the "retain" flag, so you can see the last published message on any topic, always. You don't have to be actively subscribed/listening at the time of publish.

closed