Instead of #105, this could solve the issue raised by Cory, although I'm still not convinced it's the best solution.
The SOEHandler now checks if it modified something on the OpenFMB profile before publishing it.
I foresee these limitations:
If two profiles are linked to the same poll and only one of them fills the OpenFMB profile, both profiles will be published.
If DNP3 events are received but map to the same OpenFMB values (e.g. multiple analog input values that map to the same enum value), it will publish the events, even if the message is identical to the previous one.
If a profile only has static data not read from DNP3 (e.g. only constant strings), it will never publish.
Instead of #105, this could solve the issue raised by Cory, although I'm still not convinced it's the best solution.
The
SOEHandlernow checks if it modified something on the OpenFMB profile before publishing it.I foresee these limitations: