Skip to content

Unintended sideeffect of PR 148731: LTS gets renamed and energy history in dashboard wrong #150376

@EDelsman

Description

@EDelsman

The problem

When you rename an entity, previously statistics were not renamed. Now they are. But the statistics belong to the role the device had, not to the measuring device itself. So now when one repurposes a smartplug to do something else, the energy history looks like what the device was used for before that. It used to be that one could simply rename the entity of the new plug to the old name and inherit history, but that is no longer so. The energy dashbord history is now broken, because it implies energy use for the wrong appliance. There is no way to fix it.

Please make it as it was before: the statistics are bound to the old entity_id forever. Or at least give a user a choice to rename LTS or not. When you give a new entity that entity_id, let it inherit the original statistics again so you can replace an energy sensing plug and keep history for what is plugged in it. This does not just apply to sockets. Even a smart light: when a bulb is moved to another place, the purpose changes. I want to know how the costs for the purpose, not for the bulb.

These are graphs of power and energy sensors with statistics and recorder data. On the right a tiny bit of the values recorded when the item was renamed and repurposed. Everything is listed under the new entity_id and name. It used to be a NAS, UPS, router and other devices. Now it is used for a bike charger. There is currently no way I can make this look right in energy history. A bike charger does not use 70W for 24/7.

Image

It is believed this PR is causing the new behavior unintendedly: #148731

What version of Home Assistant Core has the issue?

core-2025.8.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

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions