# Looking for a script that summarizes broken Zigbee and Z-Wave devices **URL:** \ **Category:** Questions & Help\ **Created:** [March 2, 2024, 6:16am UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325 "2024-03-02T06:16:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Joep\_van\_Andel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep_van_andel/32/71049_2.png) [@Joep\_van\_Andel](https://community.homey.app/u/Joep_van_Andel)\ **Post date:** [March 2, 2024, 6:16am UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325/1 "2024-03-02T06:16:57Z")
Does anyone have a script that summarizes broken Zigbee and Z-Wave devices? ---
**Author:** ![DirkG](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dirkg/32/118897_2.png) [@DirkG](https://community.homey.app/u/DirkG)\ **Post date:** [March 2, 2024, 11:02am UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325/2 "2024-03-02T11:02:31Z")
This script shows “unavailable” devices: > [@\[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… But I don’t know if "unavailable"is the same like “broken”. ---
**Author:** ![Caseda](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/caseda/32/138695_2.png) [@Caseda](https://community.homey.app/u/Caseda)\ **Post date:** [March 2, 2024, 11:27am UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325/3 "2024-03-02T11:27:50Z")
If you know a good way to determine how a device shows it is “broken” we might be able to create something, as just “not reported in a day” (which already has a few HomeyScripts for that purpose) doesn’t mean it is broken, example, I have Aeotec doorsensors that only sends the battery level if it has changed from previous value, and some doors I don’t open in the winter so don’t send anything for several weeks. The “I’ve woken up” signal isn’t available for anything besides the Homey Z-Wave core. Zigbee does have a “last seen” option, but that is also for only Homey Pro (early 2023), it isn’t there for the older versions (I believe). It is pretty hard to determine if a device is broken yes or no with Homey, especially with the mix of battery and mains powered (and for Z-Wave also FLiRS devices). Also for Z-Wave the “Unavailable” tag doesn’t always mean it is broken (99.9% of the time it doesn’t). ---
**Author:** ![Joep\_van\_Andel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep_van_andel/32/71049_2.png) [@Joep\_van\_Andel](https://community.homey.app/u/Joep_van_Andel)\ **Post date:** [March 2, 2024, 4:02pm UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325/4 "2024-03-02T16:02:34Z")
Hmmmm @Caseda I didn’t knew that. Too bad, I hoped that every device would send a “heartbeat” every day, that would have made it a lot easier to check. And I know there is a lot to do about “broken”" devices. In general at this moment I don’t have a lot of “broken device” issues. But for example, a doorsensor didn’t report a door open doesn’t by definition mean the door isn’t opened but could also mean the device is broken. I am not a programmer, and not by far familiar with Homey Script and I copy pasted something and played around with the “last seen” option for Zigbee. This kind of idea works for me at this moment for Zigbee. But it is … how shall I call it, amateur “rumbling in the margins”. And I had hoped that there was a somebody who created a nice clean script voor Zigbee aswell as Z-Wave. ---
**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:** [March 2, 2024, 8:05pm UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325/5 "2024-03-02T20:05:47Z")
You can try this flow below, script is included. It’s not 100% accurate, but helps me a lot to report on ‘suspect’ devices. > [@The Flow Exchange(r) - Exchange Your Flows with Others!](https://community.homey.app/t/the-flow-exchange-r-exchange-your-flows-with-others/68981/13): > > Sensor (or any device) Connection Check. Sometimes, you’ll discover a sensor or other device doesn’t report it’s status or value anymore, but it does NOT notify you of being offline… Well, this flow checks the, most recent update time of your sensors. You can run the flow every day, twice a day, just add or remove a time triggercard. The ‘inactive time’ can be edited as well (24hrs as default) and you can choose to not send notifications when all sensors did report inside the ‘inactive time… ---
**Author:** ![Joep\_van\_Andel](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep_van_andel/32/71049_2.png) [@Joep\_van\_Andel](https://community.homey.app/u/Joep_van_Andel)\ **Post date:** [March 3, 2024, 7:17am UTC](https://community.homey.app/t/looking-for-a-script-that-summarizes-broken-zigbee-and-z-wave-devices/105325/6 "2024-03-03T07:17:09Z")
Thank You @Peter_Kawa !