Does anyone have a script that summarizes broken Zigbee and Z-Wave devices?
This script shows âunavailableâ devices:
But I donât know if "unavailable"is the same like âbrokenâ.
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).
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.
You can try this flow below, script is included.
Itâs not 100% accurate, but helps me a lot to report on âsuspectâ devices.
Thank You @Peter_Kawa !
