v2/crates/homecore-migrate/README.md
Migration tooling for importing Home Assistant filesystem storage into HOMECORE. The implementation follows ADR-165.
.storage JSON and rejects unknown schema versions.homecore::EntityEntry.homecore::DeviceEntry, including identifiers, connections, versions,
serial number, labels, topology, and config-entry links.core.config_entries to a versioned
homecore.config_entries file. Each original row is retained verbatim.
Unsupported domains and non-portable fields produce typed warnings.The import commands take the HA .storage directory and the HOMECORE storage
destination:
homecore-migrate import-entities \
--storage ~/.homeassistant/.storage \
--to ~/.homecore/storage
homecore-migrate import-devices \
--storage ~/.homeassistant/.storage \
--to ~/.homecore/storage
homecore-migrate import-config-entries \
--storage ~/.homeassistant/.storage \
--to ~/.homecore/storage
Successful imports print a machine-readable JSON object:
{"kind":"device_registry","imported":8,"warning_count":0,"warnings":[],"destination":"/home/user/.homecore/storage/core.device_registry"}
inspect, inspect-config-entries, inspect-secrets, and
inspect-automations are read-only.
| Source | Destination | Format |
|---|---|---|
core.entity_registry | core.entity_registry | HA-compatible v1/minor 13 envelope |
core.device_registry | core.device_registry | HA-compatible v1/minor 13 envelope |
core.config_entries | homecore.config_entries | HOMECORE v1/minor 0 envelope |
Config entries are storage-compatible, not runtime-compatible: importing an entry does not install or execute its HA integration. A HOMECORE plugin must explicitly claim the domain and consume the preserved source payload.
automations.yaml.!secret reference resolution in other YAML files is not implemented.cargo test -p homecore-migrate
cargo clippy -p homecore-migrate --all-targets -- -D warnings