#change state X -> X. Will it send spamming request?
1 messages · Page 1 of 1 (latest)
that's not a state change, so it won't trigger anything
if you're talking about what happens if you tell a device that's off to turn off, it will send the command again
to be clear: Do you mean if result of automation change state to the same value nothing will happen.
it's up to the integration to decide whether not to, but I suspect that most will just send the command anyway
if you don't want that, you can add a condition
I see: if I choose "device" as a result of automation the "off" will be send, but if I will select "entitity" as a result of automation and the state will be not modified nothing will happen.
no, there's no difference between those
hmm so I didn't get it
Will it send request to device controling light if state is already "off" ?
What did you mean by
that's not a state change, so it won't trigger anything
?
I misunderstood your initial question
wrong screen, for this changing from "on" to "on"
ah then I got it
actions always run
thanks
any way to configure HA to not send request if state didn't change?
for all automations?
no
🍻
Add conditions where you want to avoid it. I do that in my "turn off all the lights" automation to avoid wasting time turning off lights that area already off, because it can slow down the response
This is what I am doing, but I don't like it because I repeat myself a lot
script:
fr_off:
mode: queued
sequence:
- condition: state
entity_id: switch.fr_lamp_group
state: 'on'
- entity_id: switch.fr_lamp_group
action: homeassistant.turn_off
sorry, this is better example of repeating
I have trigger and condition: motion off / person off. plus I check if light is on (not off).
A lot of repeating
I was looking a way to simplify it, but if not possible, then I have my answer 🙂
you can always combine things
blueprints are one option, scripts are another, templates another