-
AuthorPosts
-
Anonymous
InactiveApril 17, 2009 at 3:10 pmPost count: 3I am trying to figure out how to link a button on my RemoteLinc to the EZServe so that I can use the button to initiate a macro. I have tried putting the RemoteLinc in link mode (with flashing LED) and then pushing the button on the EZServe, but this does not work.
Can someone please provide step-by-step instructions on how to link a RemoteLinc button to the EZServe?
Thank you!
InactiveApril 17, 2009 at 5:23 pmPost count: 1001I just linked my RemoteLinc button 5 to my EZSrve. Then defined two macros, one that turns on an ICON switch when button 5 ON is pressed and a second that turns the same ICON switch OFF when button 5 OFF is pressed.
Put the desired RemoteLinc button into linking mode by holding the ON button paddle for approx 10 seconds. The RemoteLinc will beep and the LED will flash when it enters linking mode. Now press and hold the Set button on the EZSrve until the LED on the RemoteLinc turns off, approx 10 seconds. The RemoteLinc button x is now linked to EZSrve. The RemoteLinc will time out to save battery life so this process should be done immediately.
The Macro definition requires the use of two hex digits in the
If Device: DRemoteLinc Does: 1105 for the button 5 ON
If Device: DRemoteLinc Does: 1305 for the button 5 OFFThe EZSrve Operating Guide in the Downloads section describes the sequence for entering the 1105/1305 values in the Does: field.
InactiveApril 18, 2009 at 2:14 amPost count: 3Thanks for your reply!
I held button 3 on the RemoteLinc until it beeped and the LED started blinking. I held the Set button on the EZSrve until the LED on the RemoteLine went out. So far, so good.
But if I go to the macro page, the dropdown list for the “If Device” does NOT list the RemoteLinc and does not allow me to enter anything myself. And where do I enter the hex code? All I have is a dropdown list for “Does” that also does not allow me to enter anything myself. I see in the manual that there should be an input field next to the “Does” dropdown list, but my page does not have this input field. Also, the manual says that the “If Device” can be edited, but my pages does not allow it – I can only choose what’s in the dropdown list.
I am using version 1.6 of the firmware (this is what the EZSrve came with).
InactiveApril 18, 2009 at 2:48 amPost count: 1001You need to add the RemoteLinc to EZSrve. Click on EZSrve Device Addition ICON on left side of screen (blue flood lights). On the Device Management screen, select Add New Device, enter a device name (I used DRemoteLinc), enter the RemoteLinc device ID: (located in the battery compartment under the batteries), and device Type: RemoteLinc. Click on Save. When the question is asked “Would you like to create an Insteon link?”, click on No.
Now that the RemoteLinc device has been added to EZSrve you should be able to go to Macros, the RemoteLinc device will be in the pulldown list of the If Device: field. Select the RemoteLinc device. From the Does: field pulldown, select Enter Command. Enter Command is now in the Does: input field. Click on keyboard Delete key to clear words Enter Command from Does: input field. Now you can type 1103 to define a Macro that will trigger from a button 3 ON press.
InactiveApril 19, 2009 at 2:50 amPost count: 3That worked perfectly! Thanks for the info…I always wondered where the RemoteLinc device ID was.
InactiveOctober 5, 2009 at 11:53 pmPost count: 10I’m wanting to do the same thing, want to create a Micro that controls a X10 device. All the directions for this were for Version 1.6. It doesn’t seem to work for V 2.05 and the Harmony Flash interface. Is there a method to doing that on this version?
Thanks,
InactiveOctober 6, 2009 at 12:39 amPost count: 1001The Harmony client is a Beta level. I will setup my RemoteLinc and see if an Action using the RemoteLinc button can be created under the Harmony client. It probably can be done under Harmony as that client is pretty far along but if not available under the Harmony client you can define the Action using the HTML interface. I will post back the results of the Harmony test.
Can you detail what the problem was attempting to do this with Harmony.
InactiveOctober 6, 2009 at 1:03 amPost count: 10I was using the flash interface in Mac OS, Safari, I wasn’t using the stand alone application. I was able to link the RemoteLinc to the EZSreve but couldn’t find it in any pull down menus and can’t find where to create Macros within the Harmony Interface. Is Actions just another name for Macros? (what I suspect) if so the device does not show up in the available devices.
InactiveOctober 6, 2009 at 1:52 amPost count: 1001The HTML interface I referred to is the EZSrve HTML interface. Not the stand alone SHN Utility. The HTML interface is what existed in V1 and continues to be available in V2. Type in the EZSrve IP address into the browser and you should get an HTML based login screen. I’m pretty sure you will be able to define the Action using the Harmony client once you add the RemoteLinc device to EZSrve.
Sounds like you did not add the RemoteLinc device to EZSrve if it does not appear in the device pulldown list. Linking the RemoteLinc to the EZSrve with the Set button makes it known to the internal PLM but does not result in the device being added to the devices known to EZSrve. From the initial Harmony screen left click on the upper left corner Icon which should display two options, one to add new Areas and one to add new Devices. Remember to put the RemoteLinc into linking mode (awake) so EZSrve will be able to talk to the device while it is being added.
The V1 Timers and Macros functions have been merged and significantly enhanced as Actions in V2.
InactiveOctober 6, 2009 at 5:58 amPost count: 10In the Harmony interface I clicked on add devices. Under desired action the white dot is on the “ADD – Unknown ID, pushbutton discovery” I give it a name then hit proceed. “Device Addition In Progress Please Wait . . .” comes up, then “push set button on desired device for 4 seconds” Then I push and hold button 3 on the RemoteLinc (button I want to program) and it starts flashing in 10 seconds and the LED on the EZSreve is flashing, the hold for 4 seconds part goes away leaving the “Device Addition In Progress Please Wait . . .” stays on and on and on and on and on, doesn’t go away. Have tried many times same results.
InactiveOctober 6, 2009 at 2:12 pmPost count: 1001I was not able to define the RemoteLinc device using the second add option, specifying a device name and the Insteon ID, under Harmony. Not sure if this is due to the lack of a Set button on the RemoteLinc. I was able to define the Remotelinc using Harmony by selecting the 3rd add option, specifying a device name, Insteon ID, and selecting the Smarthome RemoteLinc as the device type.
I was not able to define an Action that would trigger from a RemoteLinc button using Harmony. I was able to define an Action that triggers from a RemoteLinc button using the HTML interface. This particular Action triggers from RemoteLinc button 5 On (1105). The attribute value would be 1103 to trigger from button 3 On. The Action Effect 1 turns on an X10 device and after a 5 second delay Effect 2 turns the X10 device Off.
Be sure you have linked the RemoteLinc button of choice as a controller to the EZSrve as a responder. This can be done by creating a Scene where the RemoteLinc is the Controller and the EZSrve is the responder.
[attachment=1:2568065a]RemoteLincAction.JPG[/attachment:2568065a][attachment=0:2568065a]RemoteLincCondition.JPG[/attachment:2568065a]InactiveOctober 6, 2009 at 7:29 pmPost count: 10I have yet to see the logic in any of this. Once I see it, I will be able to work with it but now I’m just lost. I followed your example, I was able to create the G_RemoteLinc device and I used Button 3 to link and it saved. Here is my Action page. I don’t understand what the Value is so I used 2 as you had done. WK Bench Light is a X10 appliance module set at E01 which the EZSrev is able to control. Set the attribute to Status as in your example but it did give me an X10 command option.
[attachment=2:vvmrrfv1]screenshot_02.jpg[/attachment:vvmrrfv1]Here is the condition page setup as in your example. I’m assuming that if I get this to work at any point in time I would need to set up another action 1303 to turn the X10 module off.
[attachment=1:vvmrrfv1]screenshot_01.jpg[/attachment:vvmrrfv1]So I’m thinking this should, the way it is set up turn on the X10 module. It doesn’t.
Here is the scene I set up
[attachment=0:vvmrrfv1]screenshot_03.jpg[/attachment:vvmrrfv1]
Does the value in the first picture have something to do with the scene? I am new to this, thank you very much for your help.
InactiveOctober 6, 2009 at 9:17 pmPost count: 1001The Controller Unit number used in the Scene where the RemoteLinc is the controller has to be the RemoteLinc button (Group) number, 03 in this case.
For Insteon hardware to send a Group command sequence from one device to another the devices must be linked together. Smarthome uses the term Scene for this relationship. In its simplest form a Scene (also referred to as a Group) consists of a link record in the Controller device (RemoteLinc in this case) which points to a responder device. The link record also contains a Group number which corresponds to the button number on the controller. When you press RemoteLinc button 3, the firmware in the RemoteLinc searchs its link database looking for a link record that has a Group number that matches the button number that was pressed. If a link record with that button (Group) number exists the device address in the link record is the address of the responder device to be controlled. The responder device (EZSrve in this case) has a link record which contains the address of the controller device to which it should respond as well as a Group number that matches the button number in the controller. This is standard Insteon architecture. So far nothing is unique to the EZSrve. The same Scene would have to be established if a SwitchLinc, as a controller, is controlling LampLinc for example.
A Group command sequence sent from a controller to a responder contains the Group number of the button that was pressed and a command indicating what action to take. The value 1103 indicates an Insteon On command (0x11) and Group (button) number 03. The Action definition specifies the Device, the Insteon command, and the Group number which causes the Action to trigger. All the information has to match for the Action to trigger. The Scene (links) must exist for the Insteon hardware to send the Group sequence to begin with. In general if a controller does not have a link record defined for the specific button pressed, no commands are sent. There are some exceptions to this, there always are, but for this situation it is a requirement.
The Value of “2” for an X10 device in the Effects represents an X10 On command. A Value of “3” represents an X10 Off command. There is a chart in the EZSrve User Guide which contains the values for the various X10 commands.
Hope this helps. If something is not clear let me know. Also on the Smartlabs web site there is a rather old but still relevant Insteon Detail document that explains how the Insteon hardware works. Lots of new things have come down the road since that document was published, much of which Smartlabs (and Smarthome) consider confidential and proprietary but some of the new stuff leaks out. The Smarthome forum is a good forum to follow.
InactiveOctober 6, 2009 at 9:32 pmPost count: 10OK, that’s making a little more sense. I’ve got an appointment to get to so I can’t try this right away. One quick question, under Actions Attribute I have Status selected. Now that I know that the Value 2 means X10 on, I had an option under Attribute to put X10 command, why should I have Status there instead of X10 command? I’ll try all this, this evening when I get back. Thanks again
InactiveOctober 6, 2009 at 10:36 pmPost count: 1001The second option is X10Control and I don’t know when the X10Control option is required. Either produces the X10 commands in the tests I have run when the Effect device is X10.
-
AuthorPosts
- You must be logged in to reply to this topic.