I am not sure if mqtt are part of the core development - but I guess, as I don't have to install them extra, that they are part of the core nodes. When I use the mqtt-in Nodes (and I know that in mqtt this is standard) all messages, which come in are strings or a buffer and therefore this is the de…

Why are you getting inconsistent data on the same topic?

[image] Colin: Why are you getting inconsistent data on the same topic? As I can subscribe multiple topics using wildcards in the same node, like topic1/#

Are there any comments or does nobody see the advantage if mqtt-nodes will provide correct data-types automatically?

If you had multiple data types coming in when subscribed to a single topic, wouldn't you need to test them when the msg exits the mqtt-out node to see what it contains? Or are you suggesting that the node have a seperate output for each data type? Would the node have selectable options and if ou ch…

As I described - when I use the option that output is an analyzed JSON object - I get correct numbers, booleans and JS objects as output. If I use this option in the mqtt-in Node and the topic contains a simple string then I get an error - that this is not a JSON string. [image] So the only chang…

Hi. I understand your request and at first glance it seems reasonable to ask for the payload to be auto converted however I'm still pondering the effort Vs benefit right now. subscribing to a # topic that returns many payloads with different types of payload means at some point further down your fl…

The # is not always the root level - it could be device topic which contains different datatypes. Yes and I want to prefer to react on data types within the flow instead of having different triggers which start different flow parts . If you say the structure of the publisher is not ideal - this coul…

[image] mickym2: For sure - converting data is always possible - but I can not see the issues - why it is so difficult to improve the mqtt-in node to retrieve all native datatypes - as it works already - except for strings. Not to be overly pedantic, but it does work for strings if you provid…

[image] knolleary: But we could consider adding an extra checkbox that is shown when the 'parsed JSON Object' mode is selected as to how invalid JSON should be handled. The default would be the existing behaviour - trigger Catch nodes. But if the option is enabled, then pass on the payload as a …

Improvement of mqtt-in Nodes

Core Development

mickym2 27 January 2022 13:40 17

As I read your release notes for 2.2.0 I still cannot see a change in the mqtt nodes. There is something mentioned for json nodes - but this is a different story. So I would repeat my question - when the auto mode in the mqtt-in node would be a complete auto mode (incl. strings)?

Topic		Replies	Views
MQTT-in node - autodetect string, buffer and JSON object Feature Requests	14	3135	28 November 2019
Detect Payload is JSON object vs. String vs. Array General	19	2172	25 April 2021
MQTT IN payload type detection inconsistency General mqtt	10	302	26 February 2023
Issue retrieving json from mqtt General	16	3357	7 March 2019
Feature request: mqtt-in node converts JSON to JS object Feature Requests	16	1325	5 February 2019

Improvement of mqtt-in Nodes

Related topics