Expose power & energy usage of VeSync outlets as separate sensors #61837
+215
∄1�723
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.


Breaking change
Previous versions of this integration exposed power and energy usage from VeSync outlets as state attributes on the
switchentity itself. This used the deprecated properties:current_power_wandtoday_energy_kwh. In this version, these two attributes have been removed from theswitchentity and split into two new diagnostic sensor entities that are attached to the same Device. Automations and template entities based on the state attribute mechanism should be updated accordingly.Proposed change
This PR removes the
current_power_wandtoday_energy_kwhstate attributes from VeSync outlets that previously had such attributes and instead exposes them as diagnostic sensor entities on their own. This allows them to be more easily used in the Energy dashboard. Furthermore, this PR adds thedevice_infoproperty to all VeSync entities meaning that each device gets a proper Device registration now.Type of change
Additional information
Checklist
black --fast 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.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests:
The text was updated successfully, but these errors were encountered: