matapan Posted January 18, 2012 Posted January 18, 2012 I have a Morninglinc with firmware v3A which I added a while ago. I could always lock and unlock the device by toggling the On Off state in the Admin Console. Having read the posting related to the purpose of the two nodes created for Morninglinc, I decided to create a new scene and add the Morninglinc device to the scene. During this operation of adding the device to the scene, the Admin Console will return a Communication Error. Both Morninglinc device nodes now have a red exclamation mark on their icons. The selected Morninglinc device node also appears in the scene, with the red exclamation mark. Yet, I can still toggle the device and lock/unlock the lock with no apparent problem. I believe I added the device following the procedure outlined in the Wiki, but there might be a possibility I added the device and removed existing links. I reset the device using the procedure outlined in the Morninglinc user guide. However, I'm not certain if the factory reset procedure actually worked - I was able to press the set button after the reset to toggle the lock still. Is this by design, or have I failed to factory reset the unit properly?
LeeG Posted January 18, 2012 Posted January 18, 2012 The MorningLinc Set button will continue to cycle the lockset after a normal Insteon Factory Reset of the MorningLinc. Unplug the MorningLinc for 15 seconds. Press and hold the Set button before plugging in. While holding the Set button pressed, plug in the MorningLinc. Hold the Set button pressed for a full 10 seconds after applying power. When the Set button is released the MorningLinc LED will flash bright. If the MorningLinc had been added to the ISY with the "erase existing links" option the individual MorningLinc nodes would not toggle the lockset with the On/Off buttons. Sounds like where the MorningLinc is plugged in there is a communications problem (the red !). Try moving it to a different plug location, perhaps closer to the ISY PLM. However, once you establish good communication and the Scene creation process works you may lose the ability to command the MorningLinc completely. This symptom is being evaluated by UDI. If you do lose the ability to control the MorningLinc, that is the individual MorningLinc nodes will no longer cycle the lockset with the On/Off buttons, the MorningLinc has to be deleted from the ISY, a Factory Reset performed and added back using Start Linking. This will restore the individual node operation. Do not add the MorningLinc to Scenes. For now trigger a Program with whatever button should control the MorningLinc and have the Program send On/Off commands to the individual MorningLinc node. Both On and Off commands work against either the On node or the Off node. I issue On and Off commands to the On node just to keep things simple.
LeeG Posted January 18, 2012 Posted January 18, 2012 It may be that once the communication problem (red !) is resolved MorningLinc Scenes will rerate fine. If not the MorningLinc nodes will no longer cycle the lockset and the Show Device Links Table will display a FF FF – FF FF for the first link record. If those symptoms exist the only recovery is to delete the MorningLinc from the ISY. Factory reset the MorningLinc and add it back to the ISY. I found that my solid failure to create MorningLinc Scenes no longer happens when I moved the MorningLinc further away from the ISY PLM. I was using the MorningLinc in my test bed which put the MorningLinc about 10 wire feet from the PLM. When I moved the MorningLinc to the other end of the house all my MorningLinc Scene creation problems disappeared. There is a timing problem which was resolved by moving the MorningLinc a few milli-seconds further way.
matapan Posted January 19, 2012 Author Posted January 19, 2012 LeeG: I'm not sure if what I am experiencing is a communication problem. I have no problem adding the device, nor do I have any problem toggling it as a device. The only time a communication error with the Morninglinc occurred is when I attempted to add the Morninglinc to a scene as a responder. Moving the Morninglinc closer to the PLM does not yield any different results. Same thing occurs: There's no problem adding the device, or toggling it as a device. Adding it to a scene causes the communication error to come up.
matapan Posted January 19, 2012 Author Posted January 19, 2012 LeeG: Thanks for the reply. I am curious if the factory reset procedure supplied with the product is actually accurate, if it does not remove the linkage to the lock itself. What constitutes a reset? If the links are removed in the ISY's device discovery process, does this permanently prevent the device from being used with the controller? I am perplexed with the Morninglinc's behavior and its inability to be added to a scene. Would a device events trace help illuminate what is happening during the add to scene process?
LeeG Posted January 19, 2012 Posted January 19, 2012 The link between the MorningLinc and the lockset is not an Insteon link. The lockset has information about the PLM from the sequence of lockset buttons and PLM Set button. This writes information in the lockset but not the PLM. That is why a Factory reset of the MorningLinc does not affect the ability of the lockset to accept an RF message (non Insteon) from the PLM from the Set button. Some folks (myself included) have had problems adding a MorningLinc to a Scene but it is not a communications failure that produces the red ! When that problem surfaces the MorningLinc nodes no longer accept Insteon commands from the PLM. Not everyone is experiencing the Scene problem. It was solid here until I moved the MorningLinc to more distant point in the house. Added a few milli-seconds to the communication between the PLM and the MorningLinc which bypasses the problem. You do not have that problem for if you did the MorningLinc nodes would no longer control the lockset. Once the red ! communication problem is solved you may see this problem. You can post a Scene create event trace with Device communications events selected. I feel certain it will show the MorningLinc is not responding at all rather than responding with unexpected information.
oberkc Posted January 19, 2012 Posted January 19, 2012 I have been having morninglinc issues as well. While I don't believe it is related to this problem, I offer it up as a data point... After my first morninglinc failed, smarthome replaced it with a second. It failed to work out of the box. It would not even pair with the lock. An interesting tidbit: Tech support folks likened the relationship between the morninglinc and lock as like that of a keyfob and lock. The lock views the morninglinc as, simply, another keyfob. It is not the same as an insteon scene.
oberkc Posted January 19, 2012 Posted January 19, 2012 I have been having morninglinc issues as well. While I don't believe it is related to this problem, I offer it up as a data point... After my first morninglinc failed, smarthome replaced it with a second. It failed to work out of the box. It would not even pair with the lock. An interesting tidbit: Tech support folks likened the relationship between the morninglinc and lock as like that of a keyfob and lock. The lock views the morninglinc as, simply, another keyfob. It is not the same as an insteon scene.
matapan Posted January 28, 2012 Author Posted January 28, 2012 After performing a number of factory resets, and moving the Morninglinc around, installing it next to the PLM, I decided to capture the logs, presented below. The first log is from the action of adding Morninglinc to the network. The second log is a capture of what happens when Morninglinc is added to a scene. Can anyone knowledgable about these traces tell me what is wrong here? Thanks. Morninglinc Device Add Log: Sat 01/28/2012 09:12:29 AM : [LNK-BGN ] 02 64 01 00 06 Sat 01/28/2012 09:12:42 AM : [LNK-STAT ] 02 53 M(01) gid=00 18.EF.7C 0F06 3A Sat 01/28/2012 09:12:42 AM : Linked: Linked 18.EF.7C.00 type=0F.06.3A Sat 01/28/2012 09:12:42 AM : [iNST-ACK ] 02 62 18.EF.7C 0F 28 0F 06 SET-MSB(0F) Sat 01/28/2012 09:12:42 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 28 0F SET-MSB(0F) Sat 01/28/2012 09:12:42 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:12:42 AM : [iNST-ACK ] 02 62 18.EF.7C 0F 2B F8 06 PEEK (F8) Sat 01/28/2012 09:12:43 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 27 2B A2 PEEK (A2) Sat 01/28/2012 09:12:43 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sat 01/28/2012 09:12:43 AM : [18 EF 7C 1 ] MorningLinc database accessible Sat 01/28/2012 09:12:43 AM : [18 EF 7C 1 ] Start : Adding device to ISY Sat 01/28/2012 09:12:43 AM : [18 EF 7C 1 ] Finish : Adding device to ISY was Successful Sat 01/28/2012 09:12:43 AM : [18 EF 7C 2 ] Start : Adding device to ISY Sat 01/28/2012 09:12:43 AM : [18 EF 7C 2 ] Finish : Adding device to ISY was Successful Sat 01/28/2012 09:12:43 AM : [All ] Writing 0 bytes to devices Sat 01/28/2012 09:12:43 AM : [LNK-BGN ] 02 64 01 00 06 Sat 01/28/2012 09:12:51 AM : ---- Initializing the linked devices ---- Sat 01/28/2012 09:12:51 AM : [18 EF 7C 1 ] Reading all links Sat 01/28/2012 09:12:51 AM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Sat 01/28/2012 09:12:51 AM : [18 EF 7C 1 ] Using engine version i2 for '18.EF.7C-On' Sat 01/28/2012 09:12:52 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:12:52 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:12:52 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:12:53 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 FF 01 A2 00 13 22 2E FF 00 00 00 Sat 01/28/2012 09:12:53 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:12:53 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:13:02 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:13:02 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 27 2F 00 (00) Sat 01/28/2012 09:13:02 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Sat 01/28/2012 09:13:03 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 FF 01 A2 00 13 22 2E FF 00 00 00 Sat 01/28/2012 09:13:03 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:13:03 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:13:12 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:13:12 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:13:12 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:13:12 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 FF 01 A2 00 13 22 2E FF 00 00 00 Sat 01/28/2012 09:13:12 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:13:12 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:13:17 AM : ---- All Linked Devices are now initialized ---- Sat 01/28/2012 09:13:17 AM : ---- Start: Generate Scenes from links ---- Sat 01/28/2012 09:13:20 AM : ---- End: Generate Scenes from links ---- Sat 01/28/2012 09:13:20 AM : ---- Initializing the linked devices ---- Sat 01/28/2012 09:13:20 AM : ---- All Linked Devices are now initialized ---- Sat 01/28/2012 09:13:20 AM : [All ] Writing 0 bytes to devices Sat 01/28/2012 09:13:20 AM : [All ] Writing 0 bytes to devices MorningLinc Add to Scene Log: Sat 01/28/2012 09:05:15 AM : [18.EF.7C-Off] Start : Adding to scene 'Garage Door Lock' Sat 01/28/2012 09:05:15 AM : [18.EF.7C-Off] Making 'Garage Door Lock' a Controller Sat 01/28/2012 09:05:15 AM : [MNG-LNK-RSP ] 02 6F 40 E2 3A 18 EF 7C 0F 06 3A 06 Sat 01/28/2012 09:05:15 AM : [18 EF 7C 2 ] Link 0 : 0FF8 [A23A13222EFF0001] Saving [A23A13222EFF0001] Sat 01/28/2012 09:05:15 AM : [18.EF.7C-Off] Finish : Adding to scene 'Garage Door Lock' was Successful Sat 01/28/2012 09:05:16 AM : [All ] Writing 8 bytes to devices Sat 01/28/2012 09:05:16 AM : [18 EF 7C 1 ] Using engine version i2 for '18.EF.7C-On' Sat 01/28/2012 09:05:16 AM : [18 EF 7C 1 ] Link 1 : 0FF0 [0000000000000000] Writing [00..............] Sat 01/28/2012 09:05:16 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:05:16 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:05:16 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:05:17 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 F7 01 00 00 00 00 00 00 00 00 00 Sat 01/28/2012 09:05:17 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:05:17 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:05:26 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:05:26 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:05:26 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:05:35 AM : [iNST-ACK ] 02 62 18.EF.7C 1F 2F 00 00 00 0F F7 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 01/28/2012 09:05:36 AM : [iNST-SRX ] 02 50 18.EF.7C 13.22.2E 2B 2F 00 (00) Sat 01/28/2012 09:05:36 AM : [standard-Direct Ack][18.EF.7C-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 01/28/2012 09:05:36 AM : [iNST-ERX ] 02 51 18 EF 7C 13 22 2E 11 2F 00 01 01 00 F7 01 00 00 00 00 00 00 00 00 00 Sat 01/28/2012 09:05:36 AM : [Extended-Direct][18.EF.7C-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 01/28/2012 09:05:36 AM : [Ext. Msg. Handler] Unexpected Response (i.e. DB range): ignored Sat 01/28/2012 09:05:40 AM : [18 EF 7C 1 ] Link 1 : 0FF0 [0000000000000000] *Failed Writing [00..............]
LeeG Posted January 28, 2012 Posted January 28, 2012 The ISY did not go back to I1 which it should have. What does Link Management | Advanced Options show for the link option. It should be Automatic.
matapan Posted January 28, 2012 Author Posted January 28, 2012 Wow! Thank you LeeG! The Link Management | Advanced Options was set to Device Reported. Changing it to Automatic, then adding the device back to the network enabled me to successfully add the Morninglinc to a scene. Really appreciate your help!!!
LeeG Posted January 28, 2012 Posted January 28, 2012 That is great news! Some devices report I2 but do not function in I2 as expected. The MorningLinc is one of those devices. Best to run in Automatic as the default unless trying to solve some other problem. Even then it should be restored to Automatic. After adding to a Scene check that the MorningLInc On and Off nodes will still cycle the lockset with the On and Off buttons.
oceanman93 Posted February 18, 2012 Posted February 18, 2012 I'm glad it is not just me. I had issues with my MorningLinc and ISY. I tried multiple factory resets and gave up so had SH replace it. The new one came and everything works like a charm. Haven't added it to a scene. I'll just use programs to be safe for now. Seems there is a growing pile of returned MLs at SH.
LeeG Posted February 18, 2012 Posted February 18, 2012 For the benefit of others who may Factory Reset a MorningLinc, the only recovery is to delete the MorningLinc from the ISY and add it back using the documented process of using Start Linking to register the device. This is due to the unique security requirements of the MorningLinc.
rmlinnovator Posted February 23, 2012 Posted February 23, 2012 I am having a similar problem. I am running the latest version of stable firmware on the ISY. I cannot add my morninglinc to more than 1 scene. If I do so I loose connectivity from the ISY. Any idea how to fix this. Programs work fine but I like scenes because they are faster.
LeeG Posted February 23, 2012 Posted February 23, 2012 Delete the MorningLinc from the ISY, Factory Reset the MorningLinc (this will not lose the ability of the MorningLinc Set button to cycle the lockset), add the MorningLinc back to the ISY using Start Linking, and the “keep existing links†option. Before adding the MorningLinc to any Scene, move the MorningLinc to a location distant from the ISY PLM. The MorningLinc will not have to stay in this location, only for adding it to Scenes. Add the MorningLinc nodes to whatever Scenes are needed. Now see if the Scene(s) with the MorningLinc node(s) as Responders will control the lockset. If so move the MorningLinc to whatever location was good for the MorningLinc RF signal to reach the lockset. The purpose of moving the MorningLinc to a distant location during Scene management is to increase the delay between the PLM and the MorningLinc. I was able to add both the Lock and Unlock nodes to a Scene using this technique. If this does not work post back.
rmlinnovator Posted February 23, 2012 Posted February 23, 2012 Ok Lee will try moving when adding to scenes. It is already pretty distant from my PLM but I will try taking it further maybe to an isolated circuit like the one in my bedroom. Also the Factory Reset thing is a bit weird on the MorningLinc. When continuing to hold the button when I replug the MorningLinc the light never comes on if I am holding the button. I just usually hold it for like 10 seconds then let go then the LED comes on. I hope I am resetting it. Can't really tell.
LeeG Posted February 23, 2012 Posted February 23, 2012 Holding the Set button for a full 10 seconds should factory reset the MorningLinc. A separate circuit is not the issue. The MorningLinc needs to be as many wire feet away from the ISY PLM as possible. There is a much less desirable alternative which I will describe if this does not work. I could not get my MorningLinc into more than 1 Scene, usually the first Scene would lose connectivity between the PLM and the MorningLinc. I moved the MorningLinc to the most distant part of the house and Scene management worked every time.
Recommended Posts