Sensor name change caused deleted sensors

[beastien]

As discussed in the SSL certificate thread, I updated to 0.7.3 and the sensor name change applied in version 0.6.0 came into effect late for whatever reason.

I've been keeping up to date with versions as they have been released.

The majority of the old sensors have now disappeared and I've lost all that history (3 years worth).

Did the name change applied in 0.6.0 change the sensor names but carry over the sensor data history?

Would it be possible to roll back to a recent backup with the original sensor names (previous version 0.7.1 I believe) but keep the existing sensor history when I update to the latest version?

[CharlesGillanders]

I really don't have any explanation for what happened with your instance.

You could certainly try restoring a backup and see if you get your history back. If that worked you could also try creating custom names for the sensors before doing another update.

Another thought might be to see if you can find the previous history in the history DB https://www.home-assistant.io/integrations/history/ and perhaps rename the sensor names there to match the actual names?

[beastien]

So I've basically managed to fix the problem.

I restored a backup from a couple of days ago which still used the old sensor names.
I then reverted the integration back to version 0.5.8 and incrementally updated to 0.7.3 just to be safe and it's still retaining the older sensor names but all the history is back.

I believe now though that if I remove the integration and add it again it'll update to the new sensor names and break the history again.

I'm guessing there would be no way to avoid this if I did have to reinstall the integration?

[CharlesGillanders]

Glad you got yourself sorted. I'd be inclined to try manually changing one of the less important sensors to match the new making convention. If that worked you could consider doing it for everything - that would likely protect you if you did need to remove a reinstall at any point.