A script to check sensor last update

[Peter_Kawa]

Ah, so it’s a tag create/update error?
Hmmmm, what’s changed?
Can’t find anything here:

Tutorial: Migrating deprecated scripts - HomeyScript

[Derf_Brother]

thnx, got a good tip from Peter_Kawa

[Derf_Brother]

thnx, this works. I also see some follow up on the THEN. Hope something good comes from this

[Sharkys]

Not really, the problem is/was my misunderstanding of tag function - it do not return anything as Athom dev. said : “tag has no return value” - com.athom.homeyscript/app.js at 09d6d7397f7dcd6c001650aa7a1d3834d57734b6 · athombv/com.athom.homeyscript · GitHub

[Sharkys]

Both scripts updated

0.3b - fixed for THEN card (returning TEXT value), primary use-better use is for AND card though with variables/tag InvalidatedDevices / notReportingCount

General version

A script to check sensor last update

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…

Zigbee version

A script to check sensor last update

As there is for some time options to see Lastseen timestamp for Zigbee devices, here is the script for Zigbee devices only, which might be more accurate for Zigbee devices. Thanks @Caseda for your overview script Version 0.3 - updated for HomeyScript v. 3.5.1 Version 0.3b - fixed for THEN card (returning TEXT value), primary use-better use is for AND card though // Version 0.3b // Script checks LastSeen property of Zigbee device // Using 2 hours default threshold // Thanks Caseda for […

[Derf_Brother]

thnx. Zigbee 0.3b is working fine. Did not check the general 03.b

[Henk_Renting]

I love this script…

But I as well have the problem that some routers (powered devices) do not update their “last seen” when not used for a while. In my case only Ikea bulbs and sockets as well.
I would like to use the script mostly to report battery powered devices not reporting anymore because of a low battery (or failure of course).

Is it an option to include a/some line(s) in the script to exclude router devices, @Sharkys?
Or filter on router/end device?
I tried my best, but couldn’t find it…

[Sharkys]

@Henk_Renting

Is it an option to include a/some line(s) in the script to exclude router devices,

Added into version 0.4

A script to check sensor last update

As there is for some time options to see Lastseen timestamp for Zigbee devices, here is the script for Zigbee devices only, which might be more accurate for Zigbee devices. Thanks @Caseda for your overview script Version 0.3 - updated for HomeyScript v. 3.5.1 Version 0.3b - fixed for THEN card (returning TEXT value), primary use-better use is for AND card though Version 0.4 - added option to filter out routers and/or end devices // Version 0.4 // Script checks LastSeen property of Zig…

[Henk_Renting]

Did I already mention you are the best?
And the quickest…

Thanks @Sharkys!

[DaDa]

I’m getting a

Failed: Getting ZigBee state TypeError: Cannot read properties of undefined (reading 'getState')
    at checkZigbeeLastSeen (Test.js:32:39)
    at Test.js:106:21
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

———————————————————
✅ Script Success
↩️ Returned: "Error in retrieving ZigBee state"

and :32 reads
const result = await Homey.zigbee.getState();

Running a fully updated HP23. Did I miss something?

[Peter_Kawa]

This works @ Pro 2019, can you test it?

const result = await Homey.zigbee.getState();
log(result);

[Sharkys]

@DaDa

Did I miss something?

If you have this Yellow flag, you must recreate the script as you are still using old version of HomeyScript.
Read more on Tutorial: Migrating deprecated scripts - HomeyScript

Long story short - create new script and copy paste the script from the previous version.

[Sjoerd1]

’m making a mistake somewhere. I’m using version 0.4 but for all devices, I get: NaN-NaN-NaN, NaN:NaN:NaN. Invalid value for time?

Am I doing something wrong…? Additionally, the script now indicates that all sensors are OK. But there’s one sensor that hasn’t responded for 3 days. (that’s why I want to use this script)

[Sharkys]

Did you just copy paste the script and run it and with log scrolled up, share the screen, eg:

or

[Sjoerd1]

Thanks for taking a look. I copied the script exactly as is. I only changed the ReportingThreshold to 24. But even without that change, I’m still getting NaN-NaN-NaN.

[Sharkys]

Hm, interesting, Which Homey firmware version and HomeyScript you are on ?

Can you also go to Homey Developer Tools and launch :

Homey.Zigbee.getState();

And then copy here part like this one :

(if you want, obfuscate ieeeAddr)

[Sjoerd1]

Homeyscript 3.5.1 and Homey is now on 11.0.0. Updated this morning, was on 10.0.10. (Homey Pro 2019).

I get this error with the launch of ‘Homey.Zigbee.getState();’

[robertklep]

Should be Homey.zigbee.getState() (lower case ‘z’)

[Sjoerd1]

Ah! That worked indeed.

I don’t see any “lastSeen” like in your screenshot…

[Peter_Kawa]

@robertklep

Should be Homey.zigbee.getState() (lower case ‘z’)

Damn autocorrect, although it shouldn’t touch code blocks