Describe the bug
I run the OPCPublisher in standalone mode with pn.json configuration. When the first OpcNode has a HeartbeatInterval defined because it's value does not change often but shall be sent anyway, the Value is sent as StatusCode BadMonitoredItemIdInvalid
The missing closing curly bracket is on purpose. That's another problem. It's not a valid Json in this case.
When I move this OpcNode configuration to the end of the array in the pn.json then everything works as expected.
To Reproduce
Steps to reproduce the behavior:
Configure 49 OpcNode's. First has a HeartbeatInterval of 20. The rest hasn't. It's important to have many nodes. It's not reproducible with only a small number of nodes.
Restart OPCPublisher module
=> The first node shows the StatusCode BadMonitoredItemIdInvalid as described above and the JSON is invalid.
Move the OpcNode with the HeartbeatInterval to the end of the array of 49 OpcNodes.
Restart OPCPublisher module
=> All the node values are sent as expected. The node with the heartbeat interval is sent even if the value hasn't changed.
Expected behavior
The order of the OpcNode's does not matter.
The BadMonitoredItemIdInvalid status code should not be sent when everything is configured correctly.
The JSON message is a valid JSON even if there are StatusCode's as Value's.
Describe the bug I run the OPCPublisher in standalone mode with pn.json configuration. When the first OpcNode has a HeartbeatInterval defined because it's value does not change often but shall be sent anyway, the Value is sent as StatusCode
BadMonitoredItemIdInvalid
The missing closing curly bracket is on purpose. That's another problem. It's not a valid Json in this case.
When I move this OpcNode configuration to the end of the array in the pn.json then everything works as expected.
To Reproduce Steps to reproduce the behavior:
BadMonitoredItemIdInvalid
as described above and the JSON is invalid.Expected behavior
Version of OPCPublisher module 2.7.206