I suspect my neotrellis_keypad ESPHome External Component project (Arduino platform) has been broken by the 2025.10.0 release and the “Arduino as IDF Component” breaking change. It compiles and uploads OK but then just goes unresponsive and unable to connect. No Logger output. A simple YAML project just to access the onboard neopixel and LED works and demonstrates the adafruit_feather_esp32_v2 is functioning fine. So the likely culprit is my external component supporting the neotrellis. This relies heavily on the “Adafruit Seesaw” libraries, which I understand may not be compatible with the ESP-IDF platform. (I don’t know the details as to why.) Likely somewhere in the initialization of the component it’s crashed or looped. It certainly worked well before! So I’m wondering if this huge platform change has tried to accommodate these libraries (and failed?) or if they’re just a sacrifice to the path of progress. Any suggestions on how to recover this device and functionality, or if it’s even possible, would be greatly appreciated.
Maybe if you post your yaml we can understand the components that you think are causing the issue?
There are a lot of external components that are still working after that update so the more info we have the easier to diagnose.
The entire ESPHome device YAML and external component C code is in the project linked to in the very first line in my post.