Jump to content

cannot link a morning linc


flemingmike

Recommended Posts

Posted

hi, i have my morninglinc talking to my door, but i cannot add to the isy. ive tried it in many different outlets with no luck. i am trying to add using start linking with keep found links. when i hold the set button for 3 seconds, the light flashes, then my plm makes a noise, but its not in my isy when i get back to the pc.

Posted

Okay. Follow these steps.

 

Factory reset the MorningLinc. This will NOT affect the link between the lockset and the MorningLinc.

 

Run Tools | Diagnostics | Event Viewer with Level 3 selected.

Click Start Linking

Register the MorningLinc with the Set button and select keep existing links

Click Finish

 

Actually I think Finish is clicked, then the link option of keep existing links is selected. Been too long since I registered my two MorningLincs

 

Post the event trace.

 

Many Insteon devices now require the 3.2.6 I2CS support. Have not seen anyone mention the MorningLinc requiring I2CS yet but it is possible. The Event trace will indicate that or whatever else is bothering the device add process.

Posted

I don't believe "keep existing links" makes any difference, either. My experience is that the relationship between the morninglinc and the lock is unaffected by anything insteon.

Posted

Wed 07/11/2012 10:00:54 PM : [LNK-BGN ] 02 64 01 00 06

 

Wed 07/11/2012 10:02:58 PM : ---- Initializing the linked devices ----

 

Wed 07/11/2012 10:02:58 PM : ---- All Linked Devices are now initialized ----

 

Wed 07/11/2012 10:02:58 PM : ---- Start: Generate Scenes from links ----

 

Wed 07/11/2012 10:02:58 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)

 

Wed 07/11/2012 10:02:58 PM : ---- End: Generate Scenes from links ----

 

Wed 07/11/2012 10:02:58 PM : ---- Initializing the linked devices ----

 

Wed 07/11/2012 10:02:58 PM : ---- All Linked Devices are now initialized ----

 

Wed 07/11/2012 10:02:58 PM : [All ] Writing 0 bytes to devices

 

Wed 07/11/2012 10:02:58 PM : [All ] Writing 0 bytes to devices

Posted

oberkc

 

You are absolutely correct as far as keep existing links not affecting the link between the MorningLinc and the lockset. Even a Factory reset of the MorningLinc does not erase the MorningLinc to lockset link.

 

However, keep existing links is critical for adding the MorningLinc to the ISY. The Start Linking Set button press establishes the link records which are needed for the PLM to be authorized to read and write to the MorningLinc. Very similar to the I2CS linking requirements. If erase existing links is selected such that the Set button link is erased, the MorningLinc will reject all further commands from the PLM. Part of the extra security the MorningLinc has to prevent an outside source from controlling the MorningLinc.

Posted

flemingmike

 

That sequence looks like the ISY has a record of the MorningLinc Insteon address already. Delete the MorningLinc address from the ISY, and repeat the steps. Make sure Level 3 is selected.

Posted

Move the MorningLinc to the PLM plug point and try again being sure Level 3 is selected. The MorningLinc device would be at the end of the defined nodes until the Admin Console is restarted

  • 1 month later...
Posted

I have a morninglinc rev 1.0 that was working fine with my ISY and lock until something happened recently and it just stopped responding. Did a factory reset and the device just seems to be shot.

 

They sent me a new morninglic rev 1.2 today. Tried to link it to the ISY and everytime I try this, it comes back saying it cannot communicate with the ISY. It does show the on/off address in my list of devices. After linking the module to the lock and confirming that it locks/unlocks with the set button, i tried sending on and off commands to it from the isy console and it actually works! but, everytime i restart the console, it comes up as a device the isy cannot communicate with. It also screwed up my "replace device with" as I wanted it to replace the old shot morninglinc. I no longer see the old morninglinc as an option to replace, and when restarted, the console still shows the address and not the old device name. Any changes to the rev1.2 that is preventing this from working?

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37k
    • Total Posts
      371.5k
×
×
  • Create New...