GuyBooth

Thanks for everyone's responses. I will install the XPCP. I can always replace it later with the 2406H, but I also have a couple of access points, so I'm not anticipating any problems. For anyone who is interested I found this article very informative: http://jvde.us/x10/x10_couplers.htm

I have an XPCP X-10 Pro Passive Phase Coupler from a time when I used X-10 devices. Will it technically work well enough on an Insteon system so I will not have to purchase a 2406H? (I want to ignore the wireless access points solution for this question).

The purpose of this is to trigger a specific program after power is restored. However, I need to give the power supply and the PLM enough time to stabilize before triggering the program - preferably about 5 secs. At this time the only way I can see to do it is to use a timer relay, but I didn't want to add bits and pieces.

If the ISY is still running but the PLM has lost power is there anything that can be used to set a variable or trigger a program? Conversely when the PLM comes back on line can it set a variable or trigger a program?

Using the momentary contacts with the timer would serve to debounce the input in case of power outage. Yes it can be programmed but I prefer to do as much as possible at the lowest level.

Too bad. I was trying to use the built in timer capabilities of the momentary contacts. I can program around it.

I am trying to use a change in the IOLinc Relay Status to trigger an action on my ISY, using the momentary time to create a time delay. The program code is very simple: If Status 'CR112 Sump Alarm-Relay' is On Then Set 'CR102 Lamp Dimmer' On When I set the IOLinc options to "Latching" the system works as expected. When I set the IOLinc options to "Momentary" the following results: When the Sensor is turned On, the Relay clicks ON and the CR102 Lamp Dimmer turns on. ISY shows the Relay Status as ON After the Momentary Delay period (default 2 secs) the Relay clicks OFF, but nothing else happens. ISY shows no change in the IOLinc Relay status. If I Query the IOLinc from ISY the status then changes to OFF and the CR102 Lamp Dimmer turns off as it should. I really need the status change to reflect back to ISY without my having to Query it. Why doesn't this happen?

I am looking for a way to "tell" my system that power has been restored after an outage, possibly a very brief one. The ISY will not have experienced the outage since it is on a UPS, but I have modules on the system that "drop out" (on purpose) when power to the system is lost. Best way I can think of is to have some kind of time delay relay or module plugged into an outlet that is connected to the sensor of an IOLinc - but it must have a time delay of, say, a second or more to allow the IOLinc to power up before being triggered. Has anyone tried to do this? Any ideas on a good time delay module to do this?

Ok I just found the "condition" condition - although pretty well any one of these many conditions would be a reason to turn the water feature off!

I`d like to be able to prevent a water feature from running if it is raining - or not allow it to start if it is raining. Is there anything in the weather module that will allow me to do this? I see information concerning rainfall for the day, or rainfall forecast - but nothing that tells me whether it is raining at any given moment,

Once in a while a power blip hits my house. Sometimes it only affects one side of the split phase - I can tell because the stove clock goes to 00:00. But it also affects a couple of sensors. The ISY doesn't stop or reboot. I would like be able to detect it using some kind of Insteon device and the ISY. Does anyone know a way to do this?

Thanks Michel, I'll follow up with Tech Support.

Michel, Can you tell me if this would address the issue that I'm having (see previous posts) or is this a different problem? I don't appear to be having "all on" triggers, but as described I'm having intermittent problems after the Query runs at 3:00 am. I actually created a program to try to recreate this. It runs the Query program, and I ran it for 100 iterations - but the problem didn't show up. Yet on two occasions in three weeks I've seen it happen at 3:00:09 am....

This should actually read that the IOLinc has twice tripped OFF at 3:00:09 am - 9 secs from the Query program running, not the 9 mins that my initial post indicated.

Why does it only happen occasionally? Yes it is being used with Trigger Reverse, UPDATE: Actually it is NOT in Trigger Reverse mode, that was a prior iteration. This is a water sensor and is NC to be fail-safe. Once the sensor is triggered, it stays off until the user can check the condition and reset it when the condition has been rectified and there is no water present.

I'm having what appears to be a similar problem with "random" events. These occur right after the query takes place at 3:00 am - the setup is fairly complex, but essentially I have an IOLinc that has twice tripped OFF at 3:09 am for no apparent reason. The PLM version is reported as v99. Does this mean I will have to replace it? What are the consequences of not running the Query program at 3:00 am? I have just changed the time to 4:00 am to make sure there is consistency in the timing of the event, but it could be a couple of weeks before I see it again.

Can somebody please point me to an example of how to create a scene where the scene is triggered by an Insteon OFF command? I need to set up a scene where a sensor feeding an IOLinc turns OFF thereby turning on a KPL LED as a warning. I've read and watched tutorials but for some reason this is eluding me.

I'm having the same problem - a number of modules show up, but not the Climate Module. I have sent an email to support with my ISY details.

I been struggling with Notification emails. I find that if I do not include anything in the Body of the email, nothing at all is sent. Seems to me I should be able to send an "empty" email so I can just see the subject line - in most cases that's exactly all I need. Has anyone else seen this problem?