Could you elaborate on that second point a little more?
What I'm trying to do seems pretty straightforward. I'm reading a serial string from an RS-232 device in Node-RED, parsing that string with a function node and storing 3 values from the string in 3 different properties of the msg object. Then I want to pass those 3 properties as tags to Ignition Edge to use in Designer. So I'm really only worried about the "direction" FROM Node-Red TO Ignition Edge.
Apologies if my terminology is a little off, I'm still learning.
I've never actually used Node Red, so my suggestions are based on superficial knowledge I gained from Google...
It looks like Node Red has an OPC UA server module / feature you can add to it some how. You could probably expose these message properties via the server, then make an OPC UA connection from Ignition to Node Red.
Node Red also supports MQTT, and you could publish those properties to an MQTT broker, and receive them in Ignition using the MQTT modules. The MQTT modules should be a part of at least one of the Edge editions.
As kevin pointed out Node-Red does have a OPC Server node.
There is a stripped down version of the server but the above gives you more features to expand later on and it has more examples for you to follow.
You could also use MQTT
I've used both methods, For what you are doing, its down to which road you think will be easier. I think MQTT may need a little bit more set up in ignition, Vs telling ignition what IP address to discover the OPC server. This is assuming your node red device is on the same network as ignition. If not, use MQTT.
What about TCP module? I guess Edge may support TCP module of Ignition which can be used to communicate with Node Red. But I guess OPC UA is built in module so it may be better approach.