LeeG

The "If Status" requires a change in the status value to trigger the Program. The Then or Else clause will run depending on whether the If evaluates to True or False.

Are you asking about the status LED brightness level or the On Level of the load being controlled by those devices. If the load On Level is not being reported to the ISY for some of the devices (but not all) then something has happened to the link records either in the devices themselves or the ISY PLM. This assumes the problem is not caused by a communication problem with the circuit(s) the devices are on. If the devices can be reliably turned On and Off through the Admin Console then it is likely not a communications problem. Try a Restore Device on one of the switches. If that does not resolve the problem a Restore Modem (PLM) will restore the PLM link database.

An ISY Program is necessary to accomplish that. If Status xxxx is On Or Status xxxx is Off will trigger an ISY Program when the Status changes. The Program issues the Notify.

Forgot to answer the door bell question. An I/O Linc Relay can be used to turn On the door bell. The I/O Linc Relay has a time setting that establishes how many seconds the Relay stays energized. I think X10 has a chime module that could be activated. The Dakota Alert receiver has built in chimes unique for each channel.

The LampLinc is a dimmer, not rated for a blower motor. It does have Controller capability so it does send commands when turned on by load sense or the manual On/Off buttons. A 120V relay could be connected in parallel to the blower motor. The relay contacts could be connected to the Sense wire of an InLineLinc which will turn the InLineLinc On and Off as the blower turns On and Off. The relay contacts could be used to control the Sense line of an I/O Linc with the same On/Off result. The I/O Linc Sense connections would be low voltage wiring rather than the 120V wiring required for an InLineLinc w/sense.

The RF ranges are for clear line of sight to the Dual Band receiver. You will need to test the Motion Sensor in the required location to see if it can communicate with the closest Dual Band device. Placing a Dual Band device outside in a weather proof enclosure could help. Note the Insteon Motion Sensors are not weather proof. Another more expensive alternative is the Dakota Alert wireless devices. I am using two transmitters that are 200' away on the outside, transmitting to a Dakota Alert receiver in the house. The Dakota Alert receiver supports 4 different RF devices (channels) which I have connected to an EZIO6I to send Insteon signals.

The SynchroLinc is a Controller Only device. It cannot be turned Off with a command from another device. The ApplianceLinc is a Responder Only device. It does not have Controller capability so it cannot send commands when load sense turns the ApplianceLinc On. The capability of any given device to function as a Controller and/or Responder can usually be determined by looking at the User Guide. There will be linking instructions as a Controller and/or as a Responder if the respective capability exists.

Running Insteon devices with a UPS may cause communications problems with those devices. One technique for determining if power is On would be to use an I/O Linc. The I/O Linc Relay NO contact would turn On the I/O Linc Sensor. Send a command to turn on the I/O Linc Relay, wait a few seconds and check the Status of the I/O Linc Sensor. If the Sensor is not On then one could assume the I/O Linc does not have power. Could do the same thing with most any Insteon device that turns On and Off. Turn the device On, wait a few seconds and Query the Status. If not On then assume the device does not have power.

The Motion Sensor is rejecting the updates to the configuration data. Note the Nack being received each time the configuration is updated. Double check Jumper 5. Thu 03/08/2012 06:20:33 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:47 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

I have to conclude this is not a new EZIO4O. The internal PLM has a large memory configuration which is correctly detected by the ISY and that is where the ISY is writing link records. The internal PLM is writing Set button link records as though it is a small memory configuration. This device cannot be used with ISY Scenes. EDIT: I also noticed the internal PLM does not support the extended ALDB command used for link management. This is an additional indication the PLM is not new. Both of my new EZIOxx devices from SHN support the extended ALDB command.

The v.28 is the latest EZIOxx firmware. If the Set button link is still active use the SHN Utility and display the link records using "Manage Device Links". First use the Links Database Size: Small option and then the Large option to see which one (or both) display the Set button link. The Set button link location (Small or Large) identifies where the EXIO4O internal PLM expects the link records to reside. The event trace of adding an EZIO4O node to an ISY Scene will show where the ISY is writing link records. The New INSTEON Device with the specific Device Type of EZIO4O causes the ISY to run an algorithm that determines the internal PLM memory size. The ISY writes link records based on the internal PLM memory size. When ISY Scenes do not work it is usually a conflict between the size of the internal PLM memory versus where the internal PLM is actually writing records. A few years back some EZIOxx devices were shipped with large PLM memory but PLMs that used the memory as though it was the small memory model. That combination does not work with the ISY. They have not been shipping for a long time so a new EZIO4O should not have that problem. If this is an EZIO4O that was returned to SHN for firmware update it could have the latest firmware (which it does have) but an older PLM. By comparing were the ISY is writing link records versus where the PLM Set button is writing link records a memory size issue can be determined. EDIT: I've added two new EZIOxx devices this morning. Neither is an EZIO4O but both are at the same v.28 firmware level and have new PLMs with large memory. The ISY 3.1.17 successfully created Scenes with the EZIOxx nodes as Responders and the output relays responded correctly. Although not an absolute the EZIOxx addresses are 19.BD.xx

Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Put the MS into linking mode and click Set Options. Change the timeout value and click Ok. Click Set Options again. Post the event file and the new timeout value.

