I as home owner, who is very invested in energy monitoring would want my energy data be persistent within home assistant, so all data stays available, even though a single sensor integration changes, or a sensor needs replacement. → Therefore when ever I add a sensor to the energy dashboard as a v…

I think you have two options here to solve the problem. One is cleaner. Delete the old entity and rename the new entity to match the old one. HA will automatically fix things so the new entity has all of the old entity’s historical data. If it was for a single device and not your whole home energy…

I agree with this WTH I used this integration once . It worked. But I don’t consider this very user friendly :slight_smile:

Using device ids makes a mess and cause these exact situations which is why many on the forum warns users against them. Using entity ids makes it much easier. [image] Why and how to avoid device_ids in automations and scripts Community Guides Background When you start w…

[image] richie510: If you go with route #1, you can then just re-add the Shelly CT and give it a new name to start a new set of statistics for it. How do you achieve this @richie510 ? I have been trying this approach for the last 3 hours with a Tasmota smart plug and it’s driving me absolutel…

That sounds like a device id have been used instead of an entity id.

Your experience does not match my experience. Maybe show us some screenshots. Maybe WallyR is on to something with the device ID stuff. I have never used tasmoda, maybe it has some weird shenanigans going on. If you get weird spikes in your energy history, you can go to developer tools → statistics…

Id love this, some kind of “replace with” for sensors of the same type for the historical data to continue when you change or replace sensors. It feels “safer” than tricking the system by deleting sensors and adding new ones with the same name :slight_smile:

The problem with device ids is that they are somehow generated from the device info, so they can not be “replaced with”. Entity ids can and that is the way to do it, al though this is a manual, but simple process and allows replacement with entities that are not always 1:1.

If I could specify multiple energy sources per device with validity periods (from - to date), this would solve most use cases. Instead of adding entirely new devices when hardware changes, you would: Keep the same logical device in the energy dashboard Add a new energy source to that device with …

I worked around this issue by disabling old integration and keeping old entity in dashboard as power supply. This way no new data go to this entity but it still provide statistics.

WTH: I loose all energy data history if I need to change a energy entity

Month of "What the heck?!"

WallyR (Wally) December 13, 2024, 12:52am 4

Using device ids makes a mess and cause these exact situations which is why many on the forum warns users against them.
Using entity ids makes it much easier.