See which scenes are running and stop them

StephaneB · July 24, 2024, 11:36am

I’ve created some scenes that run for quite a long time. For example:

start the fan and stop it automatically after two hours.
detect the garage door opening and notify me in 20 minutes if I’ve forgotten to close it.
water the garden in 5-minute periods every hour, for 6 hours
…

But the problem sometimes is that I don’t know how many instances of a scene are currently running, and the only way I have, if I want to prevent these scenes from reaching their end, is to completely restart Gladys.

I would find it useful to be able to view the scenes that have running instances, how long they’ve been running, and to be able to stop one of them or all of them.

Have others besides me already had this kind of need? Does this feature seem relevant to you @pierre-gilles and worth describing a bit more?

Psoy · January 27, 2025, 9:19am

Hello @StephaneB
I agree with you, that would be very useful to me

Jluc · March 22, 2025, 2:47pm

Hello @StephaneB,
First of all, well done and thank you for all the work you’ve done to improve Gladys.
I’m following up on your feature request and, in addition, would it be possible to have the launch « arrow » button colored for as long as the scene is active?

StephaneB · March 24, 2025, 8:12am

That could be a way to visualize the scenes currently running, yes, I agree.

Lokkye · July 26, 2026, 9:06pm

Small proposal

github.com/GladysAssistant/Gladys

feat(scene): see and stop running scenes (#9015) (#2710)

master ← callemand:feature/scene-stop-execution

ouvert 09:01PM - 26 Jul 26 UTC

callemand

+860 -53

### Pull Request check-list - [x] If your changes affect the code, did you wr…ite the tests? - [x] Are server tests passing with coverage? (`cd server && npm run coverage`) — new code covered by `test/lib/scene/scene.stop.test.js`, additions to `scene.execute.test.js`, and controller tests (only a few defensive guards remain, e.g. "scene deleted while queued") - [ ] Did Cypress E2E tests pass? — not run locally; feature tested by hand (see screenshots) - [x] Is the linter passing? (`npm run eslint` on both front/server) - [x] Did you run prettier? (`npm run prettier` on both front/server) - [x] If you are adding a new feature/service, did you run the integration comparator? (`npm run compare-translations` on front) — passes (fr/en/de complete) - [x] Did you test this pull request in real life? (see screenshots below) - [x] If your changes modify the API (REST or Node.js), did you modify the API documentation? — `@api` comments added for the new endpoints - [ ] If you are adding a new features/services which needs explanation, did you modify the user documentation? — small UX addition, no dedicated docs page needed - [x] Did you add fake requests data for the demo mode (`front/src/config/demo.js`)? — added `get /api/v1/scene/running` ### Description of change Implements the community request [#9015 — *Connaître les scènes en cours d'exécution et pouvoir les arrêter*](https://community.gladysassistant.com/t/connaitre-les-scenes-en-cours-d-execution-et-pouvoir-les-arreter/9015): see which scenes are currently running (and for how long), and stop them without restarting Gladys. Delivered in two parts: **Lot 1 — See running executions** - In-memory registry of running scene executions in the `SceneManager` (keyed by a generated `executionId`), populated in `scene.execute.js` and cleaned up in a `finally`. - New `scene.getRunning()` + `GET /api/v1/scene/running` (registered before `:scene_selector` to avoid a route collision). - Real-time `scene.started` / `scene.stopped` websocket events. **Lot 2 — Stop a running scene** - An `AbortController` per execution, exposed to actions via `scope.abortSignal`. - The `delay` action is now **abortable** (a scene waiting in a long delay can be interrupted immediately), plus cooperative cancellation between actions. - `scene.stop(executionId)` / `scene.stopBySelector(sceneSelector)` + `POST /api/v1/scene/:scene_selector/stop` and `POST /api/v1/scene/execution/:execution_id/stop`. **Frontend** (scene list, scene editor and dashboard scene widget) - While a scene runs, the **Start** button becomes a live indicator (`En cours` + elapsed time, green outline) that turns into a red **Stop** button on hover. Constant width, updates in real time over websocket. Shared `RunningStopButton` component. **Notes** - The stop is cooperative: a `delay` is interrupted instantly; a long non-interruptible action (e.g. a big HTTP request) finishes before the stop takes effect between two actions. - The running registry is in-memory only (lost on reboot, which already stops scenes). ### Screenshots <img width="1239" height="787" alt="Screenshot 2026-07-26 at 22 56 23" src="https://github.com/user-attachments/assets/58ce20b9-c5c7-4cd8-878a-5b458a6310aa" /> <img width="1228" height="795" alt="Screenshot 2026-07-26 at 22 56 18" src="https://github.com/user-attachments/assets/558a2535-5f68-47b8-bfdc-5055ab4cc24b" /> <img width="618" height="302" alt="Screenshot 2026-07-26 at 22 56 03" src="https://github.com/user-attachments/assets/4406c26c-6737-4665-960c-b66cdea9822a" /> <img width="606" height="303" alt="Screenshot 2026-07-26 at 22 55 59" src="https://github.com/user-attachments/assets/7a09b68e-677c-4d6d-b2ed-007cd2a9f1da" /> <img width="402" height="124" alt="Screenshot 2026-07-26 at 22 55 52" src="https://github.com/user-attachments/assets/fcc8599f-511d-4427-8b10-03b9d05d665f" /> <img width="412" height="123" alt="Screenshot 2026-07-26 at 22 55 47" src="https://github.com/user-attachments/assets/9ee6fe55-5de3-487d-a906-8edc04f2c3c9" />

pierre-gilles · July 27, 2026, 9:32am

Excellent, is this done with Fable 5?

I don’t know if you’ve seen, but the PR isn’t passing. Can you ask Claude to monitor the PR so he automatically fixes all the feedback (CodeRabbit, Tests, Coverage)?

Lokkye · July 27, 2026, 10:01am

Not just Opus 5 in High (The same config I use at work)

« I » will fix that. But it’s just that I closed my VSCode by reflex

pierre-gilles · July 27, 2026, 11:05am

Ok Opus 5 in High C is also great!

Don’t you use the Claude agents in the cloud? I don’t do anything locally anymore

Lokkye · July 27, 2026, 11:36am

Yes I have 3 VSCode instances running in parallel, I can’t get used to the cloud mode. And I feel like I have more control when it goes off on a tangent

Chris75 · July 29, 2026, 12:31pm

I would also find it very useful to be able to stop a scene

StephaneB · August 16, 2026, 3:05pm

@pierre-gilles I’m passing this request on to you, it would be great if it could be part of next week’s 100 features

pierre-gilles · August 17, 2026, 12:48pm

It was already developed by @Lokkye (see message above)

Topic		Replies	Views
Gladys Assistant 4.31 : Filtre par tag & MQTT dans les scènes Actualités	35	863	October 15, 2024
Ajouter une description aux scènes Demandes livrées feature-core , scene	23	1260	May 26, 2023
Liste de possibles améliorations UX/UI (StéphaneB) Configuration	23	237	April 17, 2025
Duplication de scènes Demandes livrées feature-core , scene , feature-request-ux	39	2158	January 16, 2023
Possibilité d'exécuter une scène depuis le Dashboard Demandes livrées feature-core , dashboard , box-dashboard , scene	11	958	September 11, 2023

See which scenes are running and stop them

Related topics