How was the EZIO4O added to the ISY? Start Linking, New INSTEON Device, what options were used? Manual Set button links may not show up under the ISY. They are not known to the ISY and will eventually be erased or overlaid. Manual Set button links should not be done when using an ISY. They were done above as a diagnostic test. The Show Device Links Table shows a starting address of 0FF8 even though the starting address is likely 3FF8 for a large memory internal PLM. What will be helpful, besides knowing exactly how the EZIO4O was added to the ISY, is a Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected, and add one of the EZIO4O nodes as a Responder to an ISY Scene. That will show where the link record is actually being written. Post the Event Viewer trace.

FanLinc support will have to be released in the next ISY image update before a FanLinc can be controlled through MobileLinc. Likely will require an update to MobileLinc as well.

Apparently the ISY is running 2.8.16 even though the Admin Console is at the 3.1.17 level. Suggest updating the ISY to 3.1.17. Be sure to clear the Java cache after updating to 3.1.17. Then Delete the Dual Band KeypadLinc and add it back to the ISY when both the Firmware and UI line indicate 3.1.17.

What ISY firmware and what does the Admin Console show for the Device Type (second line in right pane)? If 3.1.17 does Help | About show 3.1.17 for both the Firmware line and the UI line?

ScottAvery I don't see them as being different. I did not think an 8 button KPL would work in my first post because in an 8 button KPL A is the load control button which is problematic. The initial information did not indicate the Secondary buttons A,B,C were trying to control the primary load button. Without that I think the 6 button configuration using A,B,C to control a different switch will work. The problems arise when A,B,C are trying to control ON/OFF AND have the characteristics the OP requires without the aid of the ISY (it is being moved to a new house). There might be some way to make it work with all the results the OP wants but I don’t know to do that when the load control button is involved (without an ISY).

OmegaQuest Either get another 3 pin miniature jack and change wires per Brian's information or just cut the jack off and connect the three wires directly to the I/O Linc screw terminals. Brian Nice job!

As the TriggerLinc is a Controller Only device the Admin Console reports the last command received from either node. This is true for all Controller Only devices, not just the TriggerLinc. With the TriggerLinc jumper removed the TriggerLinc sends On commands ONLY, to one node or the other depending on whether the magnetic switch goes to Open or Closed. With the jumper removed no Off commands are sent so the Admin Console will not show an Off status.

I don't think you can accomplish what you want once the load button on the same KPL became part of the requirement. That is why I indicated before if it had been an 8 button KPL using Main/A it was probably not possible.

Either the link records for those four buttons which would normally point to the ISY PLM have been lost or the PLM link records for those four buttons have been lost. With the Restore Device not resolving the problem it is likely the PLM records for those four buttons are no longer there. What PLM are you using, 2412 or 2413? If a 2413 how many link records does the PLM currently contain? You may have exceeded the capacity of a 2413 PLM. Do a Show PLM Links Table and click Count. Insteon traffic reaching the PLM during the Show can produce invalid results so it is useful to run the Show and Count multiple times. If the PLM link table has not been exceeded and the problem is with the PLM link records a Restore Modem (PLM) should restore the PLM link database. Before doing any restore I suggest running Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected and press each of the 4 KeypadLinc buttons to see if any Insteon traffic is traced when the button is pressed.

“What is the intended use for this setting, when the jumper is removed from the Triggerlinc?†From the TriggerLinc User Guide…. This mode is ideal when you need more flexibility: - For rooms where you want the lights left on after the door is closed – simply don’t Link any Responders to Scene 2 in this case - Turning lights on at full-bright when a door is opened and dim when the door is closed - Activating two independent scenes when a door/window is opened as opposed to closed “ If you simply want to track states from a sensor attached, does one simply use the jumpered setting and the Open node for state information?†Yes. “On the face of it, this appears to be totally useless.†Some Insteon devices have features that are useful where no automation is in use.

The tstat was added to 3.1.17 in the wrong mode (Off mode was not set per previous post). That may have put the tstat in a bad state. Nothing command wise can physically damage a device. Suggest deleting the tatat from the ISY, Factory reset the adaptor, add it back in Off mode.

It will run at Sunrise without Run At Startup.

Try adding the ON/OFF button to the mutually exclusive group containing C & D. Not sure that will work with the load control button. ON and OFF work together so it is not possible to add C & D to a Scene that is controlled by the OFF button without having C & D turn On with the ON button. ISY makes it so much easier.