dydx
December 13, 2022, 12:42am
1
I collected proud statistics over my power consumption over the past months. I used “sensor.kWh” that was exposed by my Emporia Vue Utility Connect.
Today I got solar so I changed the the grid entity to “sensor.kWh_consumed” and the Return to Grid to “sensor.kWh_returned” *that was previously unused).
Now I shockingly see all my previous energy data is gone!!
Is there a way to get it back?
123
(Taras)
December 13, 2022, 1:31am
2
Prior to version 2022.10.0, renaming an entity would effectively dissociate the renamed entity from its long-term statistics (i.e. such as energy data). See the comment in the following post:
Hi,
It would be nice if we would merge entities in the statistics database. When you for instance rename an entity or replace a sensor, it would be nice if the data from the old sensor could be merged with the new sensor. For instance, in my energy dashboard I now have two sensor for my solar panel production since I started using a different integration to monitor my panels, it would be great if I could merge that into one.
In version 2022.10.0, the following enhancement was designed to preserve the entity’s long-term statistics.
home-assistant:dev
← home-assistant:recorder_fix_startup
opened 07:54PM - 03 Oct 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Correct recorder startup to ensure long term statistics is preserved when entity_id is changed via the UI
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
If you are using a recent version of Home Assistant, renamed the entity via the UI, and it still failed to preserve long-term statistics, report it as an Issue in the GitHub Core repository.
dydx
December 13, 2022, 1:51am
3
Thank you!
I am not sure if I understand correctly – I actually did not rename anything. I just changed the entity that I use for “Grid Consumption”.
I am on 2022.12, so the patch should work.
Or are you suggesting renaming “sensor.kwh” to “sensor.kwh_old_unsed” and “sensor.kwh_consumed” to “sensor.kwh” and use it for “Grid Consumption”?
EDIT: Let me clarify further: The Vue Utility Connect in its normal configuration provided a sensor “sensor.kwh”. Since this doesn’t perfectly capture the consumption when power is sent back to the grid, there is an alternative configuration for solar. In this config, it provides “sensor.kwh”, “sensor.kwh_consumed” and “sensor.kwh_returned”. In my understanding, the latter two should be used now.
123
(Taras)
December 13, 2022, 2:11am
4
My apologies, I misread your post and thought you had renamed sensor.kwh
.
From what I read… changing from one entity to another indeed does not retain the history. Or did you add the new entity next to the ‘old’ one? If you only have one sensor now, then you can try to retrieve the history via the db, i.e. copy from old to new entity.