opc-ua-servers

OPC-UA servers, their root nodes and the browse run.

📄️List the configured OPC-UA servers

Returns all OPC-UA servers configured for the current tenant, including their root nodes.

📄️Add an OPC-UA server

Creates a new OPC-UA server for the current tenant. The name must not already be in use. The running client picks the server up and connects to it without a restart.

📄️Test OPC-UA connection parameters

Probes the given endpoint through the opc-ua-client without storing anything, so a server can be checked before it is saved. Returns whether an endpoint answered and, if not, why.

📄️Get an OPC-UA server

Returns the OPC-UA server with the given id, including its root nodes.

📄️Update an OPC-UA server

Updates the connection settings of an OPC-UA server, including taking it out of service and back in through the active flag. The metric pattern can no longer be changed once nodes have been browsed from the server, because it determines their external time series ids.

📄️Delete an OPC-UA server

Deletes an OPC-UA server together with its root nodes. Only possible while no nodes have been browsed from it - a server in use is taken out of service through the active flag instead, which keeps its nodes and their signals.

📄️Browse an OPC-UA server now

Starts a browse run for this server immediately instead of waiting for its interval, so a newly connected address space or a change on the server becomes visible at once. The run happens in the opc-ua-client and can take several minutes on a large address space; the answer therefore reports whether it was started, not what it found. It also ignores the browseNodes flag - that flag switches off the automatic schedule, and a server searched only on demand is exactly what the combination with this endpoint is for.

📄️Add a root node

Adds a node the browse run of this server starts from.

📄️Delete a root node

Removes a root node. The browse run stops there with the next cycle; nodes already found below it are kept.