Wingsy

ISY firmware: 4.3.26, UI: 4.4.6 PLM: 30.6B.34 v9E And as for the Log File -- can't get to that. Says "Couldn't Open the Excel macro /Users/{my_acct_name)/isy/UDReport.txt"

I think I have a similar issue. I have 60 various Insteon devices throughout my house, plus an ISY994i. Just a while ago I noticed that the ceiling fan in the MBR was on. And the MBR bathroom fan, and the family room fan. I went to check on the deck and those two fans were also on. Those are controlled with two Fanlincs 2475F and the others by On/Off switches 2477S. The two ceiling fans on the deck have no switches for control - I turn them on or off via my phone. I have no ISY program that has anything to do with fans. The two 2475F's and the three 2477S's are the only ones in the house, and they all came on at about the same time - hard to tell since I just suddenly noticed they were all on. They came on within at least an hour of each other, but I suspect all at the same time. Sure am glad I didn't wire up my well pump to one of these boxes. Can you imagine that? I've been thinking of connecting other things, more important things than lights & fans, to the Insteon system, but now after this it's totally out of the question. Reliable, it's not. Disappointed, I am.

Can the ISY994i control all 4 relays of the EZIO4O independently via an ISY program? I need to be sure of this before I part with 100 bucks. Thanks.

Rianza: Like you, I couldn't get the IOLinc's sensor to control the IOLinc's relay the way the user manual stated. I wired up my relay (the one I added) to the Open/Close sensor's external input terminals, and made that a scene controller to activate the IOLinc relay. I'm not using the IOLinc's sensor at all. I wired up my stairway lights to the IOLinc's Common and N.O. contacts. When the Open/Close (scene controller) sends an ON command to the IOLinc, that connection is closed and my lights turn on. 30 seconds later my ISY program sends an OFF command and the lights turn off. You should be able to use a similar setup but without the need for a program in the ISY. In your case I would think that setting a duration in the IOLinc to 1 second and using Momentary A would give you the ding and dong. When you use Momentary A, choosing whether an ON or an OFF command triggers the IOLinc's relay is something I never quite figured out how to do.

Yes, measured it. And I agree, must be a darlington. All the specs say is "<1v @ 10ma".

OK, I "got it" all right. Got snookered in with the umpteenth quirk of these sensors. (To paulbates: Same effect as you have seen.) When I hooked it up to the infrared sensor and stepped on the 1st stair the Open/Close went bananas. Continuous flashing of its LED, and it would signal the IOLinc to close its relay but the message back to the ISY telling it that it had changed state never arrived at the ISY, or was never sent. Therefore, no 30-second timeout and of course no re-triggering. The infrared sensor's output, when closed, is not a dry contact closure but is an NPN (transistor) output whose ON voltage is 0.7v. This is apparently not a low enough voltage to the input for it to fully register a closure. Why it signaled the IOLinc but not the ISY is puzzling. Determined to get this to work come hell or high water, I located a small 12v relay in my parts drawer and hooked it up so the infrared sensor would energize that relay, then connected that relay's N.O. contact to the Open/Close. It is now working in the stairway as I wanted. Now, let's see if I can consume another 2 days of my time to get my doors to lock. Thanks again folks.

OK, Got it. I appreciate the discussion on this problem, people. It generated more ideas to try and one of them worked! What I did: Set the Open/Close as a scene controller. Set the IOLinc-Relay as scene responder. Set IOLinc to "Momentary B: Triggered by both On and Off". Set the "Momentary Hold Time" to 30 minutes, which cannot be done via the ISY but can only be done with the Set button. Wrote a simple ISY program "If Open/Close status is on or off then wait 30 seconds and turn off IOLinc-Relay", which re-triggers when the Open/Close changes state. The Off command sent by the ISY overrides the 30-minute timeout set in the IOLinc. I should not have had to go through this to accomplish this simple little thing. I think Insteon should revisit the IOLinc firmware and allow its own sensor to work as any other sensor to control its relay.

