Skip to main content
POST
Attach points to a virtual device
Attaching moves a point. It keeps its id and its trend data, but its modeling is reset, including canonical type, measurement, precision and unit. Attach first, then apply modeling.
Only origin points on pseudo devices can be attached. The point’s current device is read from the point. A copy, a point on a real device, and a point on a different virtual device are refused with 400. To show a point of a real device on a virtual device, use Copy points to devices. The request is checked as a whole before anything moves. The points are then moved one source device at a time. If one device fails, the devices before it stay attached and the rest are not attempted. Repeat the request: points already on the virtual device are skipped and listed in skipped. The response has attached, the ids of the points that were moved, and skipped, a list of pointId and reason for the points that were already on the device. The order of ids in attached is not defined.

Authorizations

Authorization
string
header
required

Paste an access token from Create an access token. Tokens expire, so request a new one if you receive 401.

Path Parameters

buildingId
string
required

Building identifier from List buildings.

virtualDeviceId
string
required

ID of virtual device

Body

application/json
pointIds
string[]
required
Required array length: 1 - 200 elements
Maximum string length: 128
Pattern: [^\p{C}\p{Z}]{1,128}

Response

The points that were attached and the points that were skipped.