Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

About

Merge Sensor History imports historical sensor data from one entity into another in Home Assistant. It is meant for migrating data between integrations, such as replacing one integration with another so the new sensors carry the old sensors' history. It adds a sidebar panel, shown only to administrators, where source and destination pairs are chosen, either entity by entity or by picking an old and a new device whose entities are matched for review. Both recorded states and long-term statistics are imported, so periods whose raw states were already purged are still covered. Only source states older than the destination's oldest good entry are written, and the import is committed in a single transaction, so it can be re-run safely. An optional overwrite mode exists for destinations with bad data, and a service allows imports from automations. It works locally and is set up in the UI.

Automatic summary of the README of mayerwin/HA-Merge-Sensor-History. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

  • Works locally Talks to your devices on your own network. No vendor cloud in between.

  • From the Marketplace Installed through the Marketplace, formerly HACS.

  • Actively maintained Its author released or pushed a change in the last six months.

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

From the README

A Home Assistant custom component to import historical sensor data from one entity into another.

Built for migrating sensor data between integrations — for example, when replacing an Ecowitt integration with a different one and you want the new sensors to carry the old sensors' history.

  • Sidebar panel with a simple UI: select source/destination pairs, click Import
  • Imports both states and long-term statistics (hourly aggregates for energy dashboard / long-term graphs)
  • Atomic: an import is written in a single transaction, at any size, so either all of it lands or none of it does
  • Never blocks the recorder: the write goes through Home Assistant's own recorder queue, so it cannot lock the recorder out of its database
  • Idempotent: safe to re-run; a successful import shifts the cutoff so nothing is re-imported
  • Optional overwrite mode for destinations holding known-bad data (opt-in, destructive, clearly warned)
  • Entity filter to quickly find sensors by keyword
  • Pick by device: choose an old and a new device, and every entity of the old one is matched to one of the new one's, for you to check before importing
  • Also available as a service (merge_sensor_history.import_history) for use in automations or Developer Tools
  • HACS compatible
From the README of mayerwin/HA-Merge-Sensor-History, MIT License. Shortened.

Information

Installs
345 sharing analytics
GitHub stars
71
Connection
Works locally
Upkeep
Updated in the last 6 months
Version
v1.4.2,
Category
Sensors
Kind
Marketplace integration
Needs
Needs the Marketplace (HACS on 2026.10 and older)
Domain
merge_sensor_history

You might also like

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. About these numbers