"turn_on_action"/"turn_off_action" as Switch Core functionality

[Masterz69]

Component name

switch

Link to component documentation on our website

https://esphome.io/components/switch/

Describe the enhancement

Currently "turn_on_action"/"turn_off_action" only available for Template Switch.
Asking to provide that fucntionality as a Core Switch functionality.

Use cases

To trigger whatvere required actions on ESPHome side when UI (like HA) requests to change switch state, regardless of it's current state and followinf state change. F.e. if need to restart a running script when state change requsted by UI (HA or Web).

Anything else?

No response

[github-actions[bot]]

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

[ssieb]

There is the on_turn_on action. The turn_on_action is only useful for the template switch when it's not optimistic. This doesn't apply to others.

[Masterz69]

There is the on_turn_on action. The turn_on_action is only useful for the template switch when it's not optimistic. This doesn't apply to others.

Using turn_on_action in optimistic mode.
Have a script started by on_turn_on. Script have mode restart.
When calling service switch.turn_on from HA I assume it triggers script restart.

In other words: ability to perform some actions when received request from UI to switch on f.e. even if switch already in on state.
And I see it useful for me not only for Template Switch.

switch:      
  - platform: template
    name: TEST
    id: switch_test
    internal: False
    optimistic: True

    turn_on_action:
      - if:
          condition:
            - script.is_running: script_TEST
          then:
            - script.execute:    script_TEST

    on_turn_on:
          - script.execute: script_TEST

script:
  - id: script_TEST
    mode: restart
    then:

[ssieb]

In other words: ability to perform some actions when received request from UI to switch on f.e. even if switch already in on state.

How is that even possible? If that's happening, it's a bug in the ui.

[Masterz69]

In other words: ability to perform some actions when received request from UI to switch on f.e. even if switch already in on state.

How is that even possible? If that's happening, it's a bug in the ui.

Just confirmed - when using switch.turn_on service HA passes command turn_on to ESPHome device regardless on switch state.
Executed twice with ~7 second interval as seen below.

[20:40:30.798][D][api.connection:1398]: Home Assistant 2025.12.3 (192.168.1.11) connected
[20:40:43.078][D][switch:022]: 'Garland Hall' Turning ON.
[20:40:43.082][D][switch:065]: 'Garland Hall': Sending state ON
[20:40:43.082][D][main:241]: pulse_1_delay started
[20:40:50.922][D][switch:022]: 'Garland Hall' Turning ON.
[20:40:50.925][D][script:090]: Script 'pulse_1_delay' restarting (mode: restart)
[20:40:50.926][D][main:241]: pulse_1_delay started

Script was restarted on second turn_on command.
IMHO it is a nice feature and I have usage for it.

[Masterz69]

In other words: ability to perform some actions when received request from UI to switch on f.e. even if switch already in on state.

How is that even possible? If that's happening, it's a bug in the ui.

You right, not from GUI, but from HA automations, scripts.

One of usages for this feature see following.
Motion sensor by HA automation triggers switch to on, then starting script which will turn it off after some delay.
But if/when motion detected while switch is still on - script going to be restarted and delay prolonged.

Sorry my English, not native one.