Hi everyone, I am sending a bunch of MQTT messages using Node-RED and would like to make sure that each new batch is delayed until the previous batch is finished. I tried with a manual delay msg.payload = ""; msg.topic = ""; msg.selectRange = "Ax:Ay"; // Output to output 1 msg.setting = "ip"; no…

Like this [image] In fact the 1/sec rate limit has to go inside the group. It doesn't need to be a rate limit inside the group, it can just be a delay as it only sees one at a time anyway.

[image] AleXSR700: would like to make sure that each new batch is delayed until the previous batch is finished. If I have your request right, you can use my Semaphore Node. which allows exclusivity inside a flow plus some advanced controls (like message priority) [image] @marcus-j-…

This post shows how to run tasks sequentially using standard nodes. [image] "wait until" node changed behavior after recent update General The wait until node appears to be a Home Assistant node. Few here use HA so you may have to ask about it on the HA forum. However, th…

I like using the default nodes, if possible :slight_smile: I tried the linked node combination and it looks very promising. The only downside is that I cannot decide that certain topics are handled faster. [{"id":"b6630ded2db7d680","type":"inject","z":"bdd7be38.d3b55","name":"","props":[{"p":"pay…

What are all these operations that have to be queued like that?

Each topic changes a different config setting of a device. So "ip" will change the ip address of every device connected via MQTT. As that will cause the device to reboot, the next change (e.g. "template" or "settings") must not be executed for around 10 seconds (otherwise the device will not have f…

This waits 10 seconds when the incoming topic changes, but not when the topic stays the same. You could make the function node a little more complex if you only wanted to wait after ip messages rather than whenever the topic changes. [image] [{"id":"45153a8be9284a10","type":"group","z":"bdd7be38…

That looks very cool, thank you. However, it does not work if multiple different topics are being sent at the same time. When that happens, they all get sent to the "topic changed" node and then, after 10 s, all of them get released in parallel. So, topic 1 is sent to output 1 => MQTT topic 2 is…

[image] AleXSR700: it does not work if multiple different topics are being sent at the same time There is no such thing as 'at the same time'. You said [image] AleXSR700: I would like to send all messages of the same topic without queuing and only queue if the topic changes. which is…

It does queue if the following topics are not the same. But it only does this once, i.e. if there are 10 different topics with 5 messages each, then the first 5 of topic 1 will be sent directly and the other 45 will be queued. So far so good, but then the flushing causes the remaining 45 messages (…

[image] AleXSR700: But it only does this once, Can you post your flow please that exhibits this? Just the queuing group and some injects feeding it to show the problem.

Node-RED

Node-RED Forum

Possible to listen to debug console and wait until no more messages?

General

Colin 5 October 2024 16:32 3

This post shows how to run tasks sequentially using standard nodes.

Topic		Replies	Views
Can the Delay node rate limit, but pass first message immediately, and always pass on the latest message? General	76	2066	9 September 2022
Wait for payload to finish flow before passing another payload General	42	1452	29 June 2022
Rate limiting based on exec node completion General	43	1450	3 November 2021
Delay logic request for suggestions General	10	514	10 June 2020
Node-red-contrib-msg-queue - Only storing not forwarding w/ active connection General	20	2217	22 April 2021

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Possible to listen to debug console and wait until no more messages?

Related topics