# Enable / disable a scene from another scene **URL:** \ **Category:** Demande de fonctionnalités\ **Tags:** in-progress\ **Created:** [August 15, 2026, 3:49pm UTC](https://community.gladysassistant.com/t/pouvoir-activer-desactiver-une-scene-depuis-une-autre-scene/10580 "2026-08-15T15:49:01Z")\ **Posts on this page:** 2\ **Page:** 1
**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:** [August 15, 2026, 3:49pm UTC](https://community.gladysassistant.com/t/pouvoir-activer-desactiver-une-scene-depuis-une-autre-scene/10580/1 "2026-08-15T15:49:01Z")
It would be useful to be able to activate or deactivate another scene from a scene. I describe a use case: - I have a small water recovery tank. With the drought, I sometimes need to fill it from a potable water tap, but in this case I don’t want to fill it more than 40%. - Scene A checks the amount of water in my tank every 5 minutes and notifies me if it is filled to at least 40%. I then know that I need to go and turn off the tap. - I don’t want Scene A to run continuously, otherwise I will be unnecessarily notified when the filling exceeds 40% due to a storm. - Scene B allows me to activate Scene A, and I place a button from Scene B on my dashboard. It is already possible to go through a virtual MQTT device to ‹ tinker › with this, but it is not very intuitive. There is already a topic started by @guim31 that was talking about it ([Activate/Deactivate a scene from a scene](https://community.gladysassistant.com/t/pouvoir-activer-desactiver-une-scene-depuis-une-scene/6858)), but it was more of a discussion than a feature request and I thought it better for this to be handled by the AI to start a new topic. ---
**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:** [August 17, 2026, 12:05pm UTC](https://community.gladysassistant.com/t/pouvoir-activer-desactiver-une-scene-depuis-une-autre-scene/10580/2 "2026-08-17T12:05:44Z")
Hi everyone! This topic is now **under development**. A PR has been opened to add the « Enable a scene » and « Disable a scene » actions: > > > Implements feature request: https://community.gladysassistant.com/t/pouvoir-acti…ver-desactiver-une-scene-depuis-une-autre-scene/10580 > > \### Description > > Scenes already have an \`active\` flag, but until now it could only be toggled by hand in the scene UI. This PR adds two new scene actions that let a scene turn another scene's \`active\` flag on or off: > > \- \*\*Enable a scene\*\* (\`scene.enable\`) > \- \*\*Disable a scene\*\* (\`scene.disable\`) > > This removes the need for the virtual MQTT device workaround people currently use to arm/disarm a scene from another scene. > > The use case described on the forum: a scene checks a water tank level every 5 minutes and notifies when it reaches 40%. It should only be armed while the tank is being filled. With these actions, the checking scene can disable itself once it has notified, and a second scene (bound to a dashboard button) re-enables it when a new filling starts. > > Details: > > \- New \`ACTIONS.SCENE.ENABLE\` / \`ACTIONS.SCENE.DISABLE\` constants. > \- Server handlers persist the flag through \`scene.update\`, which already cancels or re-schedules the target scene's triggers, so a disabled scene really stops listening immediately. > \- A scene is allowed to target \*\*itself\*\*: that is what makes the "run once, then disarm until re-armed" pattern possible. Contrary to the "Start scene" action, the current scene is therefore kept in the scene selector. > \- Edge cases: \`AbortScene('SCENE\_NOT\_FOUND')\` when no scene is selected or when the target scene no longer exists (deleted in the meantime); unexpected errors are propagated. > \- The two actions are also exposed in the MCP scene creation schemas, so the AI assistant can build such scenes. > \- Front: shared action card component, entry in the action selector, and translations in \`en\`, \`fr\` and \`de\`. > > This pull request was produced by an automated run. > > \## Forum > > Forum: https://community.gladysassistant.com/t/pouvoir-activer-desactiver-une-scene-depuis-une-autre-scene/10580 > > \### Checklist > > \- \[x\] Tests pass: \`cd server && npm run coverage\` (Codecov requires 100% coverage on changed lines) and Cypress (\`npm run cypress:run\`) if the UI changed > \- \[x\] Linter and prettier pass on both front and server (\`npm run eslint\`, \`npm run prettier\`) > \- \[x\] No undocumented breaking change > > > \--- > \_Generated by \[Claude Code\](https://claude.ai/code/session\_01REGRUvErzpwtSrsi9gKh4J)\_ Don’t hesitate to follow the PR, test as soon as possible, and share your feedback here.