New sensor, same measurement, continous history

Hello,

one of my temperature/humidity sensor (BLE) is dead and I need to replace it. The entities are currently called:

  • sensor.atc_1715_humidity
  • sensor.atc_1715_temperature

If I connect a new sensor, it will have a need ID, with a new history. Is there a way to have a continuous history instead?
I have read some methods involving renaming entities and such, but it sounds like hacks and I was wondering if there is a more elegant way, something like defining virtual entities that can combine the historical data.

Thanks!

You can use this integration: [Guide] Migrate / copy energy statistics & history to new entity - keep full history in Energy Dashboard (2026) - #9 by ErwinHA

It’s called Merge Sensor History.

Or just remove the old sensor and replace it with a new sensor that has the same entity_id.
Not a hack, it’s the official way to continue a sensor.

What he said^^

Read here Adding new devices and replacing devices

Thank you all for the quick feedback. Indeed renaming the new entities to the old names was the easiest solution in the end. The only drawback is that this name is based on the old sensor hardware, but I can live with that.

Now I have the problem that the data is wrong between the time when the old sensor broke and the new one was in place:

I found this to fix it:

But I was wondering if there is a way without installing a new component?

The entity_id has to match, but you can change the name that the item shows to the user to what you want (if that helps)…