Hi Pascal,

This behaviour is indeed exactly as it was implemented. Monitored values are usually used for looking at status changes, valve states, ... so the deadband didn't seem necessary.

Do you have a special use case that requires other behaviour?

from node-opcua-logger.

Hi,

Thanks for the response. After your explanation it seems logic to me and I think I can manage.
In the sample config file, the deadband parameters are also there for the "monitored" option. Maybe that was the reason for the confusion from the start.

A monitored node

[[measurements]]
name = "Int32monitored"
tags = { tag1 = "test", tag2 = "AB43" }
nodeId = "ns=2;i=10849"
collectionType = "monitored"
monitorResolution = 1000 # ms
deadbandAbsolute = 0 # Absolute max difference for a value not to be collected
deadbandRelative = 0 # Relative max difference for a value not to be collected

from node-opcua-logger.

@psmt You're right. That is confusing. I'll update the readme!

from node-opcua-logger.