# Trigger Scene **URL:** \ **Category:** Configuration\ **Tags:** scene\ **Created:** [November 1, 2023, 8:30pm UTC](https://community.gladysassistant.com/t/scene-declencheur/8448 "2023-11-01T20:30:38Z")\ **Posts on this page:** 1\ **Showing post:** 25
**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:** [November 3, 2023, 2:13pm UTC](https://community.gladysassistant.com/t/scene-declencheur/8448/25 "2023-11-03T14:13:00Z")
Ok I think I understand your request, even though there remain a few points that bother me in your logic 😉 In the end we get a bit lost because in this thread you express 2 distinct requests. Your request No.1 : - Create a virtual device that groups the features of several physical devices, so that there is only one left to test within your scene. (maybe this ties into the notion of a « super device Â» I had already mentioned here \> [Créer un super device virtuel](https://community.gladysassistant.com/t/creer-un-super-device-virtuel/8056) (which was a brain fail for me ^^) Request No.2 : - Change the way a scene works \> the famous toggle ONE \<\<\>\> ALL which cannot make sense insofar as, even if I understand your logic, Gladys must process information one after the other to move forward logically. In other words, a sensor’s state cannot be a trigger. Only the **change of state** of it can be a triggering event. So your logic which is: > for the scene to execute, meaning for the alarm (total in this case) to activate, it requires « user absent Â» AND « all total-alarm sensors OK Â» We can turn it around any which way, it cannot take this form in Gladys (nor elsewhere I think). --- _[View the full topic](https://community.gladysassistant.com/t/scene-declencheur/8448)._