Psoy
September 7, 2026, 7:58pm
1
Hello everyone,
I would need a bit of help with this temperature probe:
It is well declared on Zigbee2mqtt. Here is what it exposes:
.
In Gladys, I retrieve information, but not the « Strobe Temperature ». The only one that comes up is the temperature measured at the housing:
Here is what Gladys retrieves in the Zigbee2Mqtt integration:
My question is: is it possible to retrieve « the probe temperature » in Gladys?
Thanks in advance
Will_71
September 7, 2026, 8:05pm
2
So you already have the Temperature and you want Probe_Temperature, is that right?
If that’s the case, yes, it’s easy to add. I can open a PR this week.
Psoy
September 7, 2026, 9:03pm
3
Good evening @Will_71
Yes, the temperature that is transmitted is the value measured by the box, but the temperature measured with the probe does not go back to Gladys. If you have time to make a PR, that would be great, thank you very much. I admit, I’m a bit overwhelmed with all these innovations with AI.
Will_71
September 7, 2026, 9:32pm
4
Oh don’t worry, it’s easy to add, you don’t even need AI
Will_71
September 11, 2026, 8:36pm
5
@pierre-gilles , the PR to add probe_temperature
master ← William-De71:feat/zigbee2mqtt-probe-temperature
ouvert 08:35PM - 11 Sep 26 UTC
### Description
Add a `probe` type to the `temperature-sensor` category, and … map the
Zigbee2mqtt `probe_temperature` expose to it — as found on the Excellux
[ZG-105NTH](https://www.zigbee2mqtt.io/devices/ZG-105NTH.html), a
temperature/humidity sensor with a wired external probe.
Forum: https://community.gladysassistant.com/t/manque-de-donnees-remontees-par-la-sonde-de-temperature-excellux-zg-105nth/10830
### Checklist
- [x] If a forum topic or GitHub issue exists, the description links it (`Forum: https://community.gladysassistant.com/t/...` or `Closes #...`)
- [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
Psoy
September 13, 2026, 7:17am
6
Hi @Will_71
Thanks for the PR.
So for it to be active, we need to wait for a new Gladys update, right?
Have a good day
Will_71
September 13, 2026, 7:46am
7
Yes, when @pierre-gilles has approved the PR.
Hi everyone!
This topic is now in development .
A PR has been opened to map the Zigbee2mqtt temperature probe (probe_temperature) to a dedicated type:
master ← claude/festive-sagan-r6xjqz
ouvert 02:44PM - 18 Sep 26 UTC
### Description
Conflict-free version of [#3103](https://github.com/GladysAssis… tant/Gladys/pull/3103) by @William-De71, whose branch is now `dirty` against `master`. This PR merges `master` into the original branch and keeps the original two commits untouched, plus one merge commit.
The resulting diff against `master` is byte-for-byte the same as #3103 (10 files, +111/-5):
- Add a `probe` type to the `temperature-sensor` category (`DEVICE_FEATURE_TYPES.TEMPERATURE_SENSOR.PROBE`), for the external wired probe of a device that already reports its own ambient temperature.
- Map the Zigbee2mqtt exposes `probe_temperature` (Excellux ZG-105NTH family) and `temperature_probe` (Tuya alias, e.g. TZ-ZT01_GA4) to that feature, Celsius, range -100 to 150 (same as the plain `temperature` expose).
- Exclude `probe` from `getTemperatureInRoom`, so a fridge or outdoor probe does not skew the room average, with a regression test.
- Add en/de/fr labels under `deviceFeatureCategory.temperature-sensor.probe` and the thermometer icon.
- Document the `decimal` vs `probe` boundary in `docs/specs/water-heater.md` (tank temperature stays `decimal`).
**Conflict resolved:** `server/test/services/zigbee2mqtt/exposes/numericType.test.js`. Master added a "ZLinky_TIC apparent power features" `describe` block (#3097) at the same spot where #3103 added its "Temperature probe features" block. Both blocks are kept.
**Review of #3103:** approved on my side. The type is generic and correctly scoped, the label works with the Zigbee2mqtt discover page (it names features from `deviceFeatureCategory[category][type]`), the range matches the existing `temperature` expose, and the room-average exclusion is tested. Only residual: two comments (on `PROBE` in `constants.js` and in `getTemperatureInRoom.js`) still list "a tank" as a probe example, which contradicts the spec paragraph that keeps tank temperature on `decimal`. Cosmetic, not blocking; left as in the original PR.
### Related request
Forum: https://community.gladysassistant.com/t/manque-de-donnees-remontees-par-la-sonde-de-temperature-excellux-zg-105nth/10830
### Checklist
- [x] If a forum topic or GitHub issue exists, the description links it (`Forum: https://community.gladysassistant.com/t/...` or `Closes #...`)
- [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 — ran the two affected server test files locally (27 passing); full suite and Codecov run in CI. No UI component change, only i18n and an icon map entry.
- [x] Linter and prettier pass on both front and server (`npm run eslint`, `npm run prettier`) — run on the touched files.
- [x] No undocumented breaking change
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01FLtaLbpTnNLvY9goimbaS4
---
_Generated by [Claude Code](https://claude.ai/code/session_01FLtaLbpTnNLvY9goimbaS4)_
Feel free to follow the PR, test (optional, especially for small requests), and share your feedback here if needed.
Psoy
September 22, 2026, 8:48pm
9
Good evening @Will_71
Thank you so much, the temperature probe recovery is working well