Is it possible to have a new sensor take over an old sensors history?

Yesterday (june 7 2023) there was an HA update.
After that update, all ambient weather integrations broke. There are threads on here and on github with people scrambling trying to get things working again.

one of the soutions, if a user has the correct weather station, is to update its firmware to take advantage of the new local api, and the result is that the weather station publishes data directly to HA via a push. This totally works, and I’ve configured my installation in this manner. Now I get local updates, and no more cloud! (woo!)

The hangup is the fact that this procedure creates an entire new integration and every remote sensor in the installation appears as a whole new sensor, along side the old ambientweather integration, which appears to no longer work.

Is there any way to tell home assistant “hey this sensor here is that old sensor there” and have it pick up where it left off? I’m sure I’m not alone in saying I have a staggering amount of scripts, automations, triggers and other stuff relying on these sensors and it would be very helpful to be able to ‘swap out sensors underneath all of that’, so to speak, and also to retain several years of history from them.

The relevant github thread for this is here: https://github.com/home-assistant/core/issues/94205

Manually renaming each of the new sensors to the same Entity ID as the old ones should fix it.

1 Like