Support multiple pins in deep_sleep component on ESP32 Cxx variants.

[dimarobert]

Component name

deep_sleep

Link to component documentation on our website

https://esphome.io/components/deep_sleep/

Describe the enhancement

Currently, the component only supports one wakeup_pin for ESP32 C2, C3, C6, C61, while they also support multiple pins through a pin mask.

Use cases

This would increase the feature parity to some extent between the different variants. Any multi-pin deep_sleep use cases that make sense for the other variants would make sense for the ones specified above as well.

Anything else?

This all started with a custom 2 button remote that I built using an ESP32-C3 for which I wanted both buttons to wake it up from deep sleep. I created a custom component for myself, starting with the code from the core component, that I have in use for close to 1 year. To make it easier to keep it up to date with upstream changes I made my custom multiple pins support using completely separate configuration entries. You can see this version of the implementation in this commit.

When I noticed the recent changes to the core component to support a list of pins in the wakeup_pin for the BK72XX (and at the same time the refactoring that took place a while back that better separated code between esp32 variants) I thought it would be a good time to also bring up this feature improvement request and at the same time provide the implementation I have as a POC.

I've also kindly asked ClaudeCode to try to merge my changes to use the existing configuration entries and also ensure code parity with the core implementation. Here is the result after a few additional manual cleanup passes.

Few things to note:

• as stated, I only tested on the ESP32-C3 and confirmed it works, but docs state that mask is supported on all C2, C3, C6, and C61 (with the note that C61 docs state that they are not updated for ESP32C61 yet, so some of the content may not be correct)
• one aspect that cannot be easily transferred from one pin to multiple pin wakeup is the WAKEUP_PIN_MODE coupled with the level calculation.
  • IGNORE and KEEP_AWAKE make sense as per-pin settings with multiple wakeup pins:
    • IGNORE: Enter deep sleep regardless of whether this pin is already in the wake state. This is the natural default.
    • KEEP_AWAKE: If this specific pin is already in its wake state, defer entering deep sleep until it changes. Each pin can independently prevent sleep.
  • A global WAKEUP_PIN_MODE does not translate well to multiple pins, e.g. a global KEEP_AWAKE would mean "keep awake if any pin is active," but you may only want that behavior for some pins.
  • INVERT_WAKEUP does not work with multiple pins at all, neither per-pin nor globally. The purpose of INVERT_WAKEUP on a single pin is: "if the pin is already in the wake state, flip the wake level so the device actually enters sleep and wakes on the next transition." With the GPIO wakeup API (esp_deep_sleep_enable_gpio_wakeup), a single esp_deepsleep_gpio_wake_up_mode_t level is applied to all pins in the mask. If one pin needs its level inverted while another doesn't, there is no way to represent that, the API simply doesn't support per-pin levels. Even applying INVERT_WAKEUP globally (flip the shared level if any pin is active) would break the semantics for the pins that aren't currently in their wake state.
• I noticed that based on the code that ClaudeCode generated that there might be some edge cases that my initial implementation did not cover (e.g. making sure GPIO pins are set as INPUT by calling gpio_set_direction(gpio_pin, GPIO_MODE_INPUT) on each one).

[github-actions[bot]]

🏷️ I've automatically added the component: deep_sleep label to help categorize this feature request.