Move sensor to new location while keeping the database integrity

[samuelg (Samuel)]

Okay, I digged a little bit deeper and did find some threads with equivalent problems.

The solution should be:

@wigster

So it seems that the LTS and the recent “recorder” history are only connected through the entity_id of the sensor.

So what you have to do:

• Rename the sensor to what you want it to be in the future, “name1”. This will tie the statistics to the new name
• Remove the device, restart
• The entities are now dead. Delete them. This will retain the LTS orphaned until you go to dev tools/stats and “fix” them. So don’t do that.
• Add your new device and rename the sensor to name1. The LTS will not know there was a change of device reporting. But be careful about units of measurement etc.

Seems to have worked for me as fat as I can tell.

Unfortunately I already renamed the old entity ID and named the new one after the old one, now the LTS is gone. But InfluxDB has me covered, as far as I can tell.

For reference the threads with proposed solutions:

Migrate LTS history to replacement sensor

Did you manage to find an answer to this question ?

Replace the broken sensor

Hi there my temperature sensors was broken, I want replace it. however the entity id is different therefore I just can not like the new record with the old history. I tried to change the entity id but the system is showing the id is already there. Dose any body know how to do the replacement?