# Add simple post-process function to mqtt-in node

**URL:** https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439
**Category:** Feature Requests
**Created:** [5 December 2023 14:59 UTC](https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439 "2023-12-05T14:59:19Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![SeRiusRod](https://avatars.discourse-cdn.com/v4/letter/s/278dde/32.png) [@SeRiusRod](https://discourse.nodered.org/u/SeRiusRod)
#### Post date: [5 December 2023 14:59 UTC](https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439/1 "2023-12-05T14:59:19Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [5 December 2023 22:43 UTC](https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439/2 "2023-12-05T22:43:58Z")

</div>

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

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [5 December 2023 23:10 UTC](https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439/3 "2023-12-05T23:10:38Z")

</div>

> [@SeRiusRod](#):
>
> What do you think

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.

---

<div class="post-metadata">

### Author: ![SeRiusRod](https://avatars.discourse-cdn.com/v4/letter/s/278dde/32.png) [@SeRiusRod](https://discourse.nodered.org/u/SeRiusRod)
#### Post date: [15 December 2023 12:17 UTC](https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439/4 "2023-12-15T12:17:06Z")

</div>

I thought so. 😅  
Thank you guys.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [13 February 2024 12:17 UTC](https://discourse.nodered.org/t/add-simple-post-process-function-to-mqtt-in-node/83439/5 "2024-02-13T12:17:23Z")

</div>

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