LeeG

Negative. The On Level (applied locally) and Ramp Rate (applied locally) are the values in effect at the device where paddle is pressed. If affects what is connected to Red load wire of the SwitchLinc when the On or Off paddle is pressed on that SwitchLinc. When the Scene name is selected there are other On Level and Ramp Rate values displayed for each Responder of the Scene (includes Controllers that are assumed to also be Responders). It is these values that are stored in the Responder link records in each Responder device. These values instruct the Responder device what to do when it receives an On command from the respective Controller (ISY PLM) in the case where the Scene is controlled through the Admin Console. The only time a device node name below the Scene name is selected is when the Responder On Level and Ramp Rate values for the other Responders of the Scene are being set for when the paddle on that Controller is used. Pressing the On paddle on the SwitchLinc will cause these values to be used by the other Responders of the Scene. Each Controller has a unique set of On Level and Ramp Rate values stored in each of the Responder devices.

Michel The Show ISY Links appears to be intermittent or very step specific. I ran several tests when IM made his initial post and could not recreate. Tried it again today and can reproduce with a specific sequence. Start Admin Console Show Device Links Table for ICON Dimmer Compare Show ISY Links Table for RemoteLinc2 The last Show ISY Links for RemoteLinc2 does not replace the ISY Links display from the Compare of the ICON Dimmer. Other sequences have run without any problems. Lee EDIT: it is NOT specific to the RemoteLinc2. Same sequence except the Show ISY LInks for an ICON Relay produces the same result; the Show ISY Links from Compare is not replaced. Also found it not necessary to restart Admin Console to recreate.

ricke How are you turning the House Lights Up Scene On? Each Scene Controller has a unique set of Responder On Level and Ramp Rate values. When the Scene name itself is selected the On Level and Ramp Rate values that are displayed and can be adjusted apply when the Scene name is controlled through the Admin Console or an ISY Program. When a Controller node name (SwitchLinc) below the Scene name is selected the Responder On Level and Ramp Rate values displayed and adjusted apply when that Controller paddle is pressed. It sounds like the On Level and Ramp Rate Responder values are being set for a specific Controller paddle press rather than for Scene name. When the Scene name is turned On/Off through the Admin Console or ISY Program the ISY PLM is the Controller. When an individual SwitchLinc paddle is pressed On/Off that SwitchLinc is the Controller. Each Controllers On Level and Ramp rate for the Responders in the Scene is unique. To make On Level and Ramp rates changes easier there is a check box "Apply Changes To All Devices". If this box is checked the On Level and Ramp Rate values are changed for all the Controllers at the same time rather than having to select each Controller name individually. Of course if each Controller should have a unique set of On Level and Ramp Rate values for its Responders this box should not be checked. Lee

RichardLetts Turning on the KeypadLinc button when the Sensor turns On does NOT cause the KeypadLinc to turn the I/O Linc relay On. Insteon does not propagate Controller commands from one Controller to another. There is an I/O Linc option that causes the Relay to follow the Sensor which should not be used or perhaps the I/O Linc Relay is being turned On by an ISY Program when the Sensor turns On. Suggest going to the UDI Wiki and search on garage. There is an example of how to implement a garage setup. I don't like combining the function of door control and door position indication with a single button. There are a number of forum posts that discuss how to implement such an arrangement. Those who have done it are satisfied with. Lee

elvisimprsntr There is a "Catch up schedules at restart" Configuration option that will cause Programs to run at startup as well. Try disabling that option. Lee

ricke oberkc covers just about all the issues. That is why manual Set button links should never be done while using an ISY (a few device specific exceptions described in user guide and wiki). Whenever the ISY writes link records to create a Scene or update a Scene it is NOT aware of manual Set button links and they can be overwritten as it sounds like happened. When a device is added as a Controller to an ISY Scene the ISY assumes it is also a Responder. As oberkc described adding both SwitchLincs as Controllers to a Scene will cause the ISY to cross-link the devices as they are assumed to also be Responders. These links will not be overwritten if the devices become part of additional Scenes as the ISY is aware of what it wrote. Lee

autom8tme Please do. Once the basic Insteon environment is established and stable you will find all kinds of interesting things can be done with the ISY. The users on this forum along with the great support from UDI personnel can help with just about any question that comes up. Lee

autom8tme Along with the good information and suggestions from apostolakisl, here are a few more items ….. 1. Be sure the Access Point and the Dual Band PLM pass the 4 Set button tap test confirming they are on opposite 120V phases and can hear each other’s RF signals. This is absolutely essential before working any other symptom. 2. Be sure the ISY PLM is not plugged into a surge suppression power strip and there are no UPS/PC equipment plugged into the same circuit. The UPS and PC equipment should be connected to a FilterLinc to insure they are not interfering with the Insteon signals to and from the ISY PLM. The PLM can be temporarily connected to an extension cord and powered from a separate circuit until a FilterLinc is available. 3. Concentrate on one problem at a time. Provide detail. A symptom of "cannot create a Scene" is not helpful. Cannot define a new Scene, cannot add a Controller to the Scene, cannot add a Responder to the Scene, all appeared to work in creating the Scene but it is not functional, device to device control works but only in one direction, device to device control works in both directions but the devices cannot be controlled from the ISY Admin Console. Just a sample of information that is useful in understanding the failure and possible solution. As you gain experience with the technology better problem descriptions will evolve. I can think of a half dozen reasons a Scene cannot be created or not working and many are simply not being familiar with the technology. 4. Success with Insteon has much less to do with intelligence and much more to do with knowing the technology. Each solution will add to the knowledge base. 5. The 2494m3 Dimmer Kit is two SwitchLincs that come prelinked. The prelinking is somewhat useless with the ISY as all linking (Scene creation) should be done with the ISY. The prelinking does not prevent them from being used successfully with the ISY. 6. Devices should be added to the ISY with the â€Remove existing links†option. All device linking and cross-linking is done with ISY Scenes. Lee

The Dual Bright motion head electronics actually powers the flood lights. Nothing to connect the InLineLinc Sense line to but the motion head. I use COOPER Lighting motion heads. The cheaper the better as the more expensive motion head may have electronics powering the floods. Last time I was in a Home Depot there was a wall full of sample flood lights and motion heads. Look for one that clicks (relay energizing) when motion is sensed.

backinthelab I did not follow option A. Anything related to using the Dual Bright motion head directly is a problem for the InLineLinc. The voltage from the Dual Bright motion head is controlled by electronics which does not swing from 0 volts to 120V as the InLineLinc requires (or nearly so). Option B is okay. All the home improvement stores around here sell motion heads. Replace the Dual Bright motion head with a simple motion head that indicates motion with a relay. That combination works well with an InLineLinc. I converted X10 based flood lights that way. Remove the X10 motion head, replacing it with a basic relay based motion head and used an InLineLinc w/Sense for the Insteon side. Lee

The ISY does not have reliable communication with that SwitchLinc. Apologies, most of the post was not pasted. Depending the option used for resolving existing links, "erase existing links", etc the ISY will clear current links or not but will write additional links to connect the new device to the ISY PLM. There is a fair amount of command activity involved so issues with powerline reliability on a particular circuit will often surface during the device add and/or Scene creation.

"is there a way to have it group the way I wanted or does the parent node in the group always refer to the first button?" The individual buttons can be named whatever you want but a KeypadLinc has only 8 buttons max. There cannot be 9 nodes for an 8 button KeypadLinc. The KeypadLinc Primary load control button is always first with each Secondary button in Group number order following.

The KeypadLinc button can be added to a Scene as a Controller or a Responder. As a Controller it will control other Controllers as Responders and Responders. The ISY assumes a Controller is also a Responder so long as the device has Responder capability. When referencing the Scene name itself from the Admin Console or a Program the ISY PLM is the Controller and all other devices are treated as Responders. When the KeypadLinc button is physically pressed it is the Controller of the Scene and all other devices are Responders. Take two devices, a SwitchLinc that is controlling the physical load and a KeypadLinc button that should also control the load. A single ISY Scene is defined with both the SwitchLinc and the KeypadLinc button as Controllers. Because the ISY assumes Controllers are also Responders the two devices will automatically be cross-linked. Either the SwitchLinc paddle or the KeypadLinc button will control the load and the status LEDs stay in sync. If the Scene name is referenced both the SwitchLinc and the KeypadLinc buttons are Responders of the ISY PLM and both react together. With a few exceptions which are covered in the User Guide and/or Wiki for a particular device type, Set button links should never be created after the device is added to ISY. The ISY is not aware of the Set button link. The preference is to "erase existing links" when a device is added to the ISY and use the ISY to create all Scenes.

