I’m trying to understand the fine details surrounding the use of “codecs” for payload decoding, and the resulting data. Hope that someone can clarify a bit.
Now, when I look in the web interface at the “Device Data” tab for a node, unfolding the details for an uplink packet appears to show a proper object for “objectJSON”. However, when I look at the data that is posted via the HTTP Integration (with the “JSON” marshaler selected), the “objectJSON” key is present but doesn’t contain a proper JSON object, it contains a stringified version.
I found two references in the forum about this, but I don’t understand yet why it behaves like this. It’s quite a pain to parse the whole message and retrieve specific fields from the decoded payload when halfway through the JSON path one has to throw in some specific type cast, while all the rest already is properly structured JSON.
I haven’t tested the “legacy” JSON marshaler yet (is this the json_v3 that was also referred to?), because it will be deprecated. Is it possible to get a future proof way to get a proper JSON object through the HTTP integration?