Assign Group to UI element via Environment variable

[lori]

Hello,

in order to avoid cloning couple of nodes, I want to take usage of the subflow feature. Since I have a lot of UI controls like ui_button or ui_switch. Therefor I need the ability to select the group in a instance of the subflow via environment variable. However I didn't found a way to achieve this with node red v3.1.9.

Is there any way to select the group of a ui_element in a dynamic way?

[Steve-Mcl]

That capability was added to node-red 4.x. It is currently in beta. Give it a go

Node-RED 4.0.0-beta.3 released

The third and hopefully final beta release of Node-RED 4.0 is now available! Update May16th: We've republished the beta as 4.0.0-beta.3-1 to fix a packaging error. Node-RED 4.x requires at least Node 18.x. We recommend using Node 20 This release addresses all of the issues that had been highlighted against the previous beta, and throws in some new features. Here are the highlights. The Change Log has the full list of changes. Note: if any issues are reported against the beta, we'll u…

[lori]

@Steve-Mcl thanks for pointing me to. I give this container a try nodered/node-red-dev:v4.0.0-beta.3-1.

I still see this issue, so with the version mentioned this now should work? Are there docs available explaining of how to handle ui elements within subflows? Does this also work with the legacy dashboard or only with the new flowfuse? I am always

I am always a fan of early adaption but I am struggling a bit, my main points are:

• Is there a migration guide from Dashboard 1.0 to flowfuse?
• Can I simply export my nodes from Dashboard 1.0 and import it to flowfuse?
• Is there a list of features flowfuse has in comparison to the legacy dashboard?

[Steve-Mcl]

@lori

migration guide from Dashboard 1.0 to flowfuse

Searched your word in Google & this: Dashboard 1.0 Migration Guide | Node-RED Dashboard 2.0 was the first result

@lori

Can I simply export my nodes from Dashboard 1.0 and import it to flowfuse

Kinda, but due to underlying technology changes and not all contrib nodes exist for dashboard 2 so it probably won't work

@lori

Is there a list of features flowfuse has in comparison to the legacy dashboard

Dashboard Backlog • FlowFuse

@lori

I still see this issue , so with the version mentioned this now should work

Installing node-red v4 only enables your original request for seeing the group as subflow env var. The issue is still open.

@lori

Are there docs available explaining of how to handle ui elements within subflows?

There are some (search forum and internet)

@lori

Does this also work with the legacy dashboard

Allowing you to set a config node as a subflow env var is node-red feature introduced in v4. It is available to all nodes including dashboard 1. However dashboard 2 has awareness of this feature and let's you see the subflows in the sidebar & correctly groups together the elements when more than 1 instance is added to the same group. Dashboard 1 does not. Also, the issue you mentioned above will affect dashboard 1. Even more so as dashboard one will inter mix UI elements from multiple instances added to same group as it has no native awareness of being a subflow insurance.