Repository navigation
v1.2.17 - Merge recent raw states blocked by hidden unavailable rows
Fix
Recent raw states no longer blocked by hidden unavailable rows
The states import only brings in data older than the destination's oldest entry, to avoid duplicates. Until now that cutoff counted every stored row, including hidden unavailable/unknown markers that Home Assistant never shows in the History panel. If the destination entity id had existed before (for example as a leftover ghost entity logging an unavailable marker at every restart), those invisible rows silently blocked the import of the source's recent raw states: long-term statistics came through, but the recorder window stayed empty.
The cutoff is now the destination's oldest good (visible) entry. Hidden rows no longer count as coverage, and exact-timestamp duplicates are still skipped, so imports remain idempotent. If a previous merge left the recent period empty, update and run the same pair again: the missing states are imported as long as they are still within your recorder retention (states age out daily, so do this soon).
Reported on the community forum, thank you!
Improvements
Disabled entities as sources
The Show deleted entities toggle is now Show deleted/disabled entities. It lists every entity with no live state, using the entity registry to tag each one:
[deleted, statistics only]: gone from Home Assistant; only hourly statistics remain.[disabled]/[not loaded]: still registered; their recent raw states are merged too, while those remain within your recorder retention.
Registered entities without any statistics (raw states only) are now listed as well, so a disabled sensor that never had long-term statistics can still be merged.
Panel polish
- When states are skipped because they fall inside the destination's existing range, the results now point to the gap-fill option (with a Preview) as the way to inspect and import them.
- Friendly names containing
<,>or&now display correctly in dropdowns and results. - README: documented that the source entity is never modified, with cleanup guidance once a merge is verified (delete the old entity, optionally run
recorder.purge_entities).