LeeG Posted January 16, 2012 Posted January 16, 2012 Vince UDI is working at recreating this. As of Sunday evening they had not been able to recreate using their MorningLincs. Both of my v3A MorningLincs have the problem. What is the firmware of your MorningLinc? Until a Scene is created the MorningLinc nodes will cycle the lockset by issuing On or Off commands to the node itself. Only after a Scene (sometimes more than one before the problem arises) is defined is communication lost. For now only the nodes themselves can be used until the cause is identified and resolved. Lee
Vince Posted January 16, 2012 Posted January 16, 2012 Hi Lee, The firmware on the MorningLinc is Rev 1. So if I want to use the RemoteLinc to operate the lock I'll need to program it manually? A bit off topic, do you know anything about the OutletLinc 2472D. ISY says it is an unsupported device. It will turn it on and off but it does not have the dimming feature. Is there a workaround?
LeeG Posted January 16, 2012 Posted January 16, 2012 Vince The rev1.0 is the hardware level of the MorningLinc. The Admin Console displays the firmware level on the 2nd line of the device screen just below the Node name in the right pane. What ISY firmware level is being used? OutletLinc device type was added in one of the 3.1.x Betas. In the Unsupported message there is a number x.yy. What is that number? I will check to be sure that device cat/subcat value is listed in the latest 3.1.16 beta. The only way to use the MorningLinc in a Scene at present is to manually link it. However, the ISY will not know about those link records and will overlay them if changes are made to the RemoteLinc subsequent to the manual links. Lee
LeeG Posted January 16, 2012 Posted January 16, 2012 Vince A safer alternative to manual linking would be to trigger a Program with the RemoteLinc button and issue an On or Off command to the MorningLinc node itself. This way there are no link records that the ISY is unaware of. If Control 'RemoteLinc-2 - 2' is switched On Then Set 'MorningLinc-On' Lock Door Else - No Actions - (To add one, press 'Action') If Control 'RemoteLinc-2 - 2' is switched Off Then Set 'MorningLinc-On' Unlock Door Else - No Actions - (To add one, press 'Action') EDIT: I have confirmed this works assuming the MorningLinc has been added back and no Scenes created
Vince Posted January 16, 2012 Posted January 16, 2012 Hi Lee, The morninglinc firmware is v 3.A The ISY firmware is 2.8.16 The unsupported message for the outletlinc is 1.33 I'm also having a problem when I click "Write Update to Device" for the remotelinc. I get error message [-200000/-51] Failed Writing Device Link - Remotelinc. Any thoughts on that? Does everyone have this many issues or is it just my inexperience? Lee, thanks for you patience and willingness to help the uninitiated like me.
LeeG Posted January 16, 2012 Posted January 16, 2012 Vince Beginning to think the world is picking on you? The Dual Band OutletLinc Dimmer is supported in the latest 3.1.16 Beta. There are a number of Insteon devices that were announced and released after the last offical release 2.8.16 became available. Nature of the beast. Not much the ISY can do until the devices becomes available and any differences or new features handled. Support for the new devices appear in the incremental betas. In a way it is a good thing that SmartLabs/SmartHome are continuing to add new devices and improve the ones currently available. The down side is trying to keep up with the new devices implies using Beta code for awhile. The beta images have been pretty good overall and UDI does a good job of resolving whatever surfaces and that is what the Beta process is for. UDI has announced it is targeting the next official release soon, perhaps by the end of the month. That is a target, not a hard date. Depends on how testing of the next image proceeds. I have found 3.1.16 stable for the main line Insteon functions if you are considering moving to 3.1.16 for OutletLinc support. The MorningLinc is an unknown at this point. A few folks have seen the issue but since UDI cannot recreate it is not a solid universal failure. The analysis is a work in progress. Lee
Vince Posted January 16, 2012 Posted January 16, 2012 Lee, The program worked perfectly. Thank you. Any thoughts on my problem writing to the device (RemoteLinc)?
LeeG Posted January 16, 2012 Posted January 16, 2012 Vince Sorry about that, I had read the previous information and forgot to respond to that point. The RemoteLinc sleeps to conserve battery power. While asleep it cannot receive any commands. Put the RemoteLinc into linking mode by pressing and holding Dim/Bright buttons until RemoteLinc LED blinks continuously. Now click on Write Updates to Device and they should go. When the updates are complete either press the All Off button to come out of linking mode or wait a few minutes until the RemoteLinc times out itself. Lee
LeeG Posted January 18, 2012 Posted January 18, 2012 Vince Regarding the problem where the Show Device Links Table displays FF FF ---- FF FF for the first link record, I was able to work around that problem by moving my MorningLinc further away from the ISY PLM. Not in physical distance but in the length of the wire run to the outlet the MorningLinc is plugged into. There is a timing issue with the MorningLinc which the added distance and slight delay (in milli-seconds) has resolved. I was able to create Scenes with the MorningLinc nodes as well as have a KeypadLinc button and RemoteLinc button as MorningLinc Controllers. Both the MorningLinc On node and Off node have to be added to the Scene to allow both On and Off commands to cycle the lockset Locked and Unlocked. Also there is a Responder option for the MorningLinc nodes when responders to a Scene. Click on the Controller name below the Scene name and be sure the MorningLinc Off node has the Unlock option set. Lee
Vince Posted January 18, 2012 Posted January 18, 2012 Thank you Lee. I'll try that when I have some time to work on it.
Vince Posted January 26, 2012 Posted January 26, 2012 Lee, Can you help me with a program to lock the door at 8 pm if it is unlocked. I'm still learning the logic but have not stumbled upon what I need to make this work. Thanks.
LeeG Posted January 26, 2012 Posted January 26, 2012 Vince The lockset does not communicate to the MorningLinc when the lockset is Locked/Unlocked with the lockset Keypad, key fob or manual knob. This means there is no reliable way of knowing the status of the lockset and MorningLinc at any given time. Thus the Program issues a Lock at 8:00 PM with no other condition. The lockset simply double beeps if it is already Locked or Locks when Unlocked. If Time is 8:00:00PM Then Set 'MormingLinc-On' Lock Door Else - No Actions - (To add one, press 'Action') Lee
Vince Posted January 26, 2012 Posted January 26, 2012 Simply elegant. I tried doing it at first with an "if" statement about if the door was not locked. Your solution seems to work fine. Thanks again Lee.
ScottAvery Posted March 28, 2012 Posted March 28, 2012 The individual On/Off nodes perform the same function when Insteon Direct commands are issued to either node. When the On node is a Responder in a Scene a Scene On will Lock the mechanism. When the Off node is a Responder in a Scene a Scene Off will Unlock the mechanism. Once a Factory Reset is done the MorningLinc will have to be Deleted and added using Start Linking with the 3rd link record option to reestablish ISY access to the MorningLinc device. This needs to be explained somewhere in easily located FAQ or wiki material. Either the Wiki search doesn't work or this important info is missing.
ScottAvery Posted March 28, 2012 Posted March 28, 2012 The program for the lock still works, but I can't get a button on a keypad linc to work in a scene. It shows up in ISY status as working (device toggles in status). So, I checked, and my device is showing FF code on diagnostics. How did the PLM lose authority? I installed it correctly with a reset. How often am I going to have to do this?
ScottAvery Posted March 28, 2012 Posted March 28, 2012 Actually, I guess adding to a scene broke everything. I deleted, reset, readded, tested (passed), added to scene, tested (failed)
ScottAvery Posted March 28, 2012 Posted March 28, 2012 repeated attempts yield same result. I will try with a 50 or 100 foot extension cord.
LeeG Posted March 28, 2012 Posted March 28, 2012 ScottAvery This will sound counter intuitive but try moving the MorningLinc as far away from the ISY PLM as you can when adding the MorningLinc nodes to a Scene. Once the MorningLinc has been added to a Scene with the result that the PLM can no longer command the MorningLinc the only recovery is to Delete the MorningLinc and add it back using the described Start Linking with keep existing links option. After that is done and confirmed the On and Off nodes will cycle the lockset, move the MorningLinc to a distant location before adding the MorningLinc nodes to a Scene. After each node is added to a Scene check that either MorningLinc node can still cycle the lockset. If it will a MorningLinc node can be added to another or same Scene. Once the MorningLinc nodes have been successfully added to the Scenes and the MorningLinc nodes will cycle the lockset the MorningLinc can be moved back to its normal plug point. The objective is to increase the wire feet distance between the ISY PLM and MorningLinc while adding MorningLinc nodes to Scenes. There is a timing issue where the MorningLinc will disable ISY PLM control over the MorningLinc if commands come too quickly during Scene definition. If moving the MorningLinc to a distant location during Scene creation does not work send me a PM and I will describe an alternative method. It can have far reaching implications if not done correctly so I would prefer not to describe it on the forum. So far moving the MorningLinc to a distant location has resolved the Scene creation problem for every user assuming the MorningLinc has lockset control before the move.
ScottAvery Posted March 28, 2012 Posted March 28, 2012 I read your advice previously and so thus mentioned using an extension cord (to add wire feet). The PLM and morning linc are already as far apart as possible in the house, and on different phases.
ScottAvery Posted March 29, 2012 Posted March 29, 2012 100 additional feet of wire did nothing. still can't add scenes. This has to be software correctable if the ISY is just sending links too fast.
ScottAvery Posted March 29, 2012 Posted March 29, 2012 200 feet didn't do anything either, but Lee's alternate solution worked on the first try. It IS software correctable, and SHOULD be corrected in the device driver code within the ISY so one doesn't have to do a manual workaround. How many years has this problem existed?
Michel Kohanim Posted March 29, 2012 Posted March 29, 2012 Precisely what is software correctable and how can you be so sure? The link between the doorlock and morninglinc is NOT accessible to ISY or any other programming interface. This is the only security feature for morninglinc. With kind regards, Michel
LeeG Posted March 29, 2012 Posted March 29, 2012 ScottAvery Based on the results of adding 200' I now suspect it has more to do with the number of Insteon devices on the circuit the MorningLinc is plugged into and where the MorningLinc is relative to those other devices. Best to move the MorningLinc to the end of the circuit with many Insteon devices on it. Each Insteon device is a repeater so the more the Insteon devices on a particular circuit the better the signal strength and the greater the delay in getting to the last device. The amount of time is milli-seconds but that is all it seems to take. Thanks for that information. It may be helpful to someone else with the same problem.
Recommended Posts