ESPHome 2025.10.x – Memory Type Usage Summary table is gone?

ESPHome
1

Since I think ESPHome version 2025.8.0 we got a nice Memory Type Usage Summary table in the install logs like this:

INFO ESPHome 2025.9.2

Creating ESP32S3 image...
Successfully created ESP32S3 image.
Linking .pioenvs/xs3-04/firmware.elf
                            Memory Type Usage Summary                             
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┓
┃ Memory Type/Section ┃ Used [bytes] ┃ Used [%] ┃ Remain [bytes] ┃ Total [bytes] ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━┩
│ Flash Code          │      1015912 │          │                │               │
│    .text            │      1015912 │          │                │               │
│ Flash Data          │       300808 │          │                │               │
│    .rodata          │       300552 │          │                │               │
│    .appdesc         │          256 │          │                │               │
│ DIRAM               │       138891 │    40.64 │         202869 │        341760 │
│    .text            │        87067 │    25.48 │                │               │
│    .bss             │        32320 │     9.46 │                │               │
│    .data            │        19504 │     5.71 │                │               │
│ IRAM                │        16383 │    99.99 │              1 │         16384 │
│    .text            │        15356 │    93.73 │                │               │
│    .vectors         │         1027 │     6.27 │                │               │
└─────────────────────┴──────────────┴──────────┴────────────────┴───────────────┘
Total image size: 1439674 bytes (.bin may be padded larger)
Note: The reported total sizes may be smaller than those in the technical reference manual due to reserved memory and application configuration. The total flash size available for the application is not included by default, as it cannot be reliably determined due to the presence of other data like the bootloader, partition table, and application partition size.
RAM:   [==        ]  15.8% (used 51824 bytes from 327680 bytes)
Flash: [====      ]  36.6% (used 1439418 bytes from 3932160 bytes)

But since probably ESPHome version 2025.10.0 (confirmed with version 2025.10.2) this table is replaced with this:

INFO ESPHome 2025.10.2

Creating ESP32S3 image...
Successfully created ESP32S3 image.
Linking .pioenvs/xs3-04/firmware.elf
usage: esp_idf_size [-h] [--format {table,text,tree,csv,json2,raw,dot}]
                    [--archives] [--archive-dependencies] [--dep-symbols]
                    [--dep-reverse] [--archive-details ARCHIVE_NAME] [--files]
                    [--diff MAP_FILE] [--no-abbrev] [--unify] [--show-unused]
                    [--show-unchanged] [--use-flash-size] [--lto] [-d]
                    [-o OUTPUT_FILE] [-s COLUMN] [-F PATTERN] [--sort-diff]
                    [--sort-reverse] [-q] [--no-color] [--force-terminal]
                    [--doc]
                    MAP_FILE
RAM:   [==        ]  15.4% (used 50520 bytes from 327680 bytes)
Flash: [====      ]  36.5% (used 1435814 bytes from 3932160 bytes)

It looks like this is a bug?
Or is this an intentional change?
Who knows more about this?

2

I was curious as well after noticing the same.

3

I did some searching, and now understand it better.
ESPHome appears to be using the ESP-IDF Size Tool, which can create the Memory Type Usage Summary table with the esp_idf_size --format option.

And it appears that there is a new version v2.0.0 of this ESP-IDF Size Tool released by Espressif that has a breaking change: the –ng flag has been redrawn because it is not needed any more to create the table.
And apparently ESPHome does not take this into account yet, causing this issue.
It will be solved in ESPHome version 2025.11.0, as stated in esp_idf_size: error: unrecognized arguments: --ng #10978