# Status badge "Summary of openings" **URL:** \ **Category:** Demande de fonctionnalités\ **Created:** [August 28, 2026, 10:19am UTC](https://community.gladysassistant.com/t/pastille-detat-resume-des-ouvertures/10732 "2026-08-28T10:19:09Z")\ **Posts on this page:** 5\ **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:** [August 28, 2026, 10:19am UTC](https://community.gladysassistant.com/t/pastille-detat-resume-des-ouvertures/10732/1 "2026-08-28T10:19:09Z")
Could we add to the status badge « Summary of openings »: - the ability to choose what you want to see appear: the open or closed elements. Indeed, when you leave the house, you want to know that everything is well closed, but if I’m too hot in the summer, I might want to check that everything is open ^^ - an option to display the list of elements in question by clicking on the badge! ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/b/0/b0e8acedb42d1b4285a4917f014250e2e8f61fb9.png) At my place, I see that something is open… but I don’t know what 😉 ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [August 29, 2026, 11:07am UTC](https://community.gladysassistant.com/t/pastille-detat-resume-des-ouvertures/10732/2 "2026-08-29T11:07:13Z")
I think there is a problem because I still have a discrepancy between my sensors and the result of this tablet. I checked, I currently have 4 open detectors and the tablet tells me 5. ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/8/2/82d7dfa3e9f1e1690935302cbd9c33c61a078fe3.png) ---
**Author:** ![prohand](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/prohand/32/15713_2.png) [@prohand](https://community.gladysassistant.com/u/prohand)\ **Post date:** [September 1, 2026, 12:00pm UTC](https://community.gladysassistant.com/t/pastille-detat-resume-des-ouvertures/10732/3 "2026-09-01T12:00:33Z")
I have the same problem on my end where I have nothing open but it still shows 1 open. ---
**Author:** ![quentins33](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/quentins33/32/22672_2.png) [@quentins33](https://community.gladysassistant.com/u/quentins33)\ **Post date:** [September 2, 2026, 11:26am UTC](https://community.gladysassistant.com/t/pastille-detat-resume-des-ouvertures/10732/4 "2026-09-02T11:26:36Z")
I confirm 🙂 it would be great to be able to see at a glance which element is still open. In the meantime, I’ve created a page that lists all my openings to quickly check which one is open 😅 ---
**Author:** ![valentinhttr](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/v/9de0a6/32.png) [@valentinhttr](https://community.gladysassistant.com/u/valentinhttr)\ **Post date:** [September 2, 2026, 12:15pm UTC](https://community.gladysassistant.com/t/pastille-detat-resume-des-ouvertures/10732/5 "2026-09-02T12:15:44Z")
Hello, I’ve dug into it: the chip count is correct, but the stored value is inconsistent across integrations. Gladys 5 introduced the convention [`OPENING_SENSOR_STATE = { OPEN: 0, CLOSE: 1 }`](https://github.com/GladysAssistant/Gladys/blob/c2d5a703f1faa26a5c47006d82dab6086a56cdeb/server/utils/constants.js#L269-L272), which is used by [the chip counter](https://github.com/GladysAssistant/Gladys/blob/c2d5a703f1faa26a5c47006d82dab6086a56cdeb/front/src/components/boxs/chips/ChipsBox.jsx#L235). This constant did not exist in Gladys 4, and three integrations store the opposite (open = 1): - **Z-Wave JS UI** : [`true → STATE.ON = 1`](https://github.com/GladysAssistant/Gladys/blob/c2d5a703f1faa26a5c47006d82dab6086a56cdeb/server/services/zwavejs-ui/lib/constants.js#L55-L67), reclassified as `opening-sensor` by [`refineCategory`](https://github.com/GladysAssistant/Gladys/blob/c2d5a703f1faa26a5c47006d82dab6086a56cdeb/server/services/zwavejs-ui/utils/refineCategory.js#L36-L39) - **Xiaomi** : [`MAGNET_STATUS = { OPEN: 1, CLOSE: 0 }`](https://github.com/GladysAssistant/Gladys/blob/c2d5a703f1faa26a5c47006d82dab6086a56cdeb/server/services/xiaomi/lib/utils/deviceStatus.js#L26-L29) - **Netatmo** : [`open_window === true → 1`](https://github.com/GladysAssistant/Gladys/blob/c2d5a703f1faa26a5c47006d82dab6086a56cdeb/server/services/netatmo/lib/device/netatmo.deviceMapping.js#L61-L67) (Zigbee2MQTT, Matter, and MQTT/Home Assistant, on the other hand, are compliant.) Result: an opening from these integrations and **closed** is worth `0`, so it is counted as always open. The most discreet case is Netatmo, which creates an “open window detection” feature by thermostat/thermostat head, invisible on dashboards and reset to `0` continuously → a “ghost” open. This matches your two cases (4 + 1 = 5, and 0 + 1 = 1). Note, it’s not always “+1”: conversely, a Z-Wave/Xiaomi sensor actually open is worth `1` and is **not** counted. A simple `-1` would therefore not fix anything. To confirm on your end: look on your devices’ page for an opening displayed as “Open” when it is physically closed. I think the fix is to align these three integrations with the constant… it remains to decide the fate of the values already in the database: without migration, the display remains false until the next state change, with migration, the conditions of scenes of the type “sensor = 1” change meaning.