Riemann sum stops working if source entity renamed

[michaelblight]

The problem

I wanted to rename some entities to match their function. However, any existing Riemann sum helpers that had these as their source then stopped working. In the screenshot below, I renamed sensor.arlec_s2_power to sensor.microwave_power. However, you can see the Riemann sum below still has a source of the entity before the rename, and so now its value never changes. And there's no way of changing the source for the helper - you have to delete it and create it again.

I'm assuming it's a bug that the only way forward is to delete and start again. Ideally the Riemann source should automatically update if you rename the underlying entity, and you should be able to edit all the Riemann properties after creation.

What version of Home Assistant Core has the issue?

2022.12.0

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

Riemann Sum

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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 Change the title of 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)}}

[dgomes]

I acknowledge the issue, but currently we don't have any mechanism to fix this.

For the time being, it is really up to the user to re-setup the helper with the source new name

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.