LeeG

Exactly right on all points.

The Serial Port connection between PLM and ISY has a theoretical limit of 50'. Ethernet connection between the ISY and a modem/router can be several hundred feet. Don't remember the actual max as it varies by speed and type of cable. Perhaps some insulation around the around the PLM and ISY as they both generate heat. However, check frequently in the beginning to be sure they are not getting too hot with no air circulation. Getting too hot could be terminal for either one.

This Program will not run on its own because the variable in the If is an Integer variable. Integer variables never trigger Programs. It can be set to Run at Startup or another Program with Run at Startup can run this Program. Do not see an advantage of having a second program.

Use a time based Program trigger that locks the lockset regardless of MorningLinc Status. Because the MorningLinc Status is so unreliable regarding the actual lockset status UDI may have chosen not to allow its use in Programs as a Condition. That is only speculation.

Manual Set button links should not be done. The ISY is not aware of them and will eventually erase or overlay the Set button link records. With a Set button link the ISY is not notified of the button press so it is not aware of responder state changes. The correct way is to define an ISY Scene, adding the appropriate Controllers and Responder. More than one Controller can be added to an ISY Scene. Controllers are normally added as Scene Controllers so the ISY will cross link them as appropriate so that all Controllers are in sync regarding their status LEDs. It is normal to have a different ISY Scene for each Controller button unless the responders are all the same and only On Level and/or Ramp Rates are different. For example, button A turns On a set of responders to some On Level and Ramp Rate. If button B Is turning on the same set of responder but to a different set of On Level and/or Ramp Rate values, the same ISY Scene can be used for button A and button B. Each Controller in an ISY Scene can have different On Level and/or Ramp Rate values for its responders.

The v.00 indicates the KeypadLinc was added by selecting the specific Device Type from the pulldown. Delete the KeypadLinc and add it back using Auto Discover so the KeypadLinc firmware will be retrieved during the device add process. Then post the KeypadLinc firmware. For a Secondary KeypadLinc button on the same KeypadLinc to affect the load button A On Level the firmware must be 2D or above.

Sorry for my confusion about the configuration. I was thinking there was a second device involved. What is the KeypadLinc firmware level? It is displayed at the end of the second line in the right pane when the KeypadLinc button A is selected. Some levels of KeypadLinc firmware do not support a Secondary KeypadLinc button affecting the load button the way you want.

Run Tools | Diagnostics | Event Viewer with Level set to Device communications evemts. Change slider position for the Family Lights with the KPL button G node below the Scene name selected. Post the Insteon address of the KeypadLinc, the Family Light device and the event trace. Also what ISY firmware is being used. Is the Progress Bar displayed every time the On Level slider is moved?

Your observations are correct. Set the variable Init value when the variable value is changed for those variables whose value should persist over a reboot.

No. Some devices must be power cycled when Local On Level (applied locally) Local Ramp Rate (applied locally) is changed but Responder values reside in link records. The link record is retrieved by the responder device every time a command is received. No power cycle is required for responder value changes.

Does the Progress Bar come up when the slider is moved to 30%. It sounds like the Admin Console was not notified of the slider movement. It is a Java question as the Admin Console has nothing to do with the actual movement of the slider itself. Try moving the slider to some other position and see if the Progress Bar comes up. If so after the Progress Bar is complete move the slider to 30% and see if the Progress Bar comes up again. What is the device type of the Family Room that is having its Responder On Level set to 30%?

Teken Take a look at the description of Momentary C in the I/O Linc user Guide. Both the On command and the Off command turn the Relay On. The ALL OFF (or ALL ON) use a special Scene (Group) number that all devices with a responder link record react to even though the Scene (Group) number does not actually match the Scene number in the responder link record. The I/O Linc Relay is reacting to the Off command as though it were a normal Off command for Momentary C. As Michel mentioned earlier even the tstat reacts in ways not desired. You could switch to Momentary A mode where the Relay reacts to only one command, On or Off, but not both. It could be defined to react only to an On command but that may mess up what happends with the KeypadLinc when it sends an Off command. Lee

Every Controller establishes a unique set of On Level and Ramp Rate values for each of its Responders. Click on button G node name (as a Controller) that is listed below the ISY Scene name. Look at the On Level and Ramp Rate for each Responder when button G is the Controller.

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.

Okay, thanks. Sorry the ideas were of no help.

From a post by Michel ... If you have Run at startup, then enable/disable flag is ignored

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.

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

Sorry Tim - posted to wrong topic

Text removed as it does not apply to this topic.

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.

Any time there is a Wait or Repeat in a Program the If is reevaluated should a Status change or a State variable change. This reevaluation starts the Program over from the beginning of whatever clause is driven as a result of the reevaluation. This often leads to statements after a Wait unexecuted because the If status has changed.

When the Scene definition is expanded both switches should be listed below the Scene name and both node names should be red. The single ISY Scene evolves out to multiple Insteon Scenes. Each Insteon Scene has one Controller and one or more responders. The responders of the Controller can have unique On Level and Ramp Rate values for the particular controller. The On Level and Ramp Rate values for the Responders of a Controller can be copied from another Controller in the same Scene using the Copy Scene Attributes ... button. You can also click on the Scene name, set the On Level and Ramp Rate values and check the Apply Changes To All Devices check box.. This directs the ISY to apply the defined On Level and Ramp Rate values to all the Controllers responders.

You already have an ISY Scene where one switch is a Controller and one switch is a Responder. Delete the Responder switch from the Scene and add it back as a Controller. Only one ISY Scene is required for the cross linking to be established. The ISY assumes a Controller is also a Responder.

It restarts from the beginning. How was the Program being Run from the other Program, Run (If) or Run (Then). Either way it starts from the beginning but with a Run (If) the If is evaluated and could run the Else clause should the If be False at the time.