Reading your verification report
What each section means, why a few entities are always missing at first, and what to do about each kind of integration failure.
Updated 19 August 2026 migrationtroubleshooting
After any restore, VomeHome compares what came back against what your backup said it held, and shows you the difference. A verdict of needs attention is common and usually has ordinary causes.
What each section means
| Section | What it means |
|---|---|
| Version | The restored Home Assistant matches the backup's version. A restore can move Core backwards to match. |
| Entities | A small shortfall shortly after a restore is normal — disabled devices, or integrations still starting. |
| Automations, scripts, scenes, areas | These should match exactly. A shortfall here is worth investigating. |
| Devices | Often lower than the source when integrations have not loaded. Check integrations first. |
| Integrations | Anything that did not load, grouped by what you can do about it. |
| Error log | Errors since the restore. Some noise during start-up is expected. |
Integrations are grouped by cause
Because the useful question is not which failed, but whose problem is it:
- Needs signing in again — the restore replaced the stored credentials, so cloud services no longer recognise the saved token. Re-authenticate them in Settings → Devices & services.
- Needs local network discovery — these find their devices by broadcasting on the local network, which does not cross a routed connection. See when devices are not discovered.
- Device did not answer — the address is known and nothing replied. Usually something switched off or asleep.
- Did not start — no reason given, which normally means disabled or missing a dependency.
Running both systems at once will skew the numbers
Devices that accept one connection at a time — ESPHome among them — can only talk to one Home Assistant. If your old system is still running, expect entities to look unavailable on the new one. Shut the old one down before judging the report.
For agents and scripts
The whole report is available as JSON, including a named list of actions with a reason and suggested fix for each group:
GET /api/server/<server-id>/migrate/report
People who run Home Assistant tend to have scripts and assistants of their own. Making them scrape a page for facts we already hold would be a strange way to treat them.