# Condition reversed on EDF-Tempo

**URL:** <https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162>\
**Category:** Configuration\
**Created:** [March 30, 2026, 8:20am UTC](https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162 "2026-03-30T08:20:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjm](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/bjm/32/1753_2.png) [@bjm](https://community.gladysassistant.com/u/bjm)\
**Post date:** [March 30, 2026, 8:20am UTC](https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162/1 "2026-03-30T08:20:10Z")

</div>

**Ability to invert the default behavior of the condition on EDF-Tempo**

Currently, the default behavior

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [March 30, 2026, 9:09am UTC](https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162/2 "2026-03-30T09:09:11Z")

</div>

Hello @bjm 🙂

This is already possible with the «&nbsp;If… Then… Else&nbsp;» condition!

You just need to create an «&nbsp;If… Then… Else&nbsp;», put the condition on EDF-Tempo in the «&nbsp;If&nbsp;» and place your action in the «&nbsp;Else&nbsp;».

It’s true that the message could be improved, it dates back to a time when this condition didn’t exist yet 🙂

---

<div class="post-metadata">

**Author:** ![bjm](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/bjm/32/1753_2.png) [@bjm](https://community.gladysassistant.com/u/bjm)\
**Post date:** [March 30, 2026, 9:51am UTC](https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162/3 "2026-03-30T09:51:42Z")

</div>

That’s the direction I went, but for the average user, it seemed easier to have a checkbox to continue or stop the scene.

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [March 30, 2026, 10:00am UTC](https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162/4 "2026-03-30T10:00:04Z")

</div>

I’m not sure it makes much sense to keep this very «&nbsp;linear&nbsp;» approach.

Wouldn’t the solution be to make the «&nbsp;If… Then… Else&nbsp;» block mandatory to handle conditions?

This would also make it easier to distinguish the list of actions from the list of conditions, which is often a point of friction.

I have the impression that the «&nbsp;Shortcuts&nbsp;» app on iPhone/Mac/iPad (intended for the general public) works exactly this way, conditions are only available in an «&nbsp;If&nbsp;» block:

 ![Capture d’écran 2026-03-30 à 11.59.09](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/5/f/5f010678eeb2bc720e52d78a44c346940670ed4b.jpeg)

---

<div class="post-metadata">

**Author:** ![bjm](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/bjm/32/1753_2.png) [@bjm](https://community.gladysassistant.com/u/bjm)\
**Post date:** [March 30, 2026, 10:08am UTC](https://community.gladysassistant.com/t/condition-inversee-sur-edf-tempo/10162/5 "2026-03-30T10:08:05Z")

</div>

Indeed, this would standardize the conditions.