# Flow to identify not responding device **URL:** \ **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:** 4\ **Page:** 1
**Author:** ![Marcus\_Bitterling](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcus_bitterling/32/80103_2.png) [@Marcus\_Bitterling](https://community.homey.app/u/Marcus_Bitterling)\ **Post date:** [April 8, 2025, 7:45pm UTC](https://community.homey.app/t/flow-to-identify-not-responding-device/134307/1 "2025-04-08T19:45:01Z")
I am trying to make a flow to warn me when a device is not responding but does not show offline. For example my Aqara temperature sensor sometimes just stops sending data and the temperature and humidity level stays the same in Insights. The only way to notice this is regularly checking insights but this is time consuming. When these variables are used in flows, they still work but data is used from perhaps days or weeks ago because the data stays at the last known level. Is there a way to check if for example the temperature hasn’t changed for let’s say 12 hours? This would be an indication something’s wrong and a notification could be sent to the timeline. I’m trying to figure out a flow to do this but just can’t think of one. Does anyone have suggestions? Thanks ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [April 8, 2025, 7:49pm UTC](https://community.homey.app/t/flow-to-identify-not-responding-device/134307/2 "2025-04-08T19:49:36Z")
Maybe you can find some pointers in the **Related** section at the bottom of this topic. ---
**Author:** ![Marcus\_Bitterling](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcus_bitterling/32/80103_2.png) [@Marcus\_Bitterling](https://community.homey.app/u/Marcus_Bitterling)\ **Post date:** [April 8, 2025, 7:54pm UTC](https://community.homey.app/t/flow-to-identify-not-responding-device/134307/3 "2025-04-08T19:54:03Z")
That’s a great tip! Thanks 🙏 ---
**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")
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…