another question: is it expected behavior that ben...
# umh-support
d
another question: is it expected behavior that benthos-umh outputs the same value after 30sec of the previous value? (sounds like a bug to me)
this is with subscribe = true in the yaml
used yaml: input: opcua: endpoint: 'opc.tcp://192.168.73.1:4840' nodeIDs: [ns=3;s="DB_00CommunicationDayResults"] subscribeEnabled: true pipeline: processors: - bloblang: | root = { meta("opcua_path"): this, "timestamp_ms": (timestamp_unix_nano() / 1000000).floor() } output: mqtt: urls: - '192.168.2.30:1883' topic: 'umh/v1/TLT/Muzzroom/Meulebekestraat/ProductionLine3/SortingUnit2/originID/_historian/${! meta("opcua_tag_path") }' client_id: 'benthos-umh'
2 Views