HeartBeat Interval is not working in OPC Publisher 2.9.11

[vity-topsoe]

Describe the bug
HeartBeat Interval is not working , For Tags whose value is not changing ,OPC Publisher is not emitting those.

To Reproduce
Steps to reproduce the behavior:
1Apply OPC Publisher 2.9.11
2. Set -hb =36000
3.

Expected behavior
All nodes which are not changing values ( we have set OpcSamplingInterval to 5 minutes) should emit last known value

Screenshots

OpcPublisher Configuration
"Cmd": [
"publisher",
"--pf=/appdata/publishednodes.json",
"--lf=/appdata/publisher.log",
"--aa",
"--me=Json",
"--mm=PubSub",
"--fm=false",
"--cfa=true",
"--fd=false",
"--bs=250",
"--si=10",
"--di=60",
"--tm=True",
"--ih=Mqtt",
"--hb=3600",
"--ot=300000",
"--tp=/appdata/pki/trusted",
"--rp=/appdata/pki/rejected",
"--ap=/appdata/pki/own",
"--ip=/appdata/pki/issuer"
],

OPC Publisher version 2.9.11
Number of Nodes : 416

Additional context
Add any other context about the problem here.

[vity-topsoe]

@marcschier Some more Information : We tried it on Matrikon Simulation server (OPC UA).It seems working fine however with Aspen InfoPlus.21 OPC UA Client .It is not working.

We recently switched from 2.8 to 2.9

[marcschier]

The intention is to emit a heartbeat every hour? Or every 10 hours? The config looks like you want it every hour correct?

[vity-topsoe]

The intention is to emit a heartbeat every hour? Or every 10 hours? The config looks like you want it every hour correct?

Yes , we want it every hour as it will be applied for all nodes.
To set different Heartbeat to each node, I believe we need to add with each node.

[marcschier]

Yes, just asking as above description said 36000 and 3600, - just wanted to know so I can test. And indeed I tested with 5 nodes that do never change, and I see a heartbeat emitted every hour with the latest build. Can you try "2.9.12-preview4" tagged container from mcr to confirm?

[vity-topsoe]

Yes, just asking as above description said 36000 and 3600, - just wanted to know so I can test. And indeed I tested with 5 nodes that do never change, and I see a heartbeat emitted every hour with the latest build. Can you try "2.9.12-preview4" tagged container from mcr to confirm?

We tested it earlier versions with Matrikon OPC Simulator it was working but not with Aspen InfoPlus.21 OPC UA Client.
To check with Aspen InfoPlus.21 OPC UA Client we need a release version so we can apply it on production device.
I will check the preview version with Matrikon OPC Simulator and will let you know.

[vity-topsoe]

efs:1]: Failed to connect to opc.tcp://serverip:21381/MatrikonOpcUaWrapper: Error establishing a connection: Could not process OpenSecureChannelResponse....

With 2.9.12-preview4 it did not respect "--cfa=true" and seems not connecting however it is not even generating self signed certificate ,No certificate in Rejected