I've already done that. Wrote a program to do exactly what I wanted. Except that it sometimes takes the ISY eons to respond to the sensor input and activate the relay output to turn on the lights. And by that time you're already at the 3rd or 4th step and have hit that toy firetruck parked on step #3. If I set the IOLinc so that the relay output follows the sensor input the response is consistently instantaneous. It would be nice if setting a scene using the sensor on the IOLinc to control the relay worked as quickly, but it won't work AT ALL. I can't set a scene using the IOLinc sensor to control the relay. As it stands now, using the Open/Close sensor as a controller in a scene to control the relay for a timed duration works fairly good. Response time is acceptable. What it lacks is the ability to be re-triggered while it is timing out so that if another person goes into the stairway while the light is already on that they get the full 20 seconds of light. It won't re-trigger so it goes out 20 seconds after the first person hits the steps, regardless. A program will re-trigger but a timed output using a scene won't. "Momentary C: Trigger based on sensor input" doesn't work either. With the IOLinc in front of me right now this is what I get: (Delay time set for 20 sec. Sensor input is 2 wires shorted together, or not. IOLinc sensor is scene controller, relay is scene responder.) Checking "Relay Follows Input", the relay does follow the input. When the input is closed the relay is closed. When open the relay opens, and no other options have any effect. Choosing "Latching: Continuous", relay does nothing. Choosing "Momentary A: Triggered by Either On or Off", relay does nothing. Choosing "Momentary B: Triggered by Both On and Off", relay does nothing. (Someone please explain the difference between A and B.) Choosing "Momentary C: Triggered Based on Sensor Input", relay does nothing (even with no scene established). When I change the scene to have the Open/Close sensor as the controller, I was hoping that Latching would indeed latch. Then I could use the ISY program to time the relay opening and also re-trigger if necessary. OK, it does latch... BUT NOW it latches ON when the sensor goes from closed to open (i.e., when someone's foot leaves the first step and goes to the 2nd. Too late) and does nothing when it goes from open to closed (when a foot hits the 1st step). Ahah! So I select "Trigger Reverse" to correct this. BUT THEN, it triggers the relay when closed but ALSO causes the relay to open as soon as the input opens, as in "Relay follows Open/Close Sensor". If I had hair to spare I'd pull it out! Choosing A, the relay does nothing when the sensor input is closed and the relay closes when the sensor input opens (wrong sense). Choosing "Trigger Reverse" has no effect. Choosing B, and I'm almost there. Relay closes when the input transitions from open-to-close and vice versa. But it doesn't re-trigger and can miss the next transition if there are several transitions while the relay is closed. Happens sometimes. Choosing C was covered earlier. Nothing.

Right now it's sitting on my desk. It detects the reed switch closure when I move the magnet close to the sensor. When I have it wired to my stairway light system it detects a contact closure generated by the infrared sensor (which is not an Insteon device).

Have a 2450 (v2.3) I/O Linc. My ultimate objective is to trigger the I/O Linc output ON for 20 seconds when triggered. The trigger source is an infrared beam sensor, giving a closed contact when the beam is broken. This is used as a stairway light - step on the first step to break the beam and the lights (12v) embedded in the wall come on for a period of time. I can do this by setting an Open/Close module as a controller for the IOLinc, and setting the IOLinc for "Momentary B: Triggered by both On and Off". (This works well enough, but sometimes if the Open/Close makes several transitions while the IOLinc is timing out, then the next event from the Open/Close is ignored. But that's another story.) What I want to do is to use the IOLinc's sensor input in place of the Open/Close. But if I create a scene using its sensor as the controller, nothing happens. It never triggers the relay. What's going on?

Thanks folks. Some good info up there. But I still want to know about your experience with speed in a loaded system. In my limited test setup, with an ISY and a handful of dimmers & other modules I have seen occasional delays of several seconds between an event and the ISY responding to it (from an ISY program). Usually it's a second or less. I'm chalking that up to the ISY sometimes having to do multiple retries to get its message out. Now with 40 nodes out there and each node capable of forwarding a packet from the ISY, how much of that will need to go on to complete an exchange between an outlying node to the ISY and back to another outlying node? That's what I'm curious about. It's going to be whatever it will be but I'd like to know what to expect so I can recognize a network problem when/if I have one.

I'm about to make a major commitment to an Insteon-controlled house. Under construction now and we should be in in late May. Electrician coming for survey in 2 days. I'll have 30-35 Insteon light switch/dimmers, around five 6-button switches and a few plug-in on/off modules. One high power switch for an irrigation pump, and another switch for a pair of 20 million candlepower strobe lights at the end of the driveway (seriously, LOL!). An ISY994i is my controller. My main question is, will network speeds drop off with this many devices? 2nd question. I want to have a door switch turn on a light (hopefully almost instantly) and to turn it off when closed, AND the ISY to turn it off after a delay regardless if the door switch is opened or closed. That'll work, right? (I would test this myself but my test setup is disassembled.) Thanks.

I don't recall exactly but something like 79.292 or close to that. It's West but the lookup didn't include East or West spec. And I don't know what you mean by 4.2.18 was accessed? I was using the admin console when I got that error, and the software version was 4.2.18.

ISY994i, sw: 4.2.18 In setting the location for the clock (Configuration:System) I can choose "Locate Me" which brings up a city not far from me. But when I accept this location I get an error "Invalid Longitude". It isn't invalid - it is the correct longitude but the software will not accept it. Any suggestions? (I saw a similar question dating back to 2012 and with no resolution. Is this a bug that won't go away?)