| Author |  | 
      
        | Kremlar Newbie
 
  
 
 Joined: January 30 2007
 Online Status: Offline
 Posts: 37
 | 
          With normal switches, I'm able to check off the ScanDB checkbox in the device list, save, and PowerHome will read the links from my device and update the database.
           | Posted: August 02 2007 at 21:36 | IP Logged |   |  
           | 
 |  
 When I try the same thing with a RemoteLinc, PowerHome doesn't appear to do anything.
 
 How can I read existing links off a RemoteLinc?
 
 Thanks!
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | jbbtex Senior Member
 
  
 
 Joined: February 15 2007
 Location: United States
 Online Status: Offline
 Posts: 181
 | 
          You might try turning on "Allow link spidering."
           | Posted: August 02 2007 at 23:02 | IP Logged |   |  
           | 
 |  
 If it's already on, I don't know what to tell you.
 
 I did all the linking for my RemoteLinc via PH.
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | Kremlar Newbie
 
  
 
 Joined: January 30 2007
 Online Status: Offline
 Posts: 37
 | 
          Thanks for ther reply!
           | Posted: August 03 2007 at 07:09 | IP Logged |   |  
           | 
 |  
 I finally noticed the device got marked as comm failed for some reason.  Once I cleared that, it scanned the device.
 
 Thanks!
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Kremlar,
           | Posted: August 04 2007 at 21:10 | IP Logged |   |  
           | 
 |  
 The RemoteLinc is slightly different from other Insteon devices in that it is only recognizable when you've manually placed it in "link" mode.  This is presumably done in order to preserve battery life.
 
 What will normally happen is that PowerHome will periodically scan all "Active" devices to check for status and database changes.  When your RemoteLinc is not in "link" mode, these status requests will fail and after the number of failures has reached the "Max Failure" count, PowerHome will flag the device as Comm Failed and no longer attempt to communicate with it.  As you've found out, it's easy enough to recognize and fix by going to the "Devices" tab and checking for the reddish background in the Comm Failed column and placing a check in it to clear it.
 
 To prevent this, normally place a check in the "Disabled" column for the RemoteLinc.  When you need to program or scan the RemoteLinc for link changes, clear the "Disabled" column and place the RemoteLinc in linking mode so PowerHome can communicate with it.
 
 HTH,
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | jmvanden Newbie
 
  
 
 Joined: February 16 2006
 Online Status: Offline
 Posts: 16
 | 
          Dave,
           | Posted: August 10 2007 at 15:02 | IP Logged |   |  
           | 
 |  
 So here is a problem I've run into wiht the RemoteLink.  The linking capability has to be enabled in order for PH to communicate with it.  The problem is that hte remote goes out of linking mode in 4 min, so I can't write everything to it.  Have you found a way to get around that issue?
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | Kremlar Newbie
 
  
 
 Joined: January 30 2007
 Online Status: Offline
 Posts: 37
 | 
          In the past I've only created a couple links at a time, to make sure it fits in the 4 minute window.
           | Posted: August 14 2007 at 11:18 | IP Logged |   |  
           | 
 |  
 Someone mentioned that entering link mode by holding the BRIGHT and DIM buttons should keep it in link mode for a longer period of time, but I haven't tried that yet.
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          With the RemoteLinc, you've indeed got the 4 minute link restriction.  However, if you send the links to the remotelinc fast enough, it won't time out (it's not supposed to and has been my experience so far).
           | Posted: August 14 2007 at 16:03 | IP Logged |   |  
           | 
 |  
 The way it works is something like this: you've got the initial 4 minutes of link mode.  After the 4 minutes is up, you've got about 10 seconds to communicate with it.  If you don't communicate with it within 10 seconds, then you time out.  As long as you keep pounding commands into it within 10 seconds, the timeout continues indefinately.
 
 The trick is to just keep PowerHome sending all the RemoteLinc commands as quick as possible.  Set the "Poll Interval" to 1 and make sure that the list of "Pending Operations" are all RemoteLinc related (temporarily set other devices to "Inactive" if necessary).  This should allow you to write whatever is necessary to the RemoteLinc.
 
 Normally, you would keep the RemoteLinc flagged as "Inactive".  Otherwise, PowerHome will generally flag it as "Failed".  Create all of the links and link changes for the RemoteLinc.  Save the changes.  Place the RemoteLinc in "Link" mode.  Set the RemoteLinc as "Active" in PowerHome and save.  It should bang all the changes into the RemoteLinc.
 
 HTH,
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  |