Proto change filter was never added to dnp3-master, so no filtering was being applied. I added the ProtoChangeFilter on event profile of dnp3-master, to replicate the exact same behaviour as modbus-master.
The ProtoChangeFilter was updated to not flag fields that are not present as differences. In Modbus, it wasn't an issue because all the values are always polled and sent to the internal message bus together. However, with DNP3, you only get changes that might (probably) not include the other values. This was triggering changes on every event even if the mapped OpenFMB value didn't change.
dnp3-master, so no filtering was being applied. I added theProtoChangeFilteron event profile ofdnp3-master, to replicate the exact same behaviour asmodbus-master.ProtoChangeFilterwas updated to not flag fields that are not present as differences. In Modbus, it wasn't an issue because all the values are always polled and sent to the internal message bus together. However, with DNP3, you only get changes that might (probably) not include the other values. This was triggering changes on every event even if the mapped OpenFMB value didn't change.