Configure OPC Server
Configure OPC UA Server with Tags
UI trigger: OPC UA -> Import Tags -> Start Server.
Exposes Litmus Edge's DeviceHub tags through the embedded OPC UA server so downstream OPC UA clients can subscribe.
Step table
Step | API Name | Method | Endpoint / GraphQL Operation | Notes | Output |
|---|---|---|---|---|---|
1 | Get Node Root | POST | {{edgeUrl}}/opcua/v2 -> GetNodeRoot | See current OPC UA hierarchy | Existing node tree |
2a | Import ALL DH Tags | POST | {{edgeUrl}}/opcua/v2 -> ImportAllDHTags | Imports every DeviceHub tag into OPC UA | Nodes created |
2b | Import Some DH Tags | POST | {{edgeUrl}}/opcua/v2 -> ImportSomeDeviceHubTags | Selective import by device or tag IDs | Nodes created |
3 | Start OPC UA Service | POST | {{edgeUrl}}/opcua/v2 -> StartOPCUAService | Starts the OPC UA server | Server running |
4 | Get Service Configuration | POST | {{edgeUrl}}/opcua/v2 -> GetServiceConfiguration | Verify endpoint URL, auth settings | Config object |
Note: server vs client
This workflow configures the server that Litmus Edge exposes (re-exporting DH tags). It is distinct from the OPC UA Advanced client driver used to read data from external OPC UA servers - that lives under DeviceHub.