#Broadlink fan Automation

1 messages · Page 1 of 1 (latest)

snow fern
#

I have a simple automation i'm trying to get to work and failing. The fan does not trigger on either event and i can't figure out why?
this is my automation i am trying for this. Basically i just want a fan to turn on above a certain temp, then turn off below a certain temp.

`alias: Master Fan At Work
description: ""
triggers:

  • type: temperature
    device_id: 83194019b4a29731e92a462014143112
    entity_id: c72da6384356b6c0d3cf5f63fe125cf1
    domain: sensor
    trigger: device
    id: HIGH_TEMP
    above: 70.5
  • type: temperature
    device_id: 83194019b4a29731e92a462014143112
    entity_id: c72da6384356b6c0d3cf5f63fe125cf1
    domain: sensor
    trigger: device
    below: 69
    id: FAN_OFF
    conditions: []
    actions:
  • choose:
    • conditions:
      • condition: trigger
        id:
        • HIGH_TEMP
      • condition: state
        entity_id: sun.sun
        state: above_horizon
        sequence:
      • action: remote.send_command
        metadata: {}
        data:
        num_repeats: 1
        delay_secs: 0.4
        hold_secs: 0
        device: Master_Fan
        command: fan_2
        target:
        device_id: 3f57d1f30dee4918031e33f23a005e32
        entity_id: remote.broad_remote
  • choose:
    • conditions:
      • condition: trigger
        id:
        • FAN_OFF
      • condition: state
        entity_id: sun.sun
        state: above_horizon
        sequence:
      • action: remote.send_command
        metadata: {}
        data:
        num_repeats: 1
        delay_secs: 0.4
        hold_secs: 0
        device: Master_fan
        command: fan_off
        target:
        device_id: 3f57d1f30dee4918031e33f23a005e32
        entity_id: remote.broad_remote
        mode: single`
young junco
#

Hi @snow fern,
You are using device triggers whioch makes it more dificukt to troubleshoot, but let my see if we can find something.

  • action: remote.send_command
    metadata: {}
    data:
    num_repeats: 1
    delay_secs: 0.4
    hold_secs: 0
    device: Master_Fan
    command: fan_2
    target:
    device_id: 3f57d1f30dee4918031e33f23a005e32
    entity_id: remote.broad_remote
    Did you test this seperately? Ie have you put this into dev - actions to test if it is working?
mellow kernelBOT
snow fern
#

yes. both commands work in dev tools. i need to correct something. i got the fan to cut on above the threshold but it just wont cut back off below the threshold

young junco
#

Then you are just having a trigger problem. read this...

snow fern
#

i used both device and entity for the broadlink because for some odd reason it would not work without both in dev tools and i had read somewhere else that it can be finicky that way

young junco
#

triggers are events and trigger when the threshold is crossed only

snow fern
#

are you saying the way i have it wont cut it off when it gets below the threshold?

young junco
#

It will trigger when it goes from 69 to less than 69, and when it goes from 70,5 to above that.

#

If those are the linits to your operating range, trigger on any temperature change, and in the conditions key tab set your range limits.

# 
id: FAN_OFF

conditions: []
actions:

snow fern
#

i set those limits for testing. lemme try the whole auto in dev and see

#

Executed: November 18, 2024 at 3:02:22 PM
Error: Command not found: 'fan_off'
Result:
choice: 0

#

thats whats doing it..i dont get why though.

#

it works in dev tools.

#

😣 nm....i had Master_fan as the device and not Master_Fan

#

so picky lol