# Flow to identify not responding device

**URL:** <https://community.homey.app/t/flow-to-identify-not-responding-device/134307>\
**Category:** Questions & Help\
**Created:** [April 8, 2025, 7:45pm UTC](https://community.homey.app/t/flow-to-identify-not-responding-device/134307 "2025-04-08T19:45:01Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![PeterHa](https://avatars.discourse-cdn.com/v4/letter/p/94ad74/32.png) [@PeterHa](https://community.homey.app/u/PeterHa)\
**Post date:** [April 12, 2025, 12:33am UTC](https://community.homey.app/t/flow-to-identify-not-responding-device/134307/4 "2025-04-12T00:33:16Z")

</div>

Hi Marcus,  
there is a script available from Sharkys to identify devices which are not responding

> [@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/flow-to-identify-not-responding-device/134307)._