Why not send_first_at bigger than send_every

Hi,
why not to allow to configure send_first_at higher then send_every, for example up to window_size. In some cases its reasonable to publish first value after the filter is fully filled up and has good value, not starting noise.

You could lambda a filter to only send value in between two thresholds.

No, I mean:

    - sliding_window_moving_average:
         window_size: 256
         send_every: 16
         send_first_at: 256

First send after 256 samples and then every 16th. Regardless of value.