deviceUpdated - source of change?

Is there anyway in the deviceUpdated method to determine the source of the update e.g. :

• Z-Wave
• Indigo UI
• Indigo Touch
• Plugin
• etc

I presume Indigo must know where the change happened otherwise it wouldn't invoke the method?

An example: A thermostat setpoint can be altered via the Indigo UI or a user manually adjusting the physical thermostat

Thought I would check before I started adding some more complex logic to work it out.

I think I’ve some logic on this somewhere.

I trigger on the incoming Zwave change to either mark a state or disable a trigger, can’t remember.

Then if deviceState also changes I know where from.

Something like that anyway. Can’t even think what I use it for or indeed if I still do!


Sent from my iPhone using Tapatalk Pro

[matt (support)]

Indigo currently doesn't track through its information pipeline the origination of events/actions. This is definitely on the feature request list though, as it would be handy it lots of situations: plugins, scripts, smarter conditionals, etc.

Peter's technique (catching the earlier, originating message and tracking it manually yourself) could definitely work in specific or limited scenarios, so that might be something to explore depending on what you are trying to do.

Thanks for the answers

Looks like the more complex logic route then; I will monitor the Z-Wave as suggest by Peter and I know when the plugin asks for something to be done or is asked to do something (via an action), so otherwise must be via the UI.