| Author |
|
judetf
Senior Member
Joined: January 23 2008
Online Status: Offline
Posts: 234
|
| Posted: March 25 2008 at 05:52 | IP Logged
|
|
|
I have a trigger configured for an Insteon Device Change, with an "on" value for a specified KPL button.
It works, except that it fires the event twice with just a single button press.
I found a recent thread that discusses this issue for Controllinc button presses, but the fix suggested doesn't seem to resolve my issue (setting the Boolean value for the trigger to be [LOCAL9] <> [LOCAL10]).
Based on what Dave wrote, I suspect that it has to do with problems with the links. I have created and recreated them a bunch of times as this was a new KPL (v1.65) that seems to work differently than my others (see a previous thread of mine), but I can seem to fix things.
Any help would be appreciated. I'm sure I could code around it with some variable check, but clearly that's not idea when the event log actually shows the event firing twice in rapid succession...
Thanks
jtf
Based on what I read
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: March 25 2008 at 09:09 | IP Logged
|
|
|
This may seem redundant but maybe you could test the KPL after unlinking all devices associated with the button and see if you still get the same results. If the results change then we may have a starting point.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
judetf
Senior Member
Joined: January 23 2008
Online Status: Offline
Posts: 234
|
| Posted: March 25 2008 at 09:35 | IP Logged
|
|
|
The only links on that button are to the PLC: one link with the PLC as a controller of the KPL-7 group (per Dave's suggestion on how to create controllable KPL buttons by creating one group for each numbered button on all KPLs), and link with the PLC as a responder to that button.
I'm not at home, so I can't test now, but when this first came up I removed the link to the PLC as responder to see if that helped and the trigger stopped firing entirely. As soon as I added it back I got the double-fire again. Tonight I will test removing the controller link and report back.
Thanks
jtf
|
| Back to Top |
|
| |
jbbtex
Senior Member
Joined: February 15 2007
Location: United States
Online Status: Offline
Posts: 181
|
| Posted: March 25 2008 at 14:57 | IP Logged
|
|
|
I think the first trigger is activated by the button press and the second is triggered by the group cleanup command that follows.
Change your trigger type to Group In and see if that takes care of the issue.
__________________
Brady
"Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity." - Gen. George S. Patton
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: March 25 2008 at 16:08 | IP Logged
|
|
|
If you still have a problem after trying Brady’s suggestion can you trap the PLC data at the same time. The trigger should see a Group and then a Cleanup for each button. On the Controlinc that would be a total of 6 receiveinsteonraw=02. I would think the KPL would behave similar.
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
judetf
Senior Member
Joined: January 23 2008
Online Status: Offline
Posts: 234
|
| Posted: March 25 2008 at 21:41 | IP Logged
|
|
|
Changing to Group In seems to have done the trick. I'm wary: I had been using Direct In without a problem, then that stopped working with the new KPL so someone suggested using Device Change and that _seemed_ to work until I started seeing duplicate firings.
So now this seems to work and I'll keep my fingers crossed.
Thanks once again for the assist.
jtf
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Trigger fires twice on KPL button press
