Shared Target Fields and Bindings

A shared target defines which remote device receives data from the local device. Bound sharing configurations determine what is sent.

Target fields

Field	Description
shareTargetCode	Unique shared-target code
shareTargetName	Display name
targetDeviceCode	Receiving device code; must exist in device information and cannot be the local device
note	Optional notes

Create with POST /share-target/add and modify with POST /share-target/update. Use GET /share-target/detail to inspect the target device and all configuration bindings.

Bind sharing configurations

A sharing configuration contains shareConfigCode, shareConfigName, shareStrategy (CRON), and shareConfig (a comma-separated list of local points). A target can bind multiple configurations.

Add bindings with POST /share-target/add/config:

{
  "shareTargetCode": "demo_target",
  "shareConfigCodes": ["demo_metrics"]
}

Replace example codes with actual existing configurations. POST /share-target/update/configs replaces all bindings. POST /share-target/delete/config deletes a binding using one shareConfigCode.

Networks and multinode relationships

Device codes are stable identities; device IPs are connection addresses. Multiple senders targeting one receiver can aggregate data. A device can also receive downstream data and send its local aggregation results upstream.

When replacing the receiver, update targetDeviceCode. When network addresses change, update device information. Verify connectivity and data afterward. Do not continue using the old master-device IP plus slave-device list parameters.

See Device coordination configuration for steps and UDE for template-based management.