#Automation with mmmWave Presence Detector

1 messages · Page 1 of 1 (latest)

fluid crest
#

@lethal vale this is my yaml file

lethal vale
#

There is no yaml file.

fluid crest
#

@lethal vale I was finally able to share my yaml code. I beleive the issue is dealing with the timer.helper and the finished option. https://dpaste.org/0RAz2

vale rain
#

The YAML was so good you posted the link twice zany

tardy kilnBOT
#

There are three sections to an automation:

  • trigger: When any one of these becomes true the automation starts processing. Only one trigger is ever responsible for starting an automation, if you make a condition that checks for more than one having started the automation then the condition can never be true.
  • condition: These are checked after a trigger starts the processing, and must be true for the automation to continue.
  • action: This is the part that does something, and can also include further conditions.
vale rain
# 
          - condition: and
            conditions:
              - condition: trigger
                id:
                  - MasterBathroomAthomMMWave-Detection
                enabled: true
              - condition: trigger
                id:
                  - DelayTimerFinishedForToiletOrShower
#

That can't ever be true

fluid crest
#

@vale rain - I am not understanding . I created 2 triggers.. condition is an 'AND' for detection to occur and the delayTimerFinished. (This was started in my 1st condition) that was executed successfully and the timer counter starts.

lethal vale
#

As Tinkerer said you can not have two triggers at the same time.

fluid crest
#

I have 3 for my condition and it works

lethal vale
#

Your automation will run when 1 trigger is fired. So you need to test the state of your entities and not the trigger.
Also you have your Choose statement wrong as you have multiple choose options rather than a single one with multiple choices

#

You do not need to use a And Condition at all because by default all conditions are AND'ed

fluid crest
#

ok. I thought multiple triggers were treated as 'OR' . I will make the conditions be all in the same grouping and report back.

lethal vale
#

"When" items are ORed "If" Conditions are ANDed.

fluid crest
lethal vale
#

No, that example is using two entities and a trigger, but you over complicated the levels. The one Tinkerer pointed out you have two triggers one one condition.

fluid crest
#

The above is from my yaml that I posted but the issue I'm having is the timer.finished is not being triggered when the timer counts down to zero

#

I have seen YT videos where they use triggerID in the condition to execute the action . Just like the GUI code I posted labeled 1st condition and then the action.

vale rain
#

trigger id conditions are fine

#

However, as has been said many times, only one trigger starts an automation

#

You two and trigger conditions can never be true