Node-Red: Dynamic Groov I/O Module & Channel Index

[eric3]

Is it possible to dynamically set the values of the module/channel index fields for the Groov I/O nodes?

Fairly sure I know the answer is no. But want to ask just in case I’m missing something.

I am trying to handle incoming HTTP requests that have an asphalt silo number in the payload. It would be great to dynamically set the module/channel index based on the payload so I could have 1 flow to trigger N number of silos instead of needing to configure 1 flow per silo.

[eric3]

Just found @torchard’s reply here: Optimizing Node Red Flow - #10 by torchard

Going to give this a go!

Note to self: read the docs

[torchard]

I’m glad you found that — the forum search brings up a few other examples you might find useful:

Dynamic, Self-Updating groov Tables (with Node-RED)

A lot of the time we find ourselves with tons of data available to us but we only care about seeing a particular subset, for example only the points that have recently changed or only the points that are turned on. Regardless of the application there can be a lot of value in using dynamic lists that re-sort themselves on the fly. Here’s an example of a Node-RED flow that dynamically changes pump information being displayed in a groov View screen based on which were most recently toggled: [ima…

Two ways to loop dynamic write objects for Opto nodes

If you check the help information for groov or PAC nodes, you see that there are specific JavaScript object properties you can define to dynamically write values to your Opto tags. In this post I’ll use groov View nodes, but the technique applies to PAC nodes as well. Here is an example object that the groov View nodes can write from: msg.payload = { tagName : 'MyTable', tableStartIndex : 5, value : 10 }; Sometimes the tag name will always be the same and you can just …