# 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:** 6\ **Page:** 1
**Author:** ![Alex\_S1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alex_s1/32/79236_2.png) [@Alex\_S1](https://community.homey.app/u/Alex_S1)\ **Post date:** [December 11, 2024, 7:24pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642/1 "2024-12-11T19:24:36Z")
Hi all! Since the beginning with Homey I´m experiencing “unknown node” issues with z-wave devices. After not checking it for some time, I now ended up with 12 dead notes. For me there is no chance to find out which device isnt responding anymore or lost connection except checking every single device. Is there a possibility to create a flow that checks the availability of the devices periodically or on demand. For example: start flow → check all devices if available → report I didnt find anything similar in the forum and dont see a useful option in the homey flows. Thanks Alex ---
**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, 7:40pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642/2 "2024-12-11T19:40:39Z")
You can use this script for instance. Just comment out all unneeded checks: > [@\[Homey Pro\] overview script](https://community.homey.app/t/homey-pro-overview-script/77459): > > Homey Pro overview script Always wanted an overview of your current Homey? Because you are in the process of migrating to another Homey Pro, or just for the fun of it. Well that is what this very HomeyScript script is for. Feel free to share your results in this thread, as I do like to see every ones Homey too! (no sensitive data is shown) I’ve tried to make this overview script somewhat user friendly to use. The only thing you need is an Homey Pro (any version, besides Homey (Cloud)) and t… ---
**Author:** ![Alex\_S1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alex_s1/32/79236_2.png) [@Alex\_S1](https://community.homey.app/u/Alex_S1)\ **Post date:** [December 11, 2024, 7:52pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642/3 "2024-12-11T19:52:10Z")
Thanks, Peter. A nice script. Unfortunately, it only shows general information about how many are device are connected, not reachable etc. What I´m looking for is something that checks the availability of devices and let me know which one became unresponsive. ---
**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… ---
**Author:** ![Alex\_S1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alex_s1/32/79236_2.png) [@Alex\_S1](https://community.homey.app/u/Alex_S1)\ **Post date:** [December 11, 2024, 8:36pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642/5 "2024-12-11T20:36:30Z")
Thanks. Will check it but have not much hope as I´m not good in coding. ---
**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, 9:08pm UTC](https://community.homey.app/t/device-integrity-connection-test/123642/6 "2024-12-11T21:08:44Z")
I can’t test as I don’t own any z-wave devices. After reading it, I see it"s not protocol specific. Can you run the script, just to see what it returns? With this line, you can provide certain (parts of) device names you want to check on: ```auto // Include by regex device name.... if (!device.name || !device.name.match(/temperature/motion/lux/humidity/i)) continue; ```