You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of having a continuous stream and so that there aren't 5000 points of data per day can throttle average be added to the sensor?
Another workaround would be to create a way to optionally only send through template rather than sensor directly. throttle_average could be applied to template sensor.
throttle_average
An average over the specified time period, potentially throttling incoming values. When this filter gets incoming values, it sums up all values and pushes out the average after the specified time period passed. There are two edge cases to consider within the specified time period:
no value(s) received: NaN is returned - add the heartbeat filter if periodical pushes are required and/or filter_out: nan if required
one value received: the value is pushed out after the specified time period passed, without calculating an average
For example a throttle_average: 60s will push out a value every 60 seconds, in case at least one sensor value is received within these 60 seconds.
# Take a measurement every 10s but only report the average # every 300s. This is to overcome the noisy ADC on the ESP32.update_interval: 10sfilters:
- throttle_average: 300s
The text was updated successfully, but these errors were encountered:
Instead of having a continuous stream and so that there aren't 5000 points of data per day can throttle average be added to the sensor?
Another workaround would be to create a way to optionally only send through template rather than sensor directly. throttle_average could be applied to template sensor.
throttle_average
An average over the specified time period, potentially throttling incoming values. When this filter gets incoming values, it sums up all values and pushes out the average after the specified time period passed. There are two edge cases to consider within the specified time period:
no value(s) received: NaN is returned - add the heartbeat filter if periodical pushes are required and/or filter_out: nan if required
one value received: the value is pushed out after the specified time period passed, without calculating an average
For example a throttle_average: 60s will push out a value every 60 seconds, in case at least one sensor value is received within these 60 seconds.
The text was updated successfully, but these errors were encountered: