Automation/blueprint for using switch to go on for a certain period

I am using the Danielbook/motion-illuminance.yaml blueprint

I am using this blueprint for two different scenes.
The first one is working the second won’t work.
I think it has something to do due to the fact that the first one is switching only “ligths” were the second one is switching a “switch” with after that a light bulb.
Can somebody what is wrong with the secopnd automation?

  alias: Licht gang beneden aan voor 50 seconden en onder de 50 lux op de lichtsensor
    (nieuw)
  description: ''
  use_blueprint:
    path: Danielbook/motion-illuminance.yaml
    input:
      motion_entity: binary_sensor.0x00158d0006d45afd_occupancy
      lux_entity: sensor.0x54ef4410000a2e0e_illuminance_lux
      lux_level: 50
      no_motion_wait: 45
      light_target:
        device_id:
        - 480f181eb5d8ae688a519c078e68365a
        - 2c9cf1a29a35e01a64d5bb846ceb568f```

```- id: '1640206849680'
  alias: Licht keuken aan voor 50 seconden en onder de 50 lux op de lichtsensor (nieuw)
    ben ik nu aan het testen
  description: ''
  use_blueprint:
    path: Danielbook/motion-illuminance.yaml
    input:
      motion_entity: binary_sensor.0x00158d0006e47dcc_occupancy
      lux_entity: sensor.0x54ef4410000a2e0e_illuminance_lux
      lux_level: 50
      no_motion_wait: 45
      light_target:
        entity_id:
        - switch.keukenlicht_socket_1```

You could try to modify the blueprint by deleting the light domain restriction, otherwise using the blueprint as is you can only command light entities.

Okay. That is something that i can do. Is there a blueprint where i can switch switches instead of lights? :slightly_smiling_face: