Jump to content

KPL toggle mode and sync issues


ThisIsTheWay

Recommended Posts

I am having trouble configuring a KPL in toggle mode the following scenario with one ceiling light and two other devices that are meant to control it.

- (A) SwitchLinc on wall direct wired to light 

- (B) RemoteLinc - two buttons ~ one set make (A) go on through a scene "ON (A)" and the other set to make (A) go off through a scene "OFF (A)"

- (C) KPL - one button in toggle mode needing to control on/off of (A)

 

The KPL is a controller and responded of "ON (A)".  and a responder to "OFF (A)"  Setting it up like these seemed to fix some sync issues I had when using the remotelinc then the KPL.  But when I use the SwitchLinc, it feels like the KPL is out of sync.  Sometimes it take multiple presses to get the desired action. 

I've added a new scene called "(A) HELPER FOR TOGGLE" and added (A) and the KPL to it.  These seems to have fixed the issue.  Is this all I needed to do to fix it?  If so, can someone please explain why it works?

 

Link to comment

Not sure I am following everything.  (it is late and I am not in the mood to think too hard at this point.)

My initial question: in what mode is your remotelinc?  If I recall correctly, it can be set to four-scene (two buttons on/off for each scene) or eight scene (eight buttons, all toggle on/off).

Setting this up will likely depend on how you have your remotelinc configured, and which buttons you are using to control the scene.

Link to comment

@oberkc I know the feeling.  I am quite tired as well. 

My remotelinc is eight scene.  I have one button set to control a scene that turns the light (A) on and another set to control a scene that turns the light (A) off. 

 

I wish there were some clear examples somewhere that would help me understand how to setup more complex cases. 

Link to comment
8 hours ago, uffy said:

My remotelinc is eight scene. 

This might cause some complications.  Since, in this mode, each button toggles between sending ON and OFF commands, hitting the button for the ON scene might turn it off half the time.  I don't recall, but the remotelinc might be configurable to be in "non-toggle" mode, much like a keypad button.  I would have to check the manual to be sure.  If so configurable, this might be a good idea for this application.  Alternatively, depending on your use for the other remotelinc buttons, you might also consider putting it into 4-scene mode.

8 hours ago, uffy said:

I wish there were some clear examples somewhere that would help me understand how to setup more complex cases. 

Have you seen the "cookbook" and wiki?

My initial thoughts would be to create a single scene, with all four devices (switchlinc, keypad button, remote button1, remote button2), all as controllers.  Configure the responder levels (ON, RAMP RATES) as desired, including the second remotelinc button ON level to >> 0 (or off).  Verify that the responder levels to each of the controller devices are configured similarly.

If you are having intermittent problems, I would initial consider communication problems.  It may not be a configuration issue.  When things work "sometimes", I tend to suspect interference with insteon communication.  

9 hours ago, uffy said:

The KPL is a controller and responded of "ON (A)".  and a responder to "OFF (A)" 

I would expect that this would result in the KPL not controlling the other devices when trying to turn them off.  What are your thoughts for setting it up this way?

As a rule, any given device can be controller only of a single scene.  It cannot be controller of multiple scenes.  Given this, you could create a bunch of scenes, one for each of the four devices, a single scene (with all as controllers) or somewhere in-between.  

Link to comment
On 12/3/2019 at 6:57 AM, oberkc said:

I don't recall, but the remotelinc might be configurable to be in "non-toggle"

Yes!  My RemoteLinc is in 8-scene non-toggle mode.  

 

I've had the RemoteLinc for years with all the scenes setup as follows.  Button A will control a scene that turns lights on Button B will control a scene to turn the lights off.  Same for for C/D. But, E and F control scenes that used to use the IRLinc to blast commands to my in-windows Air conditioner telling it to turn the AC temp down (button E) or AC temp up (button F).  For whatever reason, at the time, this made a lot of sense. Then G is a scene that locks the doors and turns off all the lights.  H is a scene that just unlocks the front door and turns on the foyer lights.

Link to comment

Okay. Assuming button a always sends on commands and button be always sends off commands? If so, I would create a single scene with button a, button b, switching to, and keypad button, all devices would be as controllers.  Ensure you remove them from any other scene in which they may be involved.

Verify proper response levels for each controller in the scene. Obviously, button b would not need to be concerned with responder levels, since it always sends an off command. If button b is configured and, set the responder levels to button b controller as zero, or off.

Link to comment
On 12/4/2019 at 12:11 PM, oberkc said:

Verify proper response levels for each controller in the scene. Obviously, button b would not need to be concerned with responder levels, since it always sends an off command. If button b is configured and, set the responder levels to button b controller as zero, or off.

Ok, so basically, I had not used my ISY in a long time and forgot to set the levels at each controller in a scene.  I thought the scenes levels defined each controller in the scene's levels (very silly mistake).  Also, I didn't logically appreciate this idea.  This means, I had multiple scenes for things that should have been in a single scene.  ie. ceiling light on/off fucntion being controlled by a remotelinc in non-toggle 8 button mode.  One button for on one & button for off.  = one scene for on & one scene for off.  This logic is bad.  I have since adjusted to One scene with both buttons and their responded levels being set inside the scene. 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...