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.
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: