What actions constitute "Last Activity At" in device/device driver

I have a WaterCop (Z_wave, mains powered) with a custom driver. The device itself has no built in feature to periodically report the connection is OK and the device is active, so I added one by creating a simple "basicGet" action.

My problem is the device code runs but does not update "Last Activity At" found on the device page.

Is sending the command "zwave.basicV1.basicGet().format()" not qualify as "activity" ?

Thanks
John

BTW I use bertabcd1234 excellent "Device Activity Check" to monitor my devices. Hence the need for triggering an activity on this device.

//_____________________________________________________________________
def connectCheck(){
	// updates lastactivity so App "Device Activity Check" will know its still communicating.
    zwave.basicV1.basicGet().format()
    log.debug "  connectCheck performed"
}

The last activity gets updated whenever an attribute is updated.

So in some of my drivers I have something in the parse method that will just updated a dummy attribute so that I can use that as a marker that the device is alive.

But if you are sending a basic get, and then add a sendevent in the handler method for the response to that message, the last activity at will get updated whenever it executes.

1 Like