# Device integrity/connection test **URL:** \ **Category:** Questions & Help\ **Created:** [December 11, 2024, 7:24pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642 "2024-12-11T19:24:36Z")\ **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:** [December 11, 2024, 8:31pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642/4 "2024-12-11T20:31:31Z")
The author wrote in that topic it’s is pretty complicated to check the state of Homey z-wave. But I was under the impression it could list unreachable nodes f.i. There’s a nice script, aimed at zigbee, which checks the _last updated_ flag, which can be a good indicator of a device still being alive Maybe you can adjust it, to have it check z-wave devices: > [@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/device-integrity-connection-test/123642)._