#triggerless automation
1 messages · Page 1 of 1 (latest)
A triggerless automation is a script. However without a trigger the script won't run. Why don't you want to use a trigger?
I am not sure what kind of trigger it would be. I have it working partially (switch on) by using every one of the 13 thermostatic valves as triggers. However that gets more complicated when switching the pump off whenever ALL targets are below actual. If I use eg HA starting as trigger, will the automation then only run on startup or anytime after startup?
So I am looking for Paulus IS home rather than Paulus ARRIVES home. I understand I can make it a condition, but then what would be the trigger?
What are you trying to achieve?
A trigger is always a single event, so when X changes to Y.
- When Paulus arrives home (changes state from
not_hometohome) - When HA starts (changes from booting to started)
switch a central heating pump on/off depending on the relation of target/actual temperature of any (on) / all (off) the 13 thermostatic valves.
I have not understood if the meaning of "When HA starts" is that the automation will only run on startup, or anytime from startup as well.
Only on startup, as a trigger is a single event
You need to trigger on changes of those valves
OK, that is what I thought. So how to make so that it would run anytime the conditions are met?
please explain in more detail what you are trying to achieve
I just wrote that twice: switch a central heating pump on/off depending on the relation of target/actual temperature of any (on) / all (off) of the 13 thermostatic valves.
Am I right in thinking that I will have to enter all 13 devices as triggers?
either that or you might be able to use a template
Yes, but I'm asking for more details so I can help you.
What do you meant with the relation of target/actual temperature.
But you can probably combine them in one trigger
# example
trigger: state
entity_id:
- climate.valve_1
- climate.valve_2
- climate.valve_3
attribute: temperature
Tihis will trigger when the temperature attribute of one of those climate entities changes
I see, neater, nice. Obviously I was only looking at GUI so far. Will have to dive into YAML then. Thanks
With the new triggers introduced as lab feature in 2025.12 it will become easier
Haven't looked at it yet, but I was planning on doing so. Thanks.
you can create this in the GUI as well, no need to type YAML