# Tab for offline devices **URL:** \ **Category:** Ideas & Suggestions\ **Created:** [August 22, 2025, 6:11am UTC](https://community.homey.app/t/tab-for-offline-devices/142086 "2025-08-22T06:11:15Z")\ **Posts on this page:** 1\ **Showing post:** 15
**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:** [August 24, 2025, 2:35pm UTC](https://community.homey.app/t/tab-for-offline-devices/142086/15 "2025-08-24T14:35:10Z")
> [@John\_William\_Brekke](#): > > What if a device stops working but is stated as online in Homey? Homey doesn’t detect that on it’s own, which is silly. F.i. zigbee2mqtt has individual settings for both battery & mains powered devices, wich determines after how many hours of inactivity you’d like devices to be considered offline. But, there’s a very neat script you can run, it checks for last update values of all/selected sensors and you can send notifications with the results: > [@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/tab-for-offline-devices/142086)._