# Demande de mise en place d'un bouton arrêt et redémarrage du raspberry **URL:** \ **Category:** Demandes livrées\ **Tags:** feature-core, in-progress\ **Created:** [Janvier 13, 2022, 5:36 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786 "2022-01-13T17:36:34Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![mikael](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/m/f04885/32.png) [@mikael](https://community.gladysassistant.com/u/mikael)\ **Post date:** [Janvier 13, 2022, 5:36 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/1 "2022-01-13T17:36:35Z")
Bonjour, J’ai pas trouver de opic parlant de çà mais un bouton pour arrêter/redemarrer proprement le raspberry depuis gladys serait un plus. Je pense qu’il aurait sa place au niveau du menu système pour les administrateurs. J’ai rapidement vu que c’était possible d’éteindre l’hôte depuis un docker mais j’ai pas fait le test. ---
**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:** [Janvier 13, 2022, 7:44 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/2 "2022-01-13T19:44:09Z")
Pourquoi pas, bonne idée 🙂 ---
**Author:** ![Fabic](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/f/a698b9/32.png) [@Fabic](https://community.gladysassistant.com/u/Fabic)\ **Post date:** [Janvier 13, 2022, 8:00 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/3 "2022-01-13T20:00:30Z")
Sinon : Ouvrir un terminal (“cmd” dans la barre de recherche sous windows ou ctrl+alt+T sous linux) ssh pi@ip-de-gladys mdp du pi (raspberry la première fois) sudo shutdown now ---
**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:** [Janvier 13, 2022, 9:18 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/4 "2022-01-13T21:18:00Z")
Ce qui est un peu moins user friendly il faut l’avouer haha ---
**Author:** ![mikael](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/m/f04885/32.png) [@mikael](https://community.gladysassistant.com/u/mikael)\ **Post date:** [Janvier 14, 2022, 9:07 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/5 "2022-01-14T09:07:14Z")
petite précision lorsque l’on se connecte la première fois il demande le changement de mot de passe du compte pi. Je demande çà car Gladys est dans une démarche user friendly. c’est comme si dans windows on te disait de taper la commande `shutdown /s` à chaque fois pour arrêter ton pc. C’est juste que des fois mon raspberry est arrêté de façon brutale car mon pc est pas forcément allumer. Après c’est pas une feature a développer en urgence car pour la majorité nous savons aller sur un système linux et l’arrêter proprement. ---
**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:** [Janvier 14, 2022, 9:17 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/6 "2022-01-14T09:17:52Z")
> [@mikael](#): > > Je demande çà car Gladys est dans une démarche user friendly. c’est comme si dans windows on de disait de taper la commande `shutdown /s` à chaque fois pour arrêter ton pc. Je suis 100% d’accord avec toi, dans la v4 la principale philosophie c’est « pas de CLI, pas de SSH ». ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [Décembre 28, 2022, 5:53 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/7 "2022-12-28T17:53:46Z")
Salut @pierre-gilles Il y a une possibilité d’avoir un cron sur le pi qui lance un script disons toute les secondes ce script peut crée dans Gladys puis copié dans le système local [26 commandes Docker les plus courantes avec exemples](https://geekflare.com/fr/docker-commands/) partie 19 A partir de là n’importe quelle commande peut-être exécutée (arret/redemarrage etc) depuis le container Gladys dans le système local, il faut juste au démarrage avoir un script qui supprimes le script envoyé depuis Gladys précédemment ! 🙂 Il serait même possible d’avoir un retour d’état avec exec dans le script [26 commandes Docker les plus courantes avec exemples](https://geekflare.com/fr/docker-commands/) partie 7 il suffit de faire une création de fichier dans le docker avec la commande qui va bien ! 😉 ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [Décembre 28, 2022, 7:48 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/8 "2022-12-28T19:48:18Z")
C’est une idée effectivement, cependant trop risqué pour moi, il suffit que le/les scripts ne soit pas supprimé et on redemarre en boucle. Dans tous les cas ont est en mode serveur, le besoin de stop restart est quasi nul. Seul cas un update de kernel, dans ce cas c’est toi qui le fait manuellement et donc peut redémarrer. ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [Décembre 28, 2022, 8:05 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/9 "2022-12-28T20:05:22Z")
il y a la possibilité de limiter le nombre de fois ou le script peut-être exécuté via une limite par timestamp dans le nom du script par exemple ou mieux via crontab non ? Donc un crontab toute les secondes qui surveille un script envoyé depuis Gladys, dans le script il y la 1ère commande crontab à exécuter ainsi pas de risque de boucle et on peut avoir un log qui peut être analysé par une 2de commande crontab du script précédent qui lui peut générer un retour via un crontab qui génère une commande dans le container Gladys. Bref de quoi faire interagir Gladys avec son environnement…cela pourrait même être intégrable dans Gladys avec les scénarios ! 🫢 ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [Décembre 28, 2022, 8:09 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/10 "2022-12-28T20:09:06Z")
Je penses que le plus propre pour l’hote c’est de passer par dbus, il y’a un package nodejs de dispo. Côté Gladys on pourra vérifier que dbus est dispo dans le conteneur, et si c’est le cas d’afficher le/les boutons. Et oui pourquoi pas avoir aussi dans les scenes une action dispo. [https://www.freedesktop.org/wiki/Software/systemd/dbus/](https://www.freedesktop.org/wiki/Software/systemd/dbus/) Et dans ce cas on limite les risques. ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [Décembre 30, 2022, 10:23 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/11 "2022-12-30T22:23:47Z")
Quelle que soit la solution ce serait un vrai plus pour l’utilisateur lambda de pouvoir arrêter son système proprement (pour une question de maintenance par exemple) sans passer par une connexion ssh pas user-friendly ! Je connais pas dbus, il marcherait aussi sur d’autre plate-forme que PI et/ou sous windows ? ---
**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\ **Post date:** [Juillet 24, 2026, 2:18 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/12 "2026-07-24T14:18:58Z")
J’ai (Claude :)) commencé à faire une implémentation simple en utilisant dbus. ![Screenshot 2026-07-24 at 16.14.52](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/7/3/735a9601857f86ca217cbf44b2bc7812f5f1429b.png) ![Screenshot 2026-07-24 at 16.17.07](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/4/f/4f2efff2fb691baa8367f7f40825c23687b56f60.png) Il faut que je fasse les tests sur mon installation avec le docker mais c’est en bonne voie. ---
**Author:** ![Lokkye](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lokkye/32/5881_2.png) [@Lokkye](https://community.gladysassistant.com/u/Lokkye)\ **Post date:** [Juillet 24, 2026, 7:31 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/13 "2026-07-24T19:31:45Z")
Tester sur mon MiniPC sous debian Les PRs qui vont bien: > > > Documents the new \*\*Reboot / Shutdown host\*\* feature added in GladysAssistant/Gl…adys#2709. > > \- Add \`-v /run/dbus:/run/dbus:ro\` to the \`docker run\` command so the buttons (Settings → System) can reach systemd-logind over the system D-Bus socket. > \- Add a "Reboot / Shutdown the host from Gladys" section explaining the requirements (systemd host, \`--privileged\`, D-Bus socket) and behaviour. > \- English (\`docs/\`) and French (\`i18n/fr\`) versions. > > Companion PR: GladysAssistant/Gladys#2709 > > 🤖 Generated with \[Claude Code\](https://claude.com/claude-code) > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fast… as possible, make sure to review and check all of these items: > > \- \[x\] If your changes affect the code, did you write the tests? > \- \[x\] Are server tests passing with coverage? (\`cd server && npm run coverage\`) — Codecov requires \*\*100% coverage on lines changed in this PR\*\* \_(the new functions \`rebootHost\`/\`shutdownHost\`/\`isHostPowerManagementAvailable\` are at 100%; the new controller handlers and the added \`getInfos\` line are covered too)\_ > \- \[\] Did Cypress E2E tests pass? (\`npm run cypress:run\` from repo root, if UI changed) \_(left to CI)\_ > \- \[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) — en/fr/de complete > \- \[\] Did you test this pull request in real life? With real devices? \_(AMD64 test image being built for a real x86\_64 host running systemd)\_ > \- \[x\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (apidoc \`@api\` comments added for the two new endpoints) > \- \[x\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See https://github.com/GladysAssistant/v4-website — done in \`feature/reboot-shutdown-host-docs\` (EN + FR) > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`)? \_N/A — no new device/service data, only two admin actions\_ > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > Adds the ability to \*\*reboot or shut down the host machine\*\* running Gladys (Raspberry Pi, mini-PC…) directly from the \*\*Settings → System\*\* page — a frequently requested feature (\[forum\](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786)). > > Until now \`system.shutdown()\` only stopped the Gladys process; there was no way to power off / reboot the underlying host. > > \*\*Mechanism.\*\* The two actions talk to \`systemd-logind\` over the host \*\*system D-Bus socket\*\* (\`org.freedesktop.login1\` → \`Reboot\` / \`PowerOff\`, non-interactive), via \`dbus-send\`. No new npm dependency; the \`dbus\` package is added to both Docker images so \`dbus-send\` is present. > > \*\*Backend\*\* > \- \`system.rebootHost\` / \`system.shutdownHost\`: call systemd-logind through D-Bus. > \- \`system.isHostPowerManagementAvailable\`: best-effort capability check (Linux + \`dbus-send\` binary + system D-Bus socket), exposed in \`getInfos()\` as \`host\_power\_management\_available\`. > \- \`POST /api/v1/system/reboot\` and \`POST /api/v1/system/shutdown-host\` (authenticated + admin). The command is awaited so failures are returned to the client. > > \*\*Frontend\*\* (Settings → System) > \- New "Reboot / Shutdown host" card with a \*\*two-step confirmation\*\* (anti-misclick). > \- Buttons are \*\*disabled with a tooltip\*\* when the capability is unavailable, and the server error message is surfaced on failure. > \- Reboot button is orange (\`btn-warning\`), Shutdown is red (\`btn-danger\`), matching the app's button conventions. > \- i18n: en / fr / de. > > \*\*Docker\*\* > \- Install the \`dbus\` package in \`docker/Dockerfile\` and \`docker/Dockerfile.buildx\`. > \- Requires the host D-Bus socket mounted: \`-v /run/dbus:/run/dbus:ro\` (documented in the v4-website PR). > > \*\*Behaviour on a standard install\*\*: after a \*\*reboot\*\* the Gladys container comes back thanks to \`--restart=always\`; after a \*\*shutdown\*\* the machine stays off until powered on manually. If the host is not systemd-based or the socket isn't mounted, the buttons stay disabled. > > \*\*Tests\*\*: unit tests for the two host-power functions (D-Bus command + failure propagation), the capability check (Linux/binary/socket matrix), and the two new controller endpoints. > > \_Screenshots to be added.\_ > > > > \## Summary by CodeRabbit > > \* \*\*New Features\*\* > \* Added administrator host power controls in System Settings (reboot and shutdown) with two-step confirmations. > \* Added success/error feedback and clear messaging when host power actions are unavailable. > \* Added host power availability detection to automatically disable the controls when unsupported. > \* Added English, French, and German translations for the host power UI. > \* \*\*Bug Fixes\*\* > \* Improved user-facing error reporting when host power commands cannot be issued. > \* \*\*Chores\*\* > \* Updated container images to include the system tooling required for host power requests. ---
**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:** [Juillet 27, 2026, 7:31 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/14 "2026-07-27T19:31:04Z")
Merci pour la PR 🙂 Je t’ai fais un retour : > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fast… as possible, make sure to review and check all of these items: > > \- \[x\] If your changes affect the code, did you write the tests? > \- \[x\] Are server tests passing with coverage? (\`cd server && npm run coverage\`) — Codecov requires \*\*100% coverage on lines changed in this PR\*\* \_(the new functions \`rebootHost\`/\`shutdownHost\`/\`isHostPowerManagementAvailable\` are at 100%; the new controller handlers and the added \`getInfos\` line are covered too)\_ > \- \[\] Did Cypress E2E tests pass? (\`npm run cypress:run\` from repo root, if UI changed) \_(left to CI)\_ > \- \[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) — en/fr/de complete > \- \[\] Did you test this pull request in real life? With real devices? \_(AMD64 test image being built for a real x86\_64 host running systemd)\_ > \- \[x\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (apidoc \`@api\` comments added for the two new endpoints) > \- \[x\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See https://github.com/GladysAssistant/v4-website — done in \`feature/reboot-shutdown-host-docs\` (EN + FR) > \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`)? \_N/A — no new device/service data, only two admin actions\_ > > NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open. > > \### Description of change > > Adds the ability to \*\*reboot or shut down the host machine\*\* running Gladys (Raspberry Pi, mini-PC…) directly from the \*\*Settings → System\*\* page — a frequently requested feature (\[forum\](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786)). > > Until now \`system.shutdown()\` only stopped the Gladys process; there was no way to power off / reboot the underlying host. > > \*\*Mechanism.\*\* The two actions talk to \`systemd-logind\` over the host \*\*system D-Bus socket\*\* (\`org.freedesktop.login1\` → \`Reboot\` / \`PowerOff\`, non-interactive), via \`dbus-send\`. No new npm dependency; the \`dbus\` package is added to both Docker images so \`dbus-send\` is present. > > \*\*Backend\*\* > \- \`system.rebootHost\` / \`system.shutdownHost\`: call systemd-logind through D-Bus. > \- \`system.isHostPowerManagementAvailable\`: best-effort capability check (Linux + \`dbus-send\` binary + system D-Bus socket), exposed in \`getInfos()\` as \`host\_power\_management\_available\`. > \- \`POST /api/v1/system/reboot\` and \`POST /api/v1/system/shutdown-host\` (authenticated + admin). The command is awaited so failures are returned to the client. > > \*\*Frontend\*\* (Settings → System) > \- New "Reboot / Shutdown host" card with a \*\*two-step confirmation\*\* (anti-misclick). > \- Buttons are \*\*disabled with a tooltip\*\* when the capability is unavailable, and the server error message is surfaced on failure. > \- Reboot button is orange (\`btn-warning\`), Shutdown is red (\`btn-danger\`), matching the app's button conventions. > \- i18n: en / fr / de. > > \*\*Docker\*\* > \- Install the \`dbus\` package in \`docker/Dockerfile\` and \`docker/Dockerfile.buildx\`. > \- Requires the host D-Bus socket mounted: \`-v /run/dbus:/run/dbus:ro\` (documented in the v4-website PR). > > \*\*Behaviour on a standard install\*\*: after a \*\*reboot\*\* the Gladys container comes back thanks to \`--restart=always\`; after a \*\*shutdown\*\* the machine stays off until powered on manually. If the host is not systemd-based or the socket isn't mounted, the buttons stay disabled. > > \*\*Tests\*\*: unit tests for the two host-power functions (D-Bus command + failure propagation), the capability check (Linux/binary/socket matrix), and the two new controller endpoints. > > \_Screenshots to be added.\_ > > > > \## Summary by CodeRabbit > > \* \*\*New Features\*\* > \* Added administrator host power controls in System Settings (reboot and shutdown) with two-step confirmations. > \* Added success/error feedback and clear messaging when host power actions are unavailable. > \* Added host power availability detection to automatically disable the controls when unsupported. > \* Added English, French, and German translations for the host power UI. > \* \*\*Bug Fixes\*\* > \* Improved user-facing error reporting when host power commands cannot be issued. > \* \*\*Chores\*\* > \* Updated container images to include the system tooling required for host power requests. Tu peux demander à Claude de me répondre 😂 ---
**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:** [Août 24, 2026, 12:09 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/15 "2026-08-24T12:09:35Z")
Salut tout le monde ! Ce sujet est désormais **en cours de développement**. Une PR a été ouverte pour ajouter les boutons d’arrêt et de redémarrage de l’hôte dans les paramètres Système : > > > \### Description > > Conflict-resolution branch for #2709 (\`callemand:feature/reboot…-shutdown-host\`), which had become \`dirty\` against \`master\`. This branch is the PR's head merged with the current \`master\`, with the conflict resolved — the feature itself is unchanged from #2709. > > \*\*The conflict\*\*: \`front/src/routes/settings/settings-system/SettingsSystemPage.jsx\`. Since #2709 was opened, \`master\` reorganized the System settings page into two thematic columns (system & maintenance on the left — updates, containers, logs, database upkeep; behavior preferences on the right) and added \`SettingsSystemKeepDeviceHistory\` / \`SettingsSystemTimeExpiryState\`. #2709 had added its \`SettingsSystemHostPower\` card to the old flat list. > > \*\*Resolution\*\*: keep \`master\`'s two-column layout intact, and place the host power card at the end of the left (system & maintenance) column, where it belongs thematically. No other file conflicted; the server-side changes (\`system.rebootHost\` / \`system.shutdownHost\` / \`detectHostPowerManagement\`, the two API routes, \`getInfos()\` fields) merged cleanly. > > Verification on the merged tree: > > \- \`npx eslint\` on the touched server and front files: no errors (5 pre-existing warnings from #2709, unchanged). > \- Prettier: both touched front files match the project style. > \- Server tests for the affected areas (\`test/lib/system\`, \`test/controllers/system\`): 259 passing. > \- \`npm run compare-translations\` on front: en / fr / de complete. > \- \`npm run build\` on front: succeeds. > > If the contributor would rather land the resolution on their own branch, this merge commit can be pushed to \`callemand:feature/reboot-shutdown-host\` instead and this PR closed. > > \## Forum > > Forum: https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786 > > \### Checklist > > \- \[x\] Tests pass: the system lib and controller suites pass on the merged tree (full \`npm run coverage\` and Cypress left to CI) > \- \[x\] Linter and prettier pass on both front and server > \- \[x\] No undocumented breaking change > > 🤖 Generated with \[Claude Code\](https://claude.com/claude-code) > > https://claude.ai/code/session\_01VrJCRi9if1kC9DVmDcS8sb > > \--- > \_Generated by \[Claude Code\](https://claude.ai/code/session\_01VrJCRi9if1kC9DVmDcS8sb)\_ N’hésitez pas à suivre la PR, à tester (optionnel, surtout pour les petites demandes) et à faire vos retours ici si besoin. ---
**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:** [Août 24, 2026, 12:59 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/16 "2026-08-24T12:59:37Z")
@Lokkye j’ai testé sur ma production et j’ai ce message : ![IMG_3225](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/6/86ebfe9546ce7a5db0dbedfee4bf138742bc013c.jpeg) J’ai une installation classique (même docker run que sur le site), donc ça représente bien l’utilisateur moyen Gladys 🙂 PS : j’ai lancé Fable dessus ---
**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:** [Août 28, 2026, 12:29 UTC](https://community.gladysassistant.com/t/demande-de-mise-en-place-dun-bouton-arret-et-redemarrage-du-raspberry/6786/17 "2026-08-28T12:29:23Z")