ESPHome takes control of devices whose firmware spans several files

Taking control of an ESPHome device can fail when its maker spreads the firmware configuration across several files. Device Builder imports those files as a package when a single-file import cannot preserve them, and ESPHome finds supporting assets beside the configuration that names them.

J. Nick Koston verified the changes with the NeatoFx speaker: its configuration could fail during import or report a missing custom interface file even though that file existed in the maker’s repository. The package import preserves the links between those files.

Files in the user’s own configuration folder still take precedence when both locations contain a match. The change supports configurations that include other files without requiring the maker to flatten them into one.