# Process MQTT-data time triggered

**URL:** <https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912>\
**Category:** Dashboard\
**Created:** [14 November 2020 11:44 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912 "2020-11-14T11:44:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![GTiglio](https://avatars.discourse-cdn.com/v4/letter/g/90ced4/32.png) [@GTiglio](https://discourse.nodered.org/u/GTiglio)\
**Post date:** [14 November 2020 11:44 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/1 "2020-11-14T11:44:11Z")

</div>

Man, this can't be so difficult - but I can't manage to get this to work:

I have a MQTT-input node which sends every few seconds a value. I need every hour the last value of this MQTT-node to store it in an Influx DB. I set up an inject-node, which triggers at each hour, but how to combine the inject message with the MQTT-value to send the value hourly further to the InfluxDB ?  
I tried with an function-node, the trigger works, but how to get access to the MQTT-payload?

---

<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:** [14 November 2020 11:56 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/2 "2020-11-14T11:56:57Z")

</div>

There are a few ways. One of them would be to use the join node..

See [this article in the cookbook](https://cookbook.nodered.org/basic/join-streams) for an example of how to join messages into one object.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [14 November 2020 12:30 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/3 "2020-11-14T12:30:00Z")

</div>

Another way would be to have the `mqtt-in` node feed a `trigger` node set like this:

 ![Screen Shot 2020-11-14 at 7.29.03 AM](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/f/7f0878197ce83dd56e86805bf0391d7bedbe4872.png)  
This is ony allow one msg per hour to pass thru.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [14 November 2020 13:35 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/4 "2020-11-14T13:35:03Z")

</div>

Or a Delay node

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/b/abe47a2b46a324ac47e06b48890ba9fb29144487.png)

If there were multiple channels that this needed to handle then one Delay could do them all by putting it into `For each msg.topic` mode.

---

<div class="post-metadata">

**Author:** ![GTiglio](https://avatars.discourse-cdn.com/v4/letter/g/90ced4/32.png) [@GTiglio](https://discourse.nodered.org/u/GTiglio)\
**Post date:** [14 November 2020 17:17 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/5 "2020-11-14T17:17:16Z")

</div>

Perfect, thanks... It seems I struggle stills with basics...

---

<div class="post-metadata">

**Author:** ![GTiglio](https://avatars.discourse-cdn.com/v4/letter/g/90ced4/32.png) [@GTiglio](https://discourse.nodered.org/u/GTiglio)\
**Post date:** [14 November 2020 17:19 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/7 "2020-11-14T17:19:28Z")

</div>

thank you !

---

<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:** [14 December 2020 17:19 UTC](https://discourse.nodered.org/t/process-mqtt-data-time-triggered/35912/8 "2020-12-14T17:19:32Z")

</div>

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