ESPHome 2026.4.0 beta - packages & Config Bundle for Remote Compilation

ESPHome
1

Hello,

I’ve just noticed the Config Bundle for Remote Compilation feature coming in ESPHome 2026.4.0 and am rather exited :slight_smile:

However, I am finding it does not include all local config and secrets required to build the bundle remotely.

I’m not sure where best to report this issue with a beta release, so will post here.

Using the latest docker dev version, I have created a new, default device:

esphome:
name: test
friendly_name: test
esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: esp-idf

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "redacted"
  ota:
    - platform: esphome
      password: "redacted"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

When I do esphome bundle test-default.yaml inside the docker container this creates a .esphomebundle.tar.gz with two files in it - the test-default.yaml and the secrets file as expected.

However, when including the wifi configuration via a package, neither the secrets file or common/wifi.yaml are added to the .esphomebundle.tar.gz.

packages:
  - !include common/wifi.yaml

I assume this is not by design as the documentation states that the bundle includes “all !included YAML files and secrets.yaml”.

Any suggestions as I use the local packages pattern extensively for common config?

2

I see that ESPHome 2026.4.0 has been released since I posted.
The same problem occurs.

3

It looks like [substitutions] `!include ${filename}`, Substitutions in include filename paths (package refactor part 5) by jpeletier · Pull Request #12213 · esphome/esphome · GitHub broke the bundle system from discovering included files.

4
5

Thanks very much for looking into that so quickly. :clap:t2:

I’ll keep and eye out for the PR to be merged and released into dev and give it another try and will feedback my experience here.

Cheers,

Steve

6

I see that this PR has been merged into today’s ESPHome 2026.4.1 release.

I’ve tested creating bundles with includes and it all seems to be working as expected.

I’m able to create bundles, copy them to another machine and build (and deploy them) them on the remote machine using just the .esphomebundle.tar.gz file.

Cheers,

Steve