Currently the nodeId for the browser is hardcoded in the configuration of the action. Not sure how this would fit anyone's need.
I want to create a webservice where I can pass a NodeId dynamically as input and get the children as output from the webservice.
The end goal is to create a web app showing a OPC ua browser
Motivation
Passing in parameters dynamically allows us to write applications on top of node-red so that the end user can simply make configurations through a web application instead of having knowledge of node-red.
This issue is stale because it has been open 60 days with no activity. It will be closed in 15 days, but can be saved by removing the stale label or commenting.
Describe the requested feature
Currently the nodeId for the browser is hardcoded in the configuration of the action. Not sure how this would fit anyone's need.
I want to create a webservice where I can pass a NodeId dynamically as input and get the children as output from the webservice.
The end goal is to create a web app showing a OPC ua browser
Motivation
Passing in parameters dynamically allows us to write applications on top of node-red so that the end user can simply make configurations through a web application instead of having knowledge of node-red.