Author |
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: April 23 2008 at 08:12 | IP Logged
|
|
|
Before I start mucking about (love Jeff's phrase) I thought I'd check for advice first:
I have a KPL button set for home/away status, but we are finding that we often forget to hit that button when we get home. So I thought I would create a trigger for _any_ KPL or Switchlinc button press, and have that mean that we are home and run the home macro. (And I plan to disable that trigger once we get home, so that it's not running constantly.)
My question: what should I use for Trigger Type and Trigger ID? Only "Insteon Device Chg" seems to allow "any" as the ID, but I don't think that will work because I have macros and timed events that run if we are _not_ home, and I suspect they would cause a "Device Change" trigger to fire.
So, looking for advice on how to fire a trigger on _any_ button/switch press, but not on other PH-driven actions.
Thanks for any assistance.
jtf
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: April 23 2008 at 11:28 | IP Logged
|
|
|
You can check the trigger's temp variables for the source of the message (i.e. don't fire if it originates from anything other than that device).
Look here for details.
|
Back to Top |
|
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: April 23 2008 at 13:39 | IP Logged
|
|
|
Perfect. We may have a winner. I set my 'home' trigger to fire on Insteon Device Change, Any trigger ID, Any trigger ID number, and Any trigger value, and I set the Boolean field to:
case([TEMP4] when 4 then 1 else 0)
If all goes according to plan, it will only fire when I physically press a KPL/Switchlinc. This is based on Dave's statement that Temp4 value 4 = "Direct Command from device."
I have tested remotely and know that PH-based device changes do _not_ cause the trigger to fire. As soon as I get home I'll try pressing some random button and see if it fires.
Thanks!
jtf
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: April 23 2008 at 13:49 | IP Logged
|
|
|
jtf,
Tonys got you covered. If you need a little more detail, I would probably use the "Insteon Device Chg" trigger with [ANY], (Any), (Any) and place the following formula in the Boolean field:
[TEMP4] = 5 and ([TEMP9] between 17 and 24)
This will cause the trigger to only fire on incoming broadcast commands from switches (essentially button presses). I would then use the "ph_enabletrigger()" and "ph_disabletrigger()" functions to enable the trigger *only* when you're away and disable it as soon as you arrive home (essentially when the trigger fires...it will disable itself).
HTH,
Dave.
|
Back to Top |
|
|
judetf Senior Member
Joined: January 23 2008
Online Status: Offline Posts: 234
|
Posted: April 23 2008 at 14:04 | IP Logged
|
|
|
Fine, I'll do it your way instead of mine. You're just showing off b/c my post came in before yours did... ;)
Already had the enable/disable trigger functions added to the respective home/away macros that I run. The logic seems flawless. What could go wrong? (Can't wait to buy an Elk system and start putting it all together! I'm sure _nothing_ will go wrong then!)
jtf
|
Back to Top |
|
|