Alexander Köpke

@Mkasakka which version of OPC Publisher are you using? Do you use it standalone (which I expect) or as part of Industrial IoT Platform? Please try to use `--mm PubSub`...

I've tested the OPC Publisher in standalone version 2.8.0 with the complexe data type of iot-edge-opc-plc (with --ctb) and the complexe data type is working: ```json { "MessageId": "379", "MessageType":...

@mregen is this information sufficient or do we require something else?

Currently ARM64 isn't supported but we will handle this as an feature request. In the meantime you could use the ARM32 variant by installing 32bit OS.

Changed to feature request, the decoding can only work with reversible encoded payload and currently the whole payload is encoded non-reversible.

@jehona-m could you follow-up on this request ?

Thanks for the context, as a user yesterday it was strange for me that the oldest possible version of kubernetes was deployed. If I don't specify anything I would assume...

Please try to add the elevation _header_ as payload to start-publishing `{{baseUrl}}/publisher/v2/publish/{{endpointId}}/start` or bulk-publishing `{{baseUrl}}/publisher/v2/publish/{{endpointId}}/bulk` : ```json { "item": { "nodeId": "nsu=mySampleNamespace;s=myNode" }, "header": { "elevation": { "type": "UserName", "value":...

Reading OPCEvents is a specific features, that is currently not implemented, I will see this issue as feature request to support Alarms and Events for OPC Publisher.

Thanks for the feedback, we will handle this issue as feature request.