It does not matter. In this case i did turn off the light in the condition to the state off, i then triggerd the rule manualy in automation section and i did trigger it with the switch also set up as a trigger.
It is testen all possible ways, and it does NOT work. I have also tried with different entitys for condition, and different ways off evaluate it, same result it is ignored
Executing an automation in the automation section ignores the triggers and bypasses the conditions.
It basically jumps straight to the action.
That’s what Burning was getting at.
And what do you do when the light is not off? You always need an else, this means you need to use a dummy service or something similar for the else part and you make this whole thing way more complicated than it needs to be.
Ok, from the beginning:
You have this code in your automations:
- id: '1596233374824'
alias: Kommer hjem "PÃ…"
description: Bortebryter på "Enkelklikk"
trigger:
- event_data:
entity_id: zwave.yttergang_dimmer
scene_id: 26
event_type: zwave.scene_activated
platform: event
- entity_id: group.allpersons
platform: state
to: home
condition:
- condition: state
entity_id: light.kjkken_dimmer_level
state: 'off'
action:
- data: {}
service: script.lys_dag_pa
mode: single
Under Configuration -> Automations the automation is enabled.
Under Developer Tools -> Template the below results in “True”:
Question: Where does the documentation use your term ‘action template’?
Answer: Nowhere because it’s a term you invented.
The words ‘condition’, ‘function’, ‘template’, ‘action’, etc all have specific meanings in Home Assistant. However, you appear to be using them in different ways and that makes it difficult to understand your replies.
Please post an example of your automation, the version that works for you, so that we can understand what you refer to as an ‘action template’.
I suspect you mean you are using a template within the automation’s action either within a condition or a service_template.
Probably, but the problem here is not how i have solved the issue, the issue is that the condition in automation is NOT working.
I have multiple scripts and multiple automations that call eachother yes. And yes, ther is a else involved.
I think we leave it here, probably very vice to update ha docs on cavitys running manual automations that conditions is not evaluated. So next persons dont need to elaborate about life choices here.
Finding relevant documentation on this site is extremly difficult. I suggest you move vital information out of the troubleshooting guide and in to the automation section.