I have an existing scene called "FrontDoor" that controls the entrance lights to my house. This scene contains an InlineLinc, plus a bunch of KPL secondary buttons.

 

I added the first RemoteLinc to my system, and one of its buttons controls that scene. Programmed fine.

 

A bit later, I went to add a 2nd RemoteLinc to the same scene. I kept getting 'Request Failed'. At first I thought the programming was simply timing out, however I now believe that ALL RemoteLincs in a scene must be in linking mode in order to add an additional RemoteLinc. Once I put BOTH RemoteLincs into linking mode, then added the new RemoteLinc to the scene, it worked fine.

 

Is this correct?

 

Thanks!!

Noticed something else interesting...

 

 

If I add 1 RemoteLinc to my scene, I notice that if I hit one of the KPL secondaries in the scene, it gives me the flashing LED indicating that it was unable to communicate with one of the other scene members.

 

If I add 2 RemoteLincs to my scene, not only will the KPL secondaries flash, but the RemoteLincs will as well when controlling the scene.

 

It almost seems to me that the RemoteLincs are being added as not only controllers to the scene, but also responders.

 

Is this correct?

 

Thanks!!

The RemoteLinc remotes, to save the batteries go to sleep and will not respond unless; as you found are in the Linking Mode.

Using HouseLinc Desktop. I also could not find mine; even though I added the 6 digit ID manually.

Some have indicated if you hold the Bright-Dim combination bottons for 10 seconds; it will also wake up. I tried that combo and it did wake up. Note this combo is also for turning on and off the beeper or LED. So if used do not use the Bright Button alone or the All OFF Button to get out of the mode. I also found it will time out in 4 minutes

Right, I understand that. That's not my issue...

Noticed something else interesting...

 

 

If I add 1 RemoteLinc to my scene, I notice that if I hit one of the KPL secondaries in the scene, it gives me the flashing LED indicating that it was unable to communicate with one of the other scene members.

 

If I add 2 RemoteLincs to my scene, not only will the KPL secondaries flash, but the RemoteLincs will as well when controlling the scene.

 

It almost seems to me that the RemoteLincs are being added as not only controllers to the scene, but also responders.

 

Is this correct?

 

Thanks!!

 

I am programming my second RemoteLinc today, and yes, I am seeing that as well. Each button I program has an Is Managed By entry.

 

The buttons on my ControLinc also have Is Managed By entries as well.

 

Another glitch, the dialog pertaining to putting the RL into linking mode only appears when I remove the RL from a scene. I never saw it when I added a button to a scene.

 

Thank you,

Rand

I am programming my second RemoteLinc today, and yes, I am seeing that as well. Each button I program has an Is Managed By entry.

 

The buttons on my ControLinc also have Is Managed By entries as well.

 

Another glitch, the dialog pertaining to putting the RL into linking mode only appears when I remove the RL from a scene. I never saw it when I added a button to a scene.

 

Michel has been emailing me, and has confirmed this is an issue that they will fix with their next update. Hopefully he'll post in this thread.

Hello All,

 

Apologies for a tardy reply.

 

Yes, this is indeed an issue due to our "simplification" methods which consider all "controllers" to be always on and able to respond. This issue has been logged as a bug and shall be fixed in the next release (if not sooner).

 

Thank you so very much for all your feedback,

With kind regards,

Michel

 

 

I am programming my second RemoteLinc today, and yes, I am seeing that as well. Each button I program has an Is Managed By entry.

 

The buttons on my ControLinc also have Is Managed By entries as well.

 

Another glitch, the dialog pertaining to putting the RL into linking mode only appears when I remove the RL from a scene. I never saw it when I added a button to a scene.

 

Michel has been emailing me, and has confirmed this is an issue that they will fix with their next update. Hopefully he'll post in this thread.