# Zigbee Thermometer & Humidity Devices **URL:** \ **Category:** Flows\ **Created:** [February 6, 2026, 7:36pm UTC](https://community.homey.app/t/zigbee-thermometer-humidity-devices/150707 "2026-02-06T19:36:58Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [February 6, 2026, 9:47pm UTC](https://community.homey.app/t/zigbee-thermometer-humidity-devices/150707/4 "2026-02-06T21:47:43Z")
What’s the purpose if I may ask? Just curious as I don’t see it. I mean, when a room is around 20° for an hour, why would you need three updates reporting 20°? My guessumption is, most sensors are event driven, like, when some value changes past a threshold \> send update; mostly in order to extend battery life. If you want to keep an eye on (network) availability, there’s a nice Homeyscript you can use: > [@A script to check sensor last update](https://community.homey.app/t/a-script-to-check-sensor-last-update/63142/25): > > Updated script I posted above - added counter of non responding devices - eg, in case you would like to initiate some action based on number of not-responding devices - please note this is the version I’m using, so feel free to change relevant variables below the section // Filter devices to check Changelog : 0.1 - update - converting notReportingCount to a number - if you used previous version of script, delete tag by await tag(‘notReportingCount’, null);\* 0.2 - added filtering based on dev… --- _[View the full topic](https://community.homey.app/t/zigbee-thermometer-humidity-devices/150707)._