Atypical use

[roelanddewindt]

Hi Erwin,
I learned about your custom integration from this discussion, as a possible solution for keeping history when replacing a sensor.
I noticed a previous answer in that thread does this by renaming the new entity to the old entity name to have the history series continues. I don't think that's the right approach for my use case. In fact I want to achieve the opposite.
My case: I'm about 1 year into HA. I feel I made a mess of entity naming. With the new enforced naming mechanism since 2026.4 and finally a customisable one in 2026.8, my OCD tells me to redo device/entity naming from scratch.
I believe your CI could help me merge history of old entities into their renamed counterparts. Could you, or anyone familiar with this CI, confirm whether this would work.
Also, the requirements state minimum 2024.1. Has this CI been validated against current 2026.9.4?
Appreciated.

[mayerwin]

If you only want to rename entities, then you don't need to import anything (and you don't need this tool at all).

[roelanddewindt]

I should give more detail. Currently got some Shellys integrated using Zigbee, feeding into kWh LTS. I want to re-integrate them using native wifi Shelly integration (after flashing their firmware from zigbee to wifi to be able to use BLE proxies, different story). In the process they will get a different name (see my OCD above).
Wouldn't this result in new statistic_id value(s) in table statistiscs_meta, needing to update the metadata_id values in table statistics?
So no a real replacement of the device, but comes down to same thing?

[mayerwin]

If you use a different integration, then the devices and entities will necessarily start from scratch (with a new ID). Then, you can use the tool to migrate your data from the old entities to the new ones, and finally delete your old integration or devices/entities.