Riemann sum integral sensor not updating while source sensor value is stable

[itssimon]

The problem

The Riemann sum integral sensor currently only updates when the source sensor updates, which is not always sufficient. Ideally it would calculate a new value periodically too, even if the source sensor value remains stable.

For example: I’m monitoring the energy used by our pool filtration system. It’s power usage stays exactly the same throughout the day after a brief priming phase. In this scenario the integration sensor does not calculate the energy used until the end of the day when the pump stops.

What version of Home Assistant Core has the issue?

2023.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Integration - Riemann sum integral

Link to integration documentation on our website

https://www.home-assistant.io/integrations/integration/

Diagnostics information

No response

Example YAML snippet

sensor:
  - platform: integration
    source: sensor.pool_filter_pump_power
    name: Pool Filter Pump Energy
    unit_prefix: k
    round: 2
    method: left

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @dgomes, mind taking a look at this issue as it has been labeled with an integration (integration) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of integration can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign integration Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

integration documentation
integration source
_{^{(message by IssueLinks)}}

[rgb-Argentum]

I'm afraid that this is not a 'feature' since integration is a function of values and time. So excluding time completely and keeping the same value until the source sensor value changes means that this integration is only half-implemented. I've tried forcing update of the base sensor and the integral itself through an automation but it didn't change anything. The only 'solution' is to insert some fakes into the sensor value stream time to time. But that makes the original sensor history look ugly.

[dgomes]

The current implementation is event driven to support sensors that update often (which is also when Riemann Sum best approaches the integral function). You are requesting a new feature because it requires a completely new implementation that is based on periodic polling of the source sensor. It's not that it can't be done, it's just that it isn't a bug...

[rgb-Argentum]

I know that the current implementation is based only on sensor update. But that is not exactly true: HASS doesn't broadcast any updates if the new value of the sensor is the same as the previous. That means the current implementation is practically changes only when the sensor value changes and not when the updates received from the sensor device. So the integration should also include an (optional, configurable) timer that periodically updates the integration value based on the last value and the time elapsed since that moment. There is no need to check or poll the sensor.

[kaijk]

My rain gauge sends a new reading every 10 minutes with 0.01 inch resolution. When its raining, successive values are often the same: 0.01, 0.01, 0.02,. 0.02, etc. This wreaked havoc with HA. It missed all the new, valid, values that happened to be the same value as the last value. Each new value is cumulative, not a repeat of the current state if unchanged from the prior. I solved this by adding a small +/- random lambda value to each incoming data point.

This doesn't guarantee that two identical 10 minute readings will not also get identical random adders, but, good enough for me. So, until another solution arises, here's mine.

The command assures that the new data are no more than a minute old so stale data does not get interpreted as new.

In the if else block. I add both positive and negative lambdas to even it out around zero over time, and never add a lambda when the new reading is zero:

- platform: command_line
  name: 'Acurite 10-Min Rainfall'
  command: "[[ $((`date +%s` - `date +%s -r '/config/externaldata/acuriteweatherdata.txt'`)) -le 60 ]] && cat /config/externaldata/acuriteweatherdata.txt || echo '0,0,0,0,0,0,0,0,0,0,0,0,0,0,0.0' "
  # Add a small lambda to try to keep successive values unique so the Utility Meter will add each value to the sum.
  value_template:  >-
    {% set val = ( value.split( ',' )[14] | float(0.0) ) | round(2) %}
    {% if val == 0.0 %}
       0.0
    {% else %}
       {{ ( val  + ( [ 0.0, -0.000001, 0.000001, -0.000002, 0.000002, -0.000003, 0.000003, -0.000004, 0.000004, -0.000005, 0.000005, -0.000006, 0.000006, -0.000007, 0.000007, -0.000008, 0.000008, -0.000009, 0.000009, -0.000010, 0.000010,-0.000011, 0.000011, -0.000012, 0.000012, -0.000013, 0.000013, -0.000014, 0.000014, -0.000015, 0.000015  ] | random ) ) | round(6)  }}
    {% endif %}
  unit_of_measurement: 'in'

[dgomes]

To possibly address the lack of updates in some sources, I've created a Helper integration: https://github.com/dgomes/ha_sampler

If you run the source through this custom helper, and then use this custom helper as the source of Riemann Integration, you should get better results.

PLEASE: don't create issues or reply to this thread about this custom_component, use the GitHub repository of the custom_component!

[thecem]

So what is the solution to fix this? to add a helper for a helper?

[dgomes]

The sampler helper is a stop gap for some use-cases.

I don't even know the real impact.

If any of you is testing/using, feedback would be nice.

[kaijk]

I don't see ha_sampler in either Integrations or HACS. I'm on 2023.4, though, if it was included later

…

On Mon, Jun 5, 2023, 12:00 PM Diogo Gomes ***@***.***> wrote: The *sampler* helper is a stop gap for some use-cases. I don't even know the real impact. If any of you is testing/using, feedback would be nice. — Reply to this email directly, view it on GitHub <#88940 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL2THYV4SDXVL36S2OKECNLXJYUFZANCNFSM6AAAAAAVLL4TF4> . You are receiving this because you commented.Message ID: ***@***.***>

[dgomes]

it's a trial, it's not part of HACS (although you can use HACS to install it)