Is this Possible

[Edwin_D]

Yes it is. What I do is turn the automation to do it on and off based on my needs using service automation.turn_off and automation.turn_on. But I know others frown upon that way of working because you lose the ability to disable the automation for other reasons.

The advised way is to create an input boolean helper. You can create one in the helper section. You turn the input_boolean on when you turn the light on with the automation you mentioned. The automatic off automation checks if the input_boolean is on to see if action is required, and turns the input boolean off off after it is done.

You can opt to turn the input boolean off when you want some kind of manual override too.

[paulgryan52 (Paul Ryan)]

sorry I’m new to HA, how would I do that

[Edwin_D]

@paulgryan52

turn fan on if it was previously on before light turned on

I can write an example, but I’d have to understand this. Wouldn’t you want to turn it off when it was previously off? I’ll assume the latter:

create an input helper in the Helper section of settings, named Auto fan (You can use another name, but then the entity name changes too in the automation. Automation for off:

alias: Fan off
description: ""
trigger:
  - platform: state
    entity_id: light.dakkapel
    from: "off"
    to: "on"
condition: 
  -  condition: time
     after: "00:30:00"
     before: "10:00:00"
action:
  - if:
      - condition: state
        entity_id: fan.dakkapel
        state: "on"
    then:
      - service: input_boolean.turn_on
        target:
          entity_id: input_boolean.auto_fan
        data: {}
  - service: fan.turn_off
    target:
      entity_id: fan.dakkapel
    data: {}
mode: single

Automation for on:

alias: Fan on
description: ""
trigger:
  - platform: state
    entity_id: light.dakkapel
    from: "on"
    to: "off"
condition:
  - condition: state
    entity_id: input_boolean.auto_fan
    state: "on"
action:
  - service: input_boolean.turn_off
    target:
      entity_id: input_boolean.auto_fan
    data: {}
  - service: fan.turn_on
    target:
      entity_id: fan.dakkapel
    data: {}
mode: single

You should of course replace entity id’s with the ones for your use case.

[stevemann (Stephen Mann (YAML-challenged))]

Go to Developer Tools, States and find your light and switch entity ID’s.
(The UI is supposed to make this step unnecessary, but it makes debugging easier if you know the actual entity IDs).

The state of the light will tell your automation if it’s currently on or off.

We could write it for you, but what fun is that?

[paulgryan52 (Paul Ryan)]

I’ll try to explain more

When

• Light turned on

If

• Fan On
• Time between 00:30-10:00

Then

• Turn Fan off

I’ve already created this automation, I want the following to happen

When

• Light turned off

if

• time between 00:30-09:45

then

• turn fan on (if on before light turned it off)
• do nothing (if off before light turned on)

[Edwin_D]

When you paste code, you heed to place it between three backticks to show properly. Otherwise it is of no use to is. See number 11 in this post:

How to help us help you - or How to ask a good question

Before we begin… This forum is not a helpdesk The people here don’t work for Home Assistant, that’s an open source project. We are volunteering our free time to help others. Not all topics may get an answer, never mind one that helps you solve your problem. [image] This also isn’t a general home automation forum, this is a forum for Home Assistant and things related to it. Any question about Home Assistant, and about using things with Home Assistant, is welcome here. We can’t help you with eve…

I see I read your example the wrong way. I edited my post above to fit your example.

[paulgryan52 (Paul Ryan)]

last question, when I click create helper, what do I select

[Edwin_D]

Strangely enough, I see it is now labeled Switch (Schakelaar in Dutch for me) while it does create an input_boolean.

[paulgryan52 (Paul Ryan)]

@Edwin_D

Auto fan

I don’t see a switch when clicking create helper

[paulgryan52 (Paul Ryan)]

[Didgeridrew]

“Toggle” creates an Input Boolean…

[paulgryan52 (Paul Ryan)]

[123 (Taras)]

The following single automation will:

Turn off the fan switch when:

• The light is turned on between 00:30-10:00.
• The fan switch is on.

Turn on the fan switch when:

• The light is turned off between 00:30-09:45.
• The fan switch is off.
• The last time the fan switch’s state changed was between 00:30-09:45.

Change the following two entity_ids to match what you have in your system.

1. light.your_light
2. switch.your_fan_plug

alias: example
trigger:
  - platform: state
    entity_id: light.your_light
    from: 'off'
    to: 'on'
    variables:
      mode: 'off'
      is_true: >
        {{ today_at('00:30') <= now() < today_at('10:00')
          and is_state('switch.your_fan_plug', 'on') }}
  - platform: state
    entity_id: light.your_light
    from: 'on'
    to: 'off'
    variables:
      mode: 'on'
      is_true: >
        {{ today_at('00:30') <= now() < today_at('09:45')
          and is_state('switch.your_fan_plug', 'off')
          and today_at('00:30') <= trigger.from_state.last_changed < today_at('09:45') }}
condition:
  - condition: template
    value_template: '{{ is_true }}'
action:
  - service: 'switch.turn_{{ mode }}'
    target:
      entity_id: switch.your_fan_plug

It doesn’t rely on an Input Boolean.

---

EDIT

Correction. Removed extraneous }} characters from second trigger’s is_true template.

