MQTT IN payloads are now parsing as primitive types bool at least, assuming numerics and arrays would too but haven't tested) rather than as strings. Assuming this is due to the new "autodetect JSON payloads" it seems to do? Intended? Meaning, I'm getting true/false instead of "true"/"false", etc. E…

Whenever we introduce a change in behaviour in nodes, we try to minimise the impact to existing users and their flows. This is why, when we introduced the new behaviour in 3.0 it only applies to newly added nodes. Existing nodes behave as they did before. It is up to you whether to adopt the behav…

So it IS the intent to parse not just JSON OBJECTS but primitive JS types from strings now? Did I miss that announcement then, as I didn't see it in the 3.0 changelogs? To be clear here, its not parsing "JSON object, binary buffer or string" its parsing to "JSON object, binary buffer, string, numbe…

[image] i8beef: So it IS the intent to parse not just JSON OBJECTS but primitive JS types from strings now? If you check the definition of JSON you will see that it does include primitive types, so, for example, the string "true" is valid JSON representing the Boolean true. So the new behavio…

[image] i8beef: To be clear here, its not parsing "JSON object, binary buffer or string" its parsing to "JSON object, binary buffer, string, number, float, array, bool, No, JSON is always a string. It is parsing from JSON to js object, array, or primitive. This post should help to clarify th…

Im assuming that's a "yes, intended behavior" then? I'm fine with that, it just wasn't a change I could find documentation for, and I couldn't figure out why two nodes that looked identical were returning different things. For the record, then, old nodes don't always select the old deprecated "stri…

[image] i8beef: half the time they are selecting the NEW option still for me which makes them look IDENTICAL to the NEW nodes I'm creating, but are FUNCTIONING differently Can you post a screen shot of the config of the two that appear the same but function differently?

If you have a backup of the flow it would be very useful to see this. There may be something we missed in v1->v3 upgrade to make this transparent and backwards compatible.

Ok I pulled the git repo and searched through the flows.json manually on an old commit... here's an example of two MQTT IN nodes that were right next to each other. Im not positive this exhibits the issue, but one of these has a "dataType: auto" and one doesn't have ANY dataType specified... if I'm…

MQTT IN payload type detection inconsistency

General

i8beef 28 December 2022 09:10 8

Unfortunately, no, I've already corrected all of them, and I don't seem to be able to put it back into that state now through the interface. Wild guess, the configuration at one time didn't save a value for the output parsing (null, these were all mostly setup back in 1.x days probably) and while it falls back to the deprecated BEHAVIOR in this case, the UI did NOT handle it and so selects the "default"?

Topic		Replies	Views
Improvement of mqtt-in Nodes Core Development	19	1279	28 March 2022
Detect Payload is JSON object vs. String vs. Array General	19	2152	25 April 2021
MQTT-in node - autodetect string, buffer and JSON object Feature Requests	14	3101	28 November 2019
Un-deprecate "string or buffer" autodetection in mqtt-in node Feature Requests	8	254	29 October 2023
MQTT in Node, changed some how? General function-node	8	312	13 May 2022

MQTT IN payload type detection inconsistency

Related topics