LeeG

Those Scenes look exactly right. With each switch/button added as a Controller the ISY cross-links them automatically so that each switch/button controls the load and the status LEDs stay in sync.

htjunkie Your understanding is correct. If Control is looking for a specific command from the device itself from a button/paddle press. The Program loop you mentioned in the first post was likely a mismatch in If to Then command. That is, an On (X10 or Insteon Status) was received and an Off was issued or vice versa.

The ISY manages link records by location in individual devices. That is, the ISY knows what link record is at each link record address in the individual device. This information allows the Show ISY Links Table for a device to display the link records as they should appear in the device. It also supports the Compare function for individual devices. Link Management in the PLM is very different. The ISY does not manage link records in the PLM by address. The PLM is given a command to add or delete a link record. No link record address is provided. The PLM has logic to locate the link record for a delete and find an available slot for an add. The ISY has no information about where any given link record is located so has no information to produce a display for a Show ISY PLM Links Table. The Show PLM Links Table reads the PLM link database sequentially. There is no Compare function for the PLM for the same reason. The ISY has no information as to what link record should be where for a PLM.

uffy - I was wrong. After taking the 994i off the wall I do have a Micro SD card behind the small cover next to the Red Error LED. Thanks Brian. I had looked for something larger along the sides like the 99i has with a similar case. Should have removed it from the mounting to see the front better.

I have "Switch1 - A" linked to Switch2, so if I press "Switch1 - A", it will turn on "Switch2". Press again it will turn off "Switch2". Only issue I have is, if I press "Switch2" locally, the status on "Switch1 - A" is not being reflected. It sounds like "Switch1 - A" was added to the ISY Scene as a Controller and "Switch2" was added as a Responder. As a Responder "Switch2" does not control any other device. Remove "Switch2" from the Scene, adding it back as a Controller. That way either device will control the other. The ISY assumes a Controller is also a Responder. For programming a specific button, can I just assign say "Switch1 -B" to "Switch3" somewhere in the GUI? Rather than using the linking mode within the switches? I do not understand the question. If “Switch1 – B†is to control “Switch3†both devices should be added to another ISY Scene as Controllers like above.

InTheDark You need to upgrade to 3.2.4. Be sure to clear the Java cache and use the correct URL for invoking the 3.2.4 Admin Console. Once on 3.2.4 run Help | About to confirm the Firmware and UI indicate 3.2.4. Delete the LampLinc and the Scene. Add the LampLinc under 3.2.4. The LampLinc is an I2CS device which requires 3.2.4. Once added recreate the Scene under 3.2.4.

Is there any other LED blinking. My 994i will blink red if there is no Ethernet connection. Make sure the Ethernet and Port A connections are not reversed. I have no external opening for an SD card which makes me think there is none.

By not moving the SwitchLinc to the PLM plug point all the questions that existed earlier still exist. I have no new suggestions.

What did Help | About show?

Look at the Scene that has the ON/OFF buttons as a Controller. What are the responders in the Scene? Buttons which are responders do not follow the non-toggle definition as far as button LEDs are concerned.

The Smarthome Garage Kit comes with a magnetic switch that has both a Normally Open (NO) and Normally Close (NC) magnetic switch built in. Use the Red/Black wire combination which will have the Sensor (and Green LED) On when the garage door is open, Off when the door is closed. Be sure to turn Off the Set Options "Trigger Reverse" (uncheck). This avoids the conflict with Query and provides a simple means of using a KeypadLinc button to reflect garage door Open/Closed status later on. Which Momentary Mode, A, B or C, does not matter unless/until the door movement is controlled from another controller such as a KeypadLinc button. Momentary C is fine. How is the door being commanded to move? Are commands being sent to the I/O Linc Relay and if so from what source?

steelman58 No problem and no confusion. The Sensor is a Controller only node. It cannot be added to a Scene as a Responder. The issue with the Scene is that the Sensor turning On sends a command to the SwitchLincs to turn On. When the Sensor turns Off it sends a command to the SwitchLincs to turn Off. No means of suppressing the Off action, thus no way to implement a controlled delay when the Sensor is the controller.

Remove the devices from Scene 37 and delete the Scene. The SwitchLincs cannot be linked to the I/O Linc Sensor and create a delayed Off. Also I strongly recommend using the other magnetic switch wire combination and turn Off Trigger Reverse. Trigger reverse only reverses the commands issued; it does not reverse the actual state of the Sensor. If a Query is done the Sensor will change state as a Query returns the true state of the Sensor, not the command reversed indications from Trigger Reverse. Then define an ISY Program that triggers from a Sensor On with the Then clause turning On both SwitchLincs. After the desired Wait the SwitchLincs are turned Off. If Status 'IOLinc-Sensor' is On Then Set 'SwitchLinc Dimmer1' On Set 'SwitchLinc Dimmer2' On Wait 10 minutes Set 'SwitchLinc Dimmer1' Off Set 'SwitchLinc Dimmer2' Off Else Wait 10 minutes Set 'SwitchLinc Dimmer1' Off Set 'SwitchLinc Dimmer2' Off The Scene that linked to two SwitchLincs can be used instead of turning each SwitchLinc On/Off individually. The RemoteLinc is a battery device. It must be put into linking mode by pressing Dim/Bright buttons until RemoteLinc LED blinks. Right click the RemoteLinc node and select Write Updates to Device.

The Admin Console is not at the correct level. The Firmware and UI lines must both indicate 3.2.4. Clear the Java cache and be sure to use the URL for the 3.2.4 Admin Console. Currently the Admin Console is from 3.1.17. If the FanLinc is still shown as unsupported when the UI line indicates 3.2.4 the FanLinc will have to be Deleted and added back with the correct Admin Console. No need to climb the ladder again. Use New INSTEON Device, enter the Insteon address, Name of your choice and leave the Device Type as Auto Discover.

They can and do. In this case there could be a link record problem, missing in the PLM or the LampLinc for some reason which would explain the lack of Scene response. Moving the LampLinc to the PLM plug point is easier than searching the two devices for the required link records. However, with a Hops Left = 0 there is some other situation as well. Whenever the Hops Left is 0 when Max Hops started at 3 something is interfering. You can run the event trace and do a few manual On/Off sequences when at the PLM plug point to confirm the Hops Left =2 is the norm.

The manual On worked but at the limit. With a Max Hops of 3 the Hops Left is 0. Tue 04/24/2012 07:25:02 PM : [standard-Direct Ack][14.3E.75-->ISY/PLM Group=0] Max Hops=3, Hops Left=0 Physically move the LampLinc to the PLM circuit to confirm the link records are correct in the PLM and the LampLinc. If it works there then look for a comm problem at the current plug point.

Two things to check. Run Help | About and confirm there is a Firmware and a UI line and they both say 3.2.4. When the SwitchLinc is selected does the right pane indicate the device is a SwitchLinc Dimmer.

Okay. You've Deleted and added the SwitchLinc under 3.2.4. You have powered the SwitchLinc from the same circuit as the PLM. The only thing left is to factory reset the PLM and do a File | Restore Modem (PLM). Would be very strange for a PLM issue be related to a single device. If the Restore Modem (PLM) does not resolve it replace the SwitchLinc.

If the FanLinc is new (last 2 or 3 weeks) and was added to the ISY before moving to 3.2.4, the FanLinc has to be Deleted and added back under 3.2.4. With the SwitchLinc Dimmer added under 3.2.4 the links are correct which leaves a communication problem. Simple test, connect the SwitchLinc to an appliance cord and plug the Appliance cord into the same circuit as the ISY PLM. If it works a communication problem exists at the current SwitchLinc location. If it does not work plugged into the same circuit as the PLM the SwitchLinc is defective. I looked back over earlier posts and did not find the FanLinc mentioned. Was the post in a different topic?

The door moves any time the Relay is turned On. It is the equivalent to pushing the manual button in the garage. When the door is closed, push the button and the door opens. When the door is open, push the button and the door closes. The Relay turning On simulates a manual button press. In any Momentary mode the Relay automatically turns Off after the timeout interval so the Direct Relay Off command serves no function. I think you are used to seeing what happens when using a Scene as that was the only choice in the SmartLinc. The various Momentary mode characteristics apply only when the I/O Linc Relay is a Responder to a Scene. If you want the same characteristics you had when using the SmartLinc assign the I/O Linc Relay as a Responder to a Scene and issue Scene commands. Scene On and Off commands are affected by which Momentary mode is chosen and possibly the status of the I/O Linc Sensor (door open/closed state).

With the SmartLinc everything had to be done with a Scene. Which Momentary mode used makes a difference when using Scenes. Since you are only controlling the I/O Linc Relay directly with the ISY or a phone app Scenes are not necessary. Only a Direct On to the I/O Linc Relay turns the relay On. A direct Off or All Off command does not turn the relay on without a Scene that has the I/O Linc Relay as a Responder..

mrohde I found these two posts from Michel about the Mac unzip situation. Please do NOT unzip the file. If you are on MAC, then the problem is that MAC automatically unzips the files. You may want to press the Ctrl button while downloading so that the file stays zipped. MAC has a [dictatorial] tendency of unzipping files automatically after download. ISY needs the file in tact and thus you have to tell MAC not to unzip. You can try: Unchecking 'open safe files' in the General tab of Safari's preferences.

I don't use the Mac but other users have reported similar error. Apparently the Mac unzips the ISY install file which makes the file invalid to install. The install file is a zip within a zip so it is not obvious that the initial file was unzipped. The last user that had the problem downloaded the file on a windows system. There is likely some Mac option to stop the unzip but I don't know what it is. If familiar with that option download without the unzip.

You have not missed it. The FanLinc options are not supported yet.

FanLinc LEDs can be turned On/Off programmatically.