mirror of
https://github.com/esphome/esphome.git
synced 2026-09-16 01:28:39 +00:00
J. Nick Koston
1f9afebbf5
When the running app does not fit any slot in the new partition table, the user has almost certainly picked the wrong migration .bin for their device. Replace the generic "No compatible app partition found" error with one that prints the running app's offset, used size, and the size limit a migration method must clear, plus an explicit reassurance that no flash content has been modified yet. Same treatment for the otadata-overlap case: include the running app offset/size and tell the user to pick a different migration method. Verification phase is non-destructive, so these errors are recoverable by retrying with the correct .bin -- the new wording makes that explicit so users don't lose time on a brick scare they aren't in. No code-flow change; only log message wording.
