Active TopicsActive Topics  Display List of Forum MembersMemberlist  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin
PowerHome Programming
 PowerHome Messageboard : PowerHome Programming
Subject Topic: KPL button reverse status Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 13:04 | IP Logged Quote RichardL
I have been successful at implementing links for KPL button status control for scenes where the buttons come on or off together (ie. behave the same)

Example: I have 3 entrances to my kitchen area, each has a few KPLs, if I press the Kit-Scene-1 button at entry 1, the Kit-Scene-1 buttons at the other KPLs come on.

Question: can I setup a link to do the opposite? In this case, if I turn on Kit-Scene-1, can I turn OFF the Kit-Scene-2 buttons at the other KPLS?

Thanks.
Back to Top View RichardL's Profile Search for other posts by RichardL
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: December 30 2009 at 14:30 | IP Logged Quote grif091
Yes. The responder link record dictates what each responder device does in response to receiving an ON command. Set the Bright level (LD1) to zero in the responder link records you want to turn OFF rather than ON or ON to some lower bright level. A Bright level of zero causes the device to turn OFF when it receives an ON command.

__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 14:39 | IP Logged Quote RichardL
Sounds good.

Just to be sure - if I link one KPL button ("A") to another KPL button ("B"), set the bright level to zero, then when I turn on "A" will this turn off the KPL status button light on "B"?

If so, that would be awesone!

Thank you.
Back to Top View RichardL's Profile Search for other posts by RichardL
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: December 30 2009 at 14:56 | IP Logged Quote grif091
This is for different KPLs. Button A on KPL1 linked to button B on KPL2. With the proper link record value for Bright level the KPL button will turn OFF when it receives an ON command. This works the same across the Insteon device line. An ON command can be used to turn OFF a SwitchLinc, LampLinc, etc. This behavior is not limited to KPL buttons.

Some of the newer devices allow this setup to be established with manual Set button links. For most responders this can only be done with software that write the link record values, such as PowerHome2.


__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 15:25 | IP Logged Quote RichardL
I can't wait to try, since I have been programmatically using the Group Clean Up to manage KPL button status. It is slow, and can cause problems when folks start pressing buttons quickly.

One fear I have is this: if I turn on botton A, and it in turn turns off button B, but button B has a trigger associated to it, which runs a scene - will it execute an "off" to that scene?

Thanks.
Back to Top View RichardL's Profile Search for other posts by RichardL
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: December 30 2009 at 15:47 | IP Logged Quote grif091
Scene control does not propagate. Controller A (KPL1 button A) turning ON/OFF responder B (KPL2 button B) does not cause KPL2 button B to then become a controller and run button B Scene. Insteon does not work that way. The circular commands that could be generated by that type of response would be impossible to control.   A PowerHome trigger fires on a specific defined condition. A trigger that is fired when a Group command from button B is generated when button B is pressed On/Off does not fire when a Group command from button A of a different KPL is generated.

__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 15:51 | IP Logged Quote RichardL
Got it. That is good. Yes, I can see an infinite loop of links firing triggers that loop back to each other... No anarchy allowed!

Like usual thanks for the good info.


Back to Top View RichardL's Profile Search for other posts by RichardL
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 22:52 | IP Logged Quote RichardL
So here I am messing with the links. Yes, if I press a KPL button on, and the link has the Bright Level set to 0, the DEVICE will turn off.   BUT...the associated KPL button itself stays lit. This is what I am fighting. I have scenes that upon a KPL button press will turn on and off devices, but the KPL buttons stay lit. Via a trigger I then use PH.InsteonGroupCU to turn off those KPL button lamps - this works but it is very slow.

I setup a test with 2 KPLs:
I linked KPL-1 button 3 to KPL-2 button 6 and 7. Button 6 is set as Bright Level 0, button 7 is set at full Bright Level. These buttons come on and off in sync. I cannot reverse it. I would hope that if button 3 is off and button 6 is on, then if I turn on 3 then 6 will go off. If I press KPL-1/button 3 on, then KPL-2/Button 6 and 7 will always light up, or remain lit if they were previously on.

You can see the setup in the snapshots below.

Note: If I want to configure buttons on the SAME KPL to behave this way, I can, using the KPL Config tab. I must code using PH.InsteonGroupCU for OTHER KPLs to have their buttons reverse.

KPL-1 Properties:



KPL-2 Properties:



Please tell me I'm missing something!

Thanks for all.
Back to Top View RichardL's Profile Search for other posts by RichardL
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: December 30 2009 at 23:03 | IP Logged Quote grif091
Give me a few minutes to set up a test here.

__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 23:13 | IP Logged Quote RichardL
Take your time.

Thank you!
Back to Top View RichardL's Profile Search for other posts by RichardL
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: December 30 2009 at 23:39 | IP Logged Quote grif091
My apologies. This works on the KPL load button but not a KPL secondary button. Setting the Bright level to zero for button A turns the load and that button LED Off but setting secondary button 6 to zero does not turn Off button 6 LED. I ran this test on new KPLs. This characteristic may have changed on later KPLs but that does not help you any. I’ll dig out an old KPL and repeat the test to see if I was just wrong or this changed on newer KPLs. Either way this does not work for your KPLs. You will have to go back to the old way of PowerHome turning a secondary KPL button Off.

__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 30 2009 at 23:53 | IP Logged Quote RichardL
Bummer. The fact that button "A" - which is a load - will respond accordingly makes sense. Buttons B-H do not change status, even though their linked devices do.

I am using KPLs v1.4.

What I am doing with the PH.InsteonGroupCU commands in VBS routines works, but is painfully slow. Appx .8 second per KPL button. I have many buttons to control.

I am not sure as to what is causng the slows. Looks like a new thread to address that is in order. But, gotta hit the sack for that last day of work this year!

Thank you for the efforts and confirmations.

Happy New Year!
Back to Top View RichardL's Profile Search for other posts by RichardL
 
grif091
Super User
Super User


Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
Posted: December 31 2009 at 00:06 | IP Logged Quote grif091
All the KPL buttons you want to turn Off for a given event can be linked as responders to a PLC/PLM Group and issue a Group Off. That will turn them all Off at the same time (assuming good powerline communication) and the PLM will automatically followed up with Group Cleanup Direct commands to each button to insure they did turn Off. Standard Group processing. Would require a separate PLC/PLM Group for each combination of KPL buttons.

__________________
Lee G
Back to Top View grif091's Profile Search for other posts by grif091
 
RichardL
Senior Member
Senior Member


Joined: December 29 2008
Location: United States
Online Status: Offline
Posts: 165
Posted: December 31 2009 at 08:08 | IP Logged Quote RichardL
I just couldn't resist, and ran a test. That is a great solution! Just as the InsteonGroupCU works individually, so will a group - and it is fast.

I now have to get my PLM house in order, which is another matter...

THANK YOU!
Back to Top View RichardL's Profile Search for other posts by RichardL
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum