| Author |
|
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: July 17 2012 at 07:52 | IP Logged
|
|
|
The I2 setting causes PH2 to use the Extended ALDB command for writing link records in the RL2. The RF only devices did not implement the old Peek/Poke commands making the Legacy method invalid. I would reinit PH2 after changing the IEngine setting. Not sure that is necessary but better safe.
Yes, the Links tab is used as would be for any other device. Select the RL2 as the Current Device and add the PLM as Responder to each of the 8 Groups (1-8) in the Responders (of Current Device) section. The Blue Group column gets a definition for each Group number 1-8 (for the RL2 buttons). The Green Buttons column representing the PLM does not matter. You can set it to the Group number but the PLM does not look at that number to match the incoming messages from RL2. Hardware like a KeypadLinc uses the Button number to match a specific KeypadLinc LED but that has no applicability to the PLM.
Virtual Devices are not involved here. A PH2 Trigger is defined for the RL2 device, Trigger Type is Insteon Group In, Trigger ID Number is 1-8 to match the RL2 button Group number (see posts above as RL2 button Group numbers are a little odd), Trigger Value is the Insteon command to cause the Trigger. The RL2 (along with the other RF only devices) send multiple Group In messages so the Trigger will fire multiple times for each button press. There are various posts on the forum on how to Disable the Trigger after the first Group In to prevent the additional triggers.
__________________
Lee G
|
| Back to Top |
|
| |
MrGibbage
Super User
Joined: October 23 2006
Location: United States
Online Status: Offline
Posts: 513
|
| Posted: October 12 2015 at 10:23 | IP Logged
|
|
|
Real old thread here, but I am stuck. I was messing around with my RL2 (when will I learn?!?!?) Now it mostly doesn't work.
I have a trigger set up to run a macro for any insteon device change for my RL2. The device is in the PH DB. I have the trigger ID set to
(ANY) and the trigger value set to (ANY).
The first line of the macro is a usermessage
"Skip's RemoteLinc2 Button Pressed: " + ph_getvar_s(2,2)+ph_getvar_s(2,9)
Now, when I press either of the top two buttons, I have noticed that in the Insteon Explorer, I can see the traffic and I do get the user
message in the log. But if I press any of the other buttons, I see no traffic in the Insteon Raw Log, and I see no user messages. This was all
working yesterday and has been working for quite a long time. I suppose I could have broken it, but I don't see how. I was just going to add
some more actions to some of the buttons.
In the device tab, I do have it set as type 244A, Engine=I2 (not I2CS; what's the difference anyway?) And use ext for ALDB is checked.
Under types, I have 2444A, 8 ctrlr groups, 0 resp groups, DevCat=0, SubCat=18, MemTop=4096, db=linear.
Any ideas?
__________________
Skip
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: October 12 2015 at 20:33 | IP Logged
|
|
|
Skip,
It sounds as if the links in your RemoteLinc for all
the buttons (other than the top two) have been
trashed. If you're not getting anything in the Insteon
log showing the transmission being received, then the
RemoteLinc is not sending a command (the RemoteLinc
will ONLY send an Insteon command if its got a link
created for that button). It is not unusual for an
Insteon device to just "forget" some links (at least
it doesnt seem to be unusual for me).
Everything else about your config looks fine. The
easiest way to fix this problem is to go to the Links
tab in Insteon Explorer and make the RemoteLinc the
current device. Then check the Responders window and
make sure that link to the PLM exists for each of the
8 buttons (they should if this was working before and
nothing else changed). If all looks good, place your
RemoteLinc in linking mode and press the "Rebuild"
text on the Links tab. This will have PowerHome just
rebuild all the defined links in the RemoteLinc and
when complete, should resolve your problem.
Dave.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: RemoteLinc2