[paulgryan52 (Paul Ryan)]

@123

alias: example
trigger:
  - platform: state
    entity_id: light.your_light
    from: 'off'
    to: 'on'
    variables:
      mode: 'off'
      is_true: >
        {{ today_at('00:30') <= now() < today_at('10:00')
          and is_state('switch.your_fan_plug', 'on') }}
  - platform: state
    entity_id: light.your_light
    from: 'on'
    to: 'off'
    variables:
      mode: 'on'
      is_true: >
        {{ today_at('00:30') <= now() < today_at('09:45')
          and is_state('switch.your_fan_plug', 'off') }}
          and today_at('00:30') <= trigger.from_state.last_changed < today_at('09:45') }}
condition:
  - condition: template
    value_template: '{{ is_true }}'
action:
  - service: 'switch.turn_{{ mode }}'
    target:
      entity_id: switch.your_fan_plug

can I still turn fan on/off manually between those times without affecting light

[123 (Taras)]

The best way to answer your question is that you should test the automation’s logic using various combinations of the light and switch being on/off.

If you don’t like thought experiments and prefer to observe it in action, change the time ranges from their current values to something more convenient (a 3 hour window around whatever time you test it during the day) then subject it to your test scenarios (I suggest you write them down beforehand because it’s easy to lose track of the various combinations).

I think it will work the way you want but testing it provides the best confirmation.

[paulgryan52 (Paul Ryan)]

I can test it when I go to bed tonight

[123 (Taras)]

Start testing the simple scenarios first (fan is on, turn light on, fan should stop, then turn light off and fan should start) and once you’re satisfied it does the basics correctly, subject it to the ‘edge cases’ where you manually turn the fan on/off and see how it impacts the automation’s behavior.

There may be some combination that fools the “last_changed” technique I used in the automation and causes the fan to be set incorrectly. If you discover such a failure scenario then it may be necessary, after all, to employ an Input Boolean as has been suggested.

[paulgryan52 (Paul Ryan)]

will do, automation won’t be used much

[paulgryan52 (Paul Ryan)]

@Edwin_D

@paulgryan52

turn fan on if it was previously on before light turned on

I can write an example, but I’d have to understand this. Wouldn’t you want to turn it off when it was previously off? I’ll assume the latter:

create an input helper in the Helper section of settings, named Auto fan (You can use another name, but then the entity name changes too in the automation. Automation for off:

alias: Fan off
description: ""
trigger:
  - platform: state
    entity_id: light.dakkapel
    from: "off"
    to: "on"
condition: 
  -  condition: time
     after: "00:30:00"
     before: "10:00:00"
action:
  - if:
      - condition: state
        entity_id: fan.dakkapel
        state: "on"
    then:
      - service: input_boolean.turn_on
        target:
          entity_id: input_boolean.auto_fan
        data: {}
  - service: fan.turn_off
    target:
      entity_id: fan.dakkapel
    data: {}
mode: single

Automation for on:

alias: Fan on
description: ""
trigger:
  - platform: state
    entity_id: light.dakkapel
    from: "on"
    to: "off"
condition:
  - condition: state
    entity_id: input_boolean.auto_fan
    state: "on"
action:
  - service: input_boolean.turn_off
    target:
      entity_id: input_boolean.auto_fan
    data: {}
  - service: fan.turn_on
    target:
      entity_id: fan.dakkapel
    data: {}
mode: single

You should of course replace entity id’s with the ones for your use case.

thank you for your .yaml, once I made the necessary changes it works perfectly, I changed the entity_id and changed the entity from fan to switch and it works just like I wanted

[123 (Taras)]

Did the example I suggested fail to work entirely or just under certain conditions? What were the results of your tests?