Replicate Flow - Find/Replace

luisfsa502 · 30 November 2018 13:44

Hey All,

I've done several great things with Node-RED, but now i need to replicate (100 times) a flow that i have developed.

The flow which was developed, creates a Group BOX with several information and displays. I tried exporting node and used find/replace tool and reimported to generate a new flow. Well, it've worked substituting the texts (on function blocks), but the group name of displays wasn't updated.

Is there a fast way to replicate flows?

Best regards.

Luis

TotallyInformation · 30 November 2018 16:15

How? To different instances or to the same instance of Node-RED?

Assuming a single instance. Have you tried to use a sub-flow instead of duplicated flows? Or have you tried to refactor your flow so that you only need to duplicate a couple of nodes rather than the whole thing? If you can refactor, you can probably either use subflows or link nodes.

luisfsa502 · 30 November 2018 17:18

Thanks for your reply, TotallyInformation. I don't know if i got what you mean with "Refactor" my flow.

But there are different instances of MQTT and SQL queries. For example: Flow01 is referred to device01, flow02 to device 02, until flow n to device N. I would like to replicate automatically.

Hope i was clearer now. i sent 2 pictures to illustrate what i want to do.

Which options i have?

Thanks!

shrickus · 30 November 2018 18:14

First of all, subflows cannot be used to "replicate" ui nodes...

Secondly, you cannot view 100 sets of graphs at once -- so what is the maximum number of devices you would want to see in the dashboard? You only need to define that many sets of ui elements, and feed in the data for any of the devices when it's time to look at them.

The trick here is to give the user some way of selecting 1 device out of a possible 100... so regular html pulldowns are not good for that. Instead, you will probably need some kind of search box that helps locate the device as you type.

Each time a device has been selected to be shown, that kicks off a flow that retrieves all the information about that device (name, label, id, + data) and updates whichever group that will be used to show it. In this case, the group names will not be shown (since they never change, just the data shown inside each group). You can put ui_text boxes inside each group to show the device info, then pass the new set of data to the chart, which will be redrawn.

So, conceptually, you have one flow that uses mqtt wildcards to listen for data from all 100 devices, extracts the device number from the topic it received, and pushes each record to the database. Then the UI has its own flows to draw the dashboard and switch between which devices are shown. All of which is not easy to set up, but certainly much more maintainable than copy/paste of 100 nearly identical flows!

zenofmud · 30 November 2018 18:19

Code refactoring is the process of restructuring existing computer code—changing the factoring—without changing its external behavior. Refactoring is intended to improve nonfunctional attributes of the software.

Depending on the way you format your MQTT topics and a little code and using a template, you might be able to have a single node for the SQL. I just helped someone change a flow that had 7 MQTT in nodes to one and seven SQL inserts to one.

From your image, it looks like you are doing the same thing for each device. It should be pretty easy.

For detailed guidance, you're going to have to supply your flow for someont to look at. And keep it to the code for two devices if they are all doing the same thing

luisfsa502 · 30 November 2018 20:01

Thanks for your reply shrickus. Certainly i won't set 100 graphs at once, at the same dashboard.

I got what you mean when you say i need to have a selection to define a device. I've already done it in another project, with historical chart. But i don't realize how can i setup/change the datasource of a MQTT using this kind of tool, for example.

By the way, i need 10 devices at once. So, in this case i need to develop a flow with 10 "boxes" and change each target from what i've selected. Right?

luisfsa502 · 30 November 2018 20:15

Thanks for your support mr zenofmud. Can you indicate me which was this discussion? Here's the sample code, i need to change MQTT sources and SQL queries inside my functions.

shrickus · 30 November 2018 21:38

That seems like a sensible approach -- it's still a lot of nodes to manage, but not terrible.

Don't think of it as changing MQTT datasources -- use a single wildcarded topic hierarchy, so you only need one mqtt in node listening to all your devices. Then use the msg.topic string to route the realtime messages through a switch node with 10 outputs, connected to each of the 10 charts.

So let's say you have a flow array of 10 slots, each with a device # in it. I would pass every mqtt msg into a JSONata expression (or a function node) that did a lookup against the slots array. Any that were not found would just be ignored. As an example, I've used a lookup-based "router" like this:

note: only the first 3 of the 10 outputs are defined in this picture

The trick is to use a JSONata expression to lookup the device id and return its index (or -1 if not found):

(
    $index := function($v, $i) {
        $v = topic ? $i
    };
    $slot := $map($flowContext("slots_array"), $index);
    $slot ? $slot : -1
)

Any msg.topic that is not found in the slots_array is silently dropped, while the other 10 active device topics are passed to one of the numbered outputs.

luisfsa502 · 1 December 2018 11:34

Thanks again for your explanations! I've created a selection box, and i'm already indexing my queries based on dropdown entry.

So, from what i understand all of my devices should publish at the same mqtt topic. Then i should pass the index of my device, through topic and create a routine to verify at which index it was published. Right?

Colin · 1 December 2018 12:05

I don't think that is what was meant. I think that it was meant that they should all be in a single hierarchy so you can use a wildcard subscription to get them all from the same MQTT In node. Then you can filter out all except the topic(s) you need for the current selection.

zenofmud · 1 December 2018 12:11

When I immport your flow, there are two nodes you have installed that are not standard - delta and start-up-trigger. What are the actual node names (i.e. node-red-contrib-xxxxx)?

Topic		Replies	Views
Duplicate flows automated in runtime General node-red-dashboard	10	375	26 September 2022
Dealing with variables when duplicating groups of nodes General	5	186	12 December 2023
One "master flow" several "slave flows" General	9	1356	21 April 2020
Duplicate flows and move UI elements Dashboard	3	63	6 November 2024
Replicate UI controls Dashboard	4	327	30 March 2021

Replicate Flow - Find/Replace

Related topics