I am sending my received uplinks to AWS ActiveMQ but rather than simply 'forwarding' on as JSON, the message gets converted to a string object. This causes problems further down my workflow for extracting the useful parts of the message
Uplink as received in console
Message received as string after using MQTT integration. Message actually looks like it gets truncated, too long for the payload maybe?
I could take the string through NodeRed, but then I need to run an instance of that somewhere, I tried using the advanced JSON template but found this very hit or miss. I would need a different integration and template for every type of device, whereas, if the MQTT integration simply repeated the JSON it could all be carried out with a single integration
I am sending my received uplinks to AWS ActiveMQ but rather than simply 'forwarding' on as JSON, the message gets converted to a string object. This causes problems further down my workflow for extracting the useful parts of the message
Uplink as received in console
Message received as string after using MQTT integration. Message actually looks like it gets truncated, too long for the payload maybe?
I could take the string through NodeRed, but then I need to run an instance of that somewhere, I tried using the advanced JSON template but found this very hit or miss. I would need a different integration and template for every type of device, whereas, if the MQTT integration simply repeated the JSON it could all be carried out with a single integration