You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create subscription (MonitoredItem) to some node. Then I need to temporarily remove the monitored node from OPC UA tree. I add the node back to OPC UA tree by creating new node with same identifier. How can I relink the old subscritption from previous old removed node to the new node (that has the same identifier but is different instance)? Is that possible or should I cache and reuse the old node? Or how to correctly deal with situation with subscription on node that can be temporarily removed?
Expected Behavior
Already existing subscription would work on new node with same identifier. Subscription is somehow relinked to the new node.
Steps To Reproduce
Create subscription (MonitoredItem) to node
Remove the node from OPC UA tree
Create new node with same identifier and add it to OPC UA tree
How to relink the subscritpion from the old node to the new node?
Additional note: I mean on the OPC UA server side how can I relink the subscription (what should I do on the server when new node (with same identifier as old removed node) is created). And so for the client the subscription would automatically continue to work without doing anything (like delete existing subscription and create new subscription).
Type of issue
Current Behavior
I create subscription (MonitoredItem) to some node. Then I need to temporarily remove the monitored node from OPC UA tree. I add the node back to OPC UA tree by creating new node with same identifier. How can I relink the old subscritption from previous old removed node to the new node (that has the same identifier but is different instance)? Is that possible or should I cache and reuse the old node? Or how to correctly deal with situation with subscription on node that can be temporarily removed?
Expected Behavior
Already existing subscription would work on new node with same identifier. Subscription is somehow relinked to the new node.
Steps To Reproduce
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: