Link an OPC-UA object node to an existing asset
PUT/opc-ua/nodes/:opcUaNodeId/asset
Links a browsed OPC-UA object node to an asset that already exists, and nothing else: the asset keeps its name, its properties and its place in the hierarchy, and the variables of the object keep their retrieval configuration.
The counterpart of POST /opc-ua/assets, which creates the asset itself. This is the way in for an asset built elsewhere - by a script deriving the hierarchy from the address space, for instance, or for an object that has to be re-linked after DELETE.
An asset comes from exactly one OPC-UA object and an object feeds exactly one asset, so a node or an asset that is already linked is refused with 409. Use DELETE first to move a link.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 409
- default
The link was created. Only the link: the variables of the object keep whatever retrieval configuration they have, and none of them is activated by this - use POST /opc-ua/signals or PUT /opc-ua/nodes/{opcUaNodeId} for that.
The addressed node is not an object node.
Unauthorized — the bearer token is missing, expired or invalid, or carries no role. Errors raised by the security aspects contain an ErrorDto body; requests rejected by the security filter chain may have an empty body.
Forbidden — the authenticated user lacks the required role or access rights.
No such OPC-UA node, or no such asset node.
The node is already linked to an asset, or the asset already comes from another OPC-UA object.
the default error response