I'm using 5.1.0 and just received a new RemoteLinc2 (Firmware 36, i2 Engine), 8 scene, verified to be default toggle mode. Setting it up in Indigo has been an adventure.

A couple of issues I've discovered and narrowed down to what seem like 5.1 bugs... First, in Indigo the button pair numbering is reversed; button 1 in Indigo controls RL2 B, button 2 in Indigo controls RL2 A, Indigo 3=RL2 D, Indigo 4=RL2 C, Indigo 5=RL2 F, Indigo 6=RL2 E, Indigo 7=RL2 H, Indigo 8=RL2 G.

Second, with Keypad LEDs and I/O-Linc (the two I've discovered so far) toggling is not possible if linking is done through Indigo. For example, I have a I/O-Linc that controls a fireplace. I established the link through Indigo and RL2 button presses only send On commands. However, if I manually link the RL2 and the I/O-Linc, then RL2 button presses toggle between On/Off commands as expected. Same with trying to set up Keypad LED controls. BTW: when I did manual linking and then sync'd in Indigo, the button names were still reversed. Also, I had a 4 scene RL2 that worked fine in 5.0 and it now in 5.1 it has the same non-toggling issue with the Keypad LEDs.

Using Indigo to link the RL2 to dimmers and on/off switches appears to work fine--except for the previously mentioned button naming issue--the dimmers and switches toggle on/off, brighten/dim as expected.

We give some details on the strange button numbering scheme on our wiki article. Unfortunately, there isn't much we can do about it despite the fact that is can be quite counter intuitive when setting up.

The other issue sounds to me like you just have your RemoteLinc 2 set in 8 Button Non-Toggle mode, but you want it in 8 Button Toggle mode. The RemoteLinc manual has the steps on how to change between the modes. I've tried it here with a RemoteLinc 2 that is the same firmware version you have, and once the RemoteLinc is in the mode you want it works correctly. That is, the links Indigo adds work as expected given whatever mode the RemoteLinc is currently in. And you can change between the modes after the links are written -- the links don't really have anything to do with the mode.

Addendum: I just tried it with an I/O-Linc and I think I am seeing the problem you reported. I'll investigate further...

Matt... In trying to figure it out yesterday I verified the RL2 was in the toggle mode, which is the default. And it is toggling Dimmers and Relay switches. Sorry I missed the Wiki on the numbering.

In Indigo 5.1 when managing links for the RL2, in setting an I/O-Link or Keypad LEDs as the responder the only choices in the third drop down box are "To On" or "To Off", no On/Off or toggle option. I don't remember it being that way in 5.0. Though in linking an ICON On/Off Relay it gives the same two choices, either "To On" or "To Off" an the RL2 will toggle the relay switch.

thanks

The "To On" label is a bit confusing. That one really mean "To On" when the ON scene is executed and to off when the OFF scene is executed, where as the "To Off" option always means to turn off regardless of the scene on/off state.

Regardless, I'm able to reproduce the problem but only when I try to change an existing link. If I create a new link in the RemoteLinc to point to the I/O-Linc then it is defined correctly and obeys the RemoteLinc's toggle mode setting. If I edit an existing link though, then the link can end up with a bad leftover value which causes it to always turn ON even when the scene being executed is OFF (note when in toggle mode note the RemoteLinc alternates between sending ON and OFF scene commands).

I'll get that bug fixed in the next version of Indigo 5.1.

I'm getting a strange problem, but I think it's related.

I've setup Triggers based on the RL2 sending on/off/instant on/instant off commands. Initially, everything was working. By the time I got to group 3 for button D, I couldn't get the RL2 to activate the command in Indigo. Indigo clearly shows that the button was activated, but the trigger doesn't activate.

When I tried to use button 2 and button 1 (A and B), they stopped working. I've tried restarting the Indigo server and rebooting the machine itself, but now nothing works on the RL2.

Ideas? Suggestions? I'm running 5.1.1 on a MacMini server.

You need to describe in detail how you have the trigger configured, including any conditions and actions.

Sure thing.

The trigger is looking for the button to activate on the remotelink2. Any button. Condition is always. Action can be anything, but let's use a "beep the lamplinc" action as an example.

Indigo sees the button being pressed, and that's logged. But it's like the trigger doesn't do anything from that point.

Like I said, it was working until I got to button 3, and I'd programmed buttons 2, 1, and 4 without a hitch. It just stopped working after I'd cloned the button for 4 and started making the edits to button 3. Then, they all stopped working altogether. Very odd.

Is that enough, or am I missing something?

I rebooted both the server and machine, but still no luck. I did notice some delayed responses, but I figured that was due to packet collision within INSTEON and not Indigo.

I was actually meaning the exact details of the trigger - for instance, take a screen shot of each tab on the edit trigger dialog...

And perhaps a snap of the Edit Device dialog for the RemoteLinc.

Here ya go.

I don't see anything wrong with that trigger. And you're sure that button presses from that remote are showing up in the Event Log?

(please copy/paste what you see in the Event Log so we can get a better picture of what is going on)

Wow! I have Jay AND Matt's attention, now.

Here's the event log. So buttons 1-4 are programmed with triggers, similar to what I shared previously. I also setup a trigger for an "Instant-On" for button 4. Again, Indigo shows that the RemoteLinc buttons are coming on or off, but the trigger just doesn't respond. I've also verified that "Hide trigger executions in Event Log" is unchecked in each trigger. I'm a snob for logging, so I never check that.

One of the dogs decided to run through the house, so all the motion sensors started going off. Still, you can see how I'm not getting a response on those triggers.

Just for the hell of it, I made a direct link to a lamp with button 5, and it worked properly. I also created a brand new trigger for button 6, and that also didn't work. Again, buttons 2, 1, and 4 worked initially, then it all stopped when I attempted to program on button 3.

Another oddity, I created a Trigger for Button A to change variable RemoteLinc_A to true/false when button 2 is on/off, and it worked like a charm. It's just when I tell it to control an action group, it doesn't do anything.

This is running on Snow Leopard Server 10.6.8. I re-ran the combo update last night for 10.6.8 v1.1, just to make sure it's not an OS issue. This is a headless server. Not sure if that makes a difference, but it can sometimes be an issue with some things.

Select the Trigger in the main window. In the popup control directly above the "Execute Actions Now" button (bottom of the main window), what item is selected?

Upload (standalone operation without Indigo connected)

That's not right, is it?

OMG! I'm such a dork! I see what I did. I unchecked "Enable" thinking it was "Remote Display".

NEVERMIND! It all works ONCE IT'S ENABLED!


Thanks for helping!

I'm glad it is up and working now.