# Be notified if a container stops responding **URL:** \ **Category:** Demandes livrées\ **Tags:** feature-core\ **Created:** [November 3, 2022, 6:09pm UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652 "2022-11-03T18:09:06Z")\ **Posts on this page:** 9\ **Page:** 1
**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, 2022, 6:09pm UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/1 "2022-11-03T18:09:06Z")
Today I’m asking for features left and right!! The day before yesterday I woke up and my button to open my roller shutter had no effect ☹ After going to check over SSH what was going on (`docker ps -a`) I saw that my z2m container had been stopped for several hours. I have no idea why (Gladys update?). I was wondering if it would be possible to be notified, either in the dashboard / or via a scene with a Telegram message, that one of the containers is OFF. What do you think? ---
**Author:** ![lmilcent](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lmilcent/32/7023_2.png) [@lmilcent](https://community.gladysassistant.com/u/lmilcent)\ **Post date:** [November 6, 2022, 1:27pm UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/2 "2022-11-06T13:27:43Z")
Try looking on the Node-RED side, it should be doable! Zigbee2MQTT is independent of Gladys, and so are the updates. And I can confirm there was a recent one for Z2M. ---
**Author:** ![damalgos](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/d/e274bd/32.png) [@damalgos](https://community.gladysassistant.com/u/damalgos)\ **Post date:** [November 7, 2022, 9:00am UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/3 "2022-11-07T09:00:23Z")
Hello, Indeed, Node-RED can solve your problem. For example, you can run a curl against Gladys and verify that it responds with a valid HTTP response (e.g., 200) ---
**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 7, 2022, 9:55pm UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/4 "2022-11-07T21:55:25Z")
Okay, I’ll take a closer look, thanks for the advice! ---
**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 7, 2022, 9:56pm UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/5 "2022-11-07T21:56:09Z")
You’re speaking Chinese to me, but if I’m not any dumber than anyone else I should be able to find it with this curl 👌😁 ---
**Author:** ![damalgos](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/d/e274bd/32.png) [@damalgos](https://community.gladysassistant.com/u/damalgos)\ **Post date:** [November 8, 2022, 7:31am UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/6 "2022-11-08T07:31:27Z")
I’ll make it simpler 😃 curl is just a command that lets you request a web page (like your browser does). The difference is that it’s all command-line. So you can get the status of the request (whether it worked or not) typically you’ve already seen 404 Not Found (that’s an HTTP response). Usually on a GET (simply retrieving a page) you get a 200 code 🙂 But yes on Node-RED you have very simple things like you can probably use (http\_requests) ---
**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 8, 2022, 1:08pm UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/7 "2022-11-08T13:08:12Z")
Thank you very much for those clarifications @damalgos ! ---
**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:39am UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/8 "2026-10-29T10:39:08Z")
Hi @guim31! You can be notified when a container stops. Two integrations from the catalog expose the status of containers, usable in a scene: - **Docker** (PhilippeMA, v2.0.0), if Gladys talks directly to the Docker engine - **Portainer** , if you already go through Portainer The status (running or stopped) becomes a device. A scene of the type « if Zigbee2MQTT is stopped → send a message » covers the wake-up without a shutter. I’m filing this topic under « 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:54am UTC](https://community.gladysassistant.com/t/etre-prevenu-si-un-container-ne-repond-plus/7652/9 "2026-10-29T10:54:14Z")