Never used this but maybe it would help. viewtopic.php?f=66&t=5834 On the UDI forum toward the bottom is a section for 3rd party apps. That is where I got the above link.

TJF1960 has it exactly right. Right click the Scene 27 and delete the Scene. Define a Scene name that is meaningful and either right click on the device nodes and select Add to Scene or drag and drop. FYI - the KeypadLinc firmware does not support turning Secondary buttons On/Off with Direct commands. A Secondary button can be added to an ISY Scene as a Responder and the Scene turned On/Off with the Admin Console or ISY Program. The Primary load control button can be turned On/Off with Direct commands.

I believe Java assigns random port numbers. If the Admin Console is seeing status changes the ISY is successfully pushing the status change data over the local IP. Don't know if the mControl plug-in requires anything special. Would not think so but with the Admin Console seeing the changes I would have expected mControl to see them if it was looking for them.

Check the ISY Admin Console for status updates. Firewall/AV are common blocks to the ISY pushing data such as device status updates.

“does it just check what the PLM thinks the status is, or does it actually check with the device†A device Query communicates with the device. The ISY maintains what it thinks is the current device status. When a Scene is turned On the ISY marks devices in the Scene as they are defined to react, not necessarily how devices actually react. The PLM does not track device status. “If you query a scene with multiple modules where not all are on, what status would you get†oberkc is quite right, a Scene does not have a status of its own. Not part of the Insteon architecture. A Query of a Scene does not produce device status updates. It will be necessary to Query each device.

Many of the pluggable devices are built on that basic model. A PLM shell with the capability of adding a daughter card for individual device function. Many of the Simplehomenet devices are built around the basic Insteon pluggable device shell with a daughter card that provides the SHN device specific function. There is nothing an application like an ISY sends to an Access Point. That is why Access Points are not defined as devices. They contain no link records and are not configurable. A developer subscription is needed to gain access to the confidential list of commands. Some information always leaks out. There are a few user hosted sites that list some of the Access Point commands. I saw one site document a method for querying an AP to determine which phase it is plugged into. Never tried the commands to see if the information was accurate. Some of the information is outdated and may no longer apply.

Every Insteon device has a PLM and that PLM has an Insteon address. There are commands that can be sent to an Access Point which requires the AP Insteon address.

What ISY firmware level is being used? If one of the 3.1.x releases clear the Java cache. Invoking a pre 3.1.x Admin Console will not show the Variables tab even when running a 3.1.x image

Some of the posts that Brian's link gets to discuss using a packet sniffer. That is a tool that is watching IP traffic. Suggests the idea of mControl using IP to communicate with the ISY is correct. Also the mControl instructions indicate the devices and Scenes must be defined in the ISY.

For sure the Insteon devices must be defined in the ISY database. I think your evaluation of how things work with mControl going through the ISY over IP is logical. I would think mControl would describe how they work when using an ISY for powerline access.

As I mentioned earlier I don't know mControl but I do know the ISY. mControl will have no direct contact with the ISY PLM. mControl probably has some ISY plugin that communicates with the ISY over IP. Commands to the ISY over IP can direct the ISY to do things through the ISY PLM to control Insteon devices that have been added to the ISY but it is physically impossible for mControl to directly communicate with the ISY PLM. The 2413S PLM has a single Serial interface which is connected to ISY Port A which is a Serial interface. A Serial interface does not allow multiple applications to communicate over the same Serial connection.

Unfortunately I know nothing about mControl or how it interfaces to the ISY. There is a category for mControl topics but nothing has been posted there since Jul 2008. Perhaps mControl has a forum.