ESPHome Warning ESPTouch November Release

After compiling for the last couple of times for the November Release of ESPHome, I noticed that I continue to get this warning.

In file included from src/esphome/components/esp32_touch/esp32_touch.h:11,
                 from src/esphome/components/esp32_touch/esp32_touch_common.cpp:3:
/data/cache/platformio/packages/framework-espidf/components/driver/touch_sensor/esp32/include/driver/touch_sensor.h:13:2: warning: #warning "This set of Touch APIs has been deprecated, please include 'driver/touch_sens.h' instead. if you want to keep using the old APIs and ignore this warning, you can enable 'Suppress legacy driver deprecated warning' option under 'Touch Configuration' menu in Kconfig" [-Wcpp]
   13 | #warning "This set of Touch APIs has been deprecated, \
      |  ^~~~~~~
Compiling .pioenvs/f

Any work around on this? Will it get updated automatically?

1 Like

Anyone else have this issue?

1 Like

Yes, I just encountered this warning while rebuilding a device today.
Also “The legacy RMT driver is deprecated, please use driver/rmt_tx.h and/or driver/rmt_rx.h”

Does anyone know if this is going to be resolved in future ESPhome updates or is this something manually we need to change?

Appreciate the feedback and yes that is for a light

The version I am getting is dealing with the touch sensor.

Here is my yaml:

binary_sensor:
  - platform: esp32_touch
    name: "Water Sensor Pin15"
    pin: 15
    threshold: 100

For now, it’s a warning, but eventually it’ll need to be fixed in the ESPHome code base. You can report it here if you’re up for it, I couldn’t find any existing issues for it.

1 Like

Ok now it is at the point where the touch sensor is blocking the update for ESPHOME v2025.12.2 . Can anyone assist?

Here is error:

In file included from src/esphome/components/esp32_touch/esp32_touch.h:11,
                 from src/esphome.h:32,
                 from src/main.cpp:3:
/data/cache/platformio/packages/framework-espidf/components/driver/touch_sensor/esp32/include/driver/touch_sensor.h:13:2: warning: #warning "This set of Touch APIs has been deprecated, please include 'driver/touch_sens.h' instead. if you want to keep using the old APIs and ignore this warning, you can enable 'Suppress legacy driver deprecated warning' option under 'Touch Configuration' menu in Kconfig" [-Wcpp]
   13 | #warning "This set of Touch APIs has been deprecated, \
      |  ^~~~~~~
xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/aquariumsensor/src/main.cpp.o] Error 1
======================== [FAILED] Took 1037.50 seconds ========================

I have posted it online here:
https://github.com/esphome/esphome/issues/12323

The warning is not an error, it is a warning (that at some point in the future will be an error, if not addressed before then).

The error you are seeing is not well described (by the message). It is likely because you are using an underpowered device to do the compilation. What are you running esphome on?

1 Like

The help forum for ESPHome is saying that it is an error that I am running out of memory. Attempting to shorten the size of my install now.

Let me guess, a raspberry pi with only 1MB of RAM?

You can set the compile limit to one core and it will take longer but might actually work.

Or, you can install esphome on a more powerful computer.

While compiling, I have confirmed
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash

I will try your suggestion this morning.

The question was what is the hardware of the machine you are compiling on. You provided the specs of what you are compiling for (the target of the cross compilation).

I have not heard of anyone compiling esp32 code on an esp32 itself. Anything is possible with enough effort, but I certainly wouldn’t want to wait for it to finish.

Sounds good, I am assuming you are asking what device my home assistant is running off of. I have a home assistant yellow with 2GB of memory. It’s averaging around 1.3 GB of runtime (+/- 70%). I am hoping that is what you are asking for.

Post the full yaml code you are attempting to compile. Post the compile log. [Formatted for forum purposes </> please]

Well that has a CM4 in it, which is better than an rpi 3 (or 2). I found this benchmark

This not bad for its class with a multi core performance of 538.

But, I am using an old 1L size PC that has an Intel i7-9700T. This is a 5+ year old CPU. Its benchmark is here: https://browser.geekbench.com/processors/intel-core-i7-9700t
Its multi-core performance is 5204, almost 10X

This is why I run esphome on it instead of on my HA machine. It is running on a different (even older) PC that is probably still 5X the CM4.

If you want to keep running on the CM4, it is probably a good idea to limit the compile processes using:
compile_process_limit

I recently installed music assistant and I have a feeling it was bogging performance down. So I have un-installed that app and I am starting to get some of the devices to compile. There is one that I am having issues with that I will continue to work on. It is the one with the touch sensor above.

Since my system is growing steadily, I am going to upgrade to a Raspberry pi CM5 with 8 GB of memory. It seems to be the best available on the market at the moment for my Raspberry pi yellow. Appreciate your troubleshooting.

You might want to read this thread:
https://www.reddit.com/r/homeassistant/comments/15mi4tq/thoughts_on_home_assistant_yellow_vs_other/

The Raspberry Pi is great for things where you need a little bit of compute and more IO, especially GPIO. But, if you need more compute it gets more expensive quickly.

Used mini PCs have a much better cost for things that need more compute and can still have a low cost for power used.

If your major complaint is compiling for esphome, just do that on your PC/Mac and not on your HA machine. When you outgrow the CM4 for HA, move it to a VM or Docker container running on a decent mini PC from a few years ago.