Missing source info at DeviceActionRanEvent

[cag014 731]

The source ID and source Type information are missing at DeviceActionRanEvent  (refreshstate)  -  5.171.15 (beta)

 

Previous version - 5.170.16

Please login or register to see this spoiler.

 

Hopefully will be fixed in next release.

[cag014 731]

 

OK, I think I figured it out.

You need to enable "Save events to History", then it works.

Is it possible to keep that source data even if "Save events to History" is disable.

I do need the data, but don't want to keep all devices in history....

 

 

Please login or register to see this image.

/monthly_2025_02/image.png.f52d13a837af5e2f5aaf5fc18b151423.png" />

Edited February 14, 2025 by cag014

[trob 7]

This behavior did not change in 5.171.15. It has been like that from the beginning, when we introduced event source data.
We will change it to include this data when "save events to history" is unchecked in 5.181 version.

[cag014 731]

3 hours ago, trob said:

This behavior did not change in 5.171.15. It has been like that from the beginning, when we introduced event source data.
We will change it to include this data when "save events to history" is unchecked in 5.181 version.

Currently when the device activated by UI or Yubi app then the sourceType sets to "User".  When the device activated physically by user the "DeviceActionRanEvent" not shown at all.

Is it possible to add identification when the device activated physically by user?

I mean (for example) when the user physically pushes On/Off the switch, to set the sourceType to "Physical" or any other suitable format for you.

It will be very helpful to identify how the switch activated (in LUA code) to set proper timeouts or execute other actions

Thank you

By the way this kind of identification exists in Hubitat (physical or digital) and makes the scenarios smarter.  (Not AI yet.... but we're moving there😀)

 

Edited February 17, 2025 by cag014

[trob 7]

1) When you physically push wall-switch, the flow is:
button->device->zwave radio->HC3 gateway->clientApp (DevicePropertyUpdatedEvent)

2) when you push button in web-UI/mobile app/use quickapp code/or any other client:
client->http request->HC3 gateway API->zwave radio->device   and then device reports it state changed in similar way as in 1) : device->zwave radio->HC3 gateway->client (DevicePropertyUpdatedEvent)

It's of course a bit of simplification, but currently DeviceActionRunEvent is more or less the part marked red - responsible for request from gateway to device, so it does not apply in first scenario. Gateway can not determine the moment when you push physical switch.
 

[cag014 731]

You could identify device property changed while no client requests submitted, means activated manually/physically.

Any how thanks for explanation... I'll try to catch "DevicePropertyUpdatedEvent" without "DeviceActionRanEvent" request. (Hopefully the events always come in consecutive order)

[cag014 731]

It does work... although I need in addition to filter the property "state" of the event.

example of the code

Please login or register to see this spoiler.