# \[FeatureRequest\] No data sensor state **URL:** \ **Category:** Ideas & Suggestions\ **Created:** [July 7, 2025, 3:09pm UTC](https://community.homey.app/t/featurerequest-no-data-sensor-state/139388 "2025-07-07T15:09:24Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [July 7, 2025, 3:34pm UTC](https://community.homey.app/t/featurerequest-no-data-sensor-state/139388/2 "2025-07-07T15:34:48Z")
Unfortunately Homey (still) does not provide for a “consider device to be offline after x hours” detection, unlike zigbee2mqtt f.i. In the almost 5 years of using Homey, I’ve never seen any news on this, presumably Athom won’t “admit” the fact sensors can stop responding for whatever reason. So, it’s best to create checks yourself. You can use a timer, like If.. device Z value X has changed Then.. start or replace timer Y, duration 4h (4h just being an example timeframe) If.. timer Y has finished Then.. send warning: device Z value X didn’t change for 4h straight Or, a bit more sophisticated, use a cool script by @sharkys to catch them all: > [@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/featurerequest-no-data-sensor-state/139388)._