Add migration for old HomeWizard sensors #105251
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
This migrates
total_power_*_t1_kwh
tototal_power_*_kwh
, whentotal_power_*_kwh
does not exists. This solves an issue where users can't access long-term storage data for the HomeWizard Energy Socket.The problem;
total_power_*_kwh
sensor, only atotal_power_*_t1_kwh
sensor. Thetotal_power_*_kwh
has been added.This does not fix the issue when the user already has installed 2023.12, because the new sensor is already created. The data is not lost, but can't be accessed. We have to find another solution for that.
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: