Ignored values not considered on Instance restart

[tipp88]

Describe the bug
When a DP is set with values to ignore:

The value is basically ignored when the DP is updated by any other adapter BUT
If the DP has a value out of the defined range and you restart influxDB instance, it will write the value to database even if it is not in the range.

SEE all those values has been written to DB by the influxDB adapter on its restart:

To reproduce
Create any DP and define values to ignore like seen in schreenshot above. Apply a value out of the limit manually (adapter will now ignore the value as expected), restart InfluxDB instance, it writes the value to DP even if it is a value which should be ignored.

Expected behavior
No value should be stored to DB on adapter restart.

[Marc-Berg]

Have you set the "Log the last value again on startup" option check box?

[tipp88]

Have you set the "Log the last value again on startup" option check box?

Yes, but that should also consider the values to ignore?

[Marc-Berg]

There is no additional complexity around handling certain values, also: no.

I do not know of any use case where this option (Log the last value again on startup) would make sense.

[tipp88]

I do not know of any use case where this option (Log the last value again on startup) would make sense.

I don't know either and to be honest, I can't remember having this set by intention. I will just deactivate it and hopefully my problem will be solved by this.

[Apollon77]

I tend to reopen ... But the main question is ... what should the adapter log when "log on startup" is enabled AND the value is out of range ... But yes I see this as a "enhancement"

[tipp88]

what should the adapter log when "log on startup" is enabled AND the value is out of range

For me that is clear, same logic as a normal log. If out of range, nothing.