Hi,

There is the concept of ModelChangeEvents (see https://reference.opcfoundation.org/Core/Part3/v105/docs/9.32), however please note that in order to benefit from that the Server must support it and the affected nodes must also have the NodeVersion Property. There is no “get all node changes” type of way. In practice this is because the address space could potentially/theoretically be infinite and/or the server itself might not even know the nodes (and might just consult some backend service) and it wouldn’t be efficient data-wise either (thus basically everything in client-server is based on the client request).

If you are making the server yourself using our SDK, then operations done within
com.prosysopc.ua.server.NodeManagerRoot.beginModelChange()
com.prosysopc.ua.server.NodeManagerRoot.endModelChange()
transaction will be sent as the GeneralModelChangeEvent. SDK probably cannot detect the creation of a node (since it doesn’t have the NodeVersion at that time), but changes can also be added manually via com.prosysopc.ua.server.NodeManagerRoot.addModelChange(UaNode, ModelChangeType…) (while the transaction is open). You could also define your own event type etc. that isn’t tied to NodeVersion Property.

If you do not have control over the server there isn’t much you can do (except ask the server vendor of any mechanisms to notifying changes, you could also e.g. just have a single node telling some configuration version and then subscribe to that and then Browse again if that changes). You could re-Browse periodically maybe and see if there are changes.