# Trigger improvement: Device state change On/Off - Open/Closed **URL:** \ **Category:** Demandes livrées\ **Created:** [May 22, 2025, 12:17pm UTC](https://community.gladysassistant.com/t/amelioration-du-declencheur-changement-detat-de-lappareil-on-off-ouvert-ferme/9539 "2025-05-22T12:17:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\ **Post date:** [May 22, 2025, 12:17pm UTC](https://community.gladysassistant.com/t/amelioration-du-declencheur-changement-detat-de-lappareil-on-off-ouvert-ferme/9539/1 "2025-05-22T12:17:20Z")
Currently when we need to activate a scene on a device’s on/off or open/closed state change, we have to create 2 triggers, 1 for each state because the 2 cannot be active at the same time: ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/a/7/a7013147e25f1d261f41e24320db98e25fb56ba1.png) 2 ideas for improvement : - a 3rd button to trigger on any state ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/6/f/6ff1479a6232e8f57117e66ee0c88d2ee93db817.png) - the ability to activate both buttons ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/e/e/ee1cb0c23f10c552dddf2addd6ca97896cde13f0.jpeg) Thanks in advance. ---
**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\ **Post date:** [May 22, 2025, 4:16pm UTC](https://community.gladysassistant.com/t/amelioration-du-declencheur-changement-detat-de-lappareil-on-off-ouvert-ferme/9539/2 "2025-05-22T16:16:30Z")
It’s true that it would be nice not to have to create multiple blocks. ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/c/f/cf917e1716ac92e4680acb9aeb3956b0689328f2.png) I’m really into that kind of thing 😉 ---
**Author:** ![StephaneB](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/stephaneb/32/15443_2.png) [@StephaneB](https://community.gladysassistant.com/u/StephaneB)\ **Post date:** [May 22, 2025, 4:29pm UTC](https://community.gladysassistant.com/t/amelioration-du-declencheur-changement-detat-de-lappareil-on-off-ouvert-ferme/9539/3 "2025-05-22T16:29:34Z")
I also think that would be a good idea. But rather in the variant with a third button, which seems more explicit to me. ---
**Author:** ![cursor-bot](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cursor-bot/32/22252_2.png) [@cursor-bot](https://community.gladysassistant.com/u/cursor-bot)\ **Post date:** [October 29, 2026, 10:42am UTC](https://community.gladysassistant.com/t/amelioration-du-declencheur-changement-detat-de-lappareil-on-off-ouvert-ferme/9539/5 "2026-10-29T10:42:13Z")
Hi @mutmut! The device state trigger has a third option, since Gladys 5.0: **Start the scene on every state change, regardless of the value.** A single trigger reacts to both on and off, or to opening and closing. You no longer need to create two triggers that conflict with each other. I’m moving this topic to « Delivered Requests ». If there’s still a case that doesn’t fit, open a new topic: it will be easier to follow. ---
**Author:** ![cursor-bot](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cursor-bot/32/22252_2.png) [@cursor-bot](https://community.gladysassistant.com/u/cursor-bot)\ **Post date:** [October 29, 2026, 10:56am UTC](https://community.gladysassistant.com/t/amelioration-du-declencheur-changement-detat-de-lappareil-on-off-ouvert-ferme/9539/6 "2026-10-29T10:56:22Z")