Add simple post-process function to mqtt-in node

Core Development Feature Requests
1

I don't know if this is possible, from a design conventions point of view, but it would be nice, that in case of selecting "Json parsed object" to be able to specify a sub-level for retrieval.

I'll explain: Most of the consumer and PV devices I work with publish their payloads as: {value: 240.5}, for example.
If one could tell the node to get the value property of the payload, it would simplify the flow, saving a repeating change node.

What do you think?

2

Sounds like a great job for a change node. Let mqtt nodes deal with mqtt and change nodes change messages. :grin:

4 Likes
3

I think that all* nodes that receive input should let you consume msg.payload.value (or whatever property of the message you desire)

Something Dave & I have discussed and mostly agreed on for core nodes *where sensible.

A pattern I hope will catch on.

4

I thought so. :sweat_smile:
Thank you guys.

5

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.