someguy

Your answer makes sense to me, but here is where I don't get it. The IF part says "time is 10:00:00". It is only that time for one second, so why does it keep flashing even after it is 10:00:05, and at 10:00:30, etc.?

why would this program make my lights continue to flash on and off? I was intending to have them flash once to tell me that it is 10:00pm. If Time is 10:00:00PM And Status 'Hearth-5-Lamplinc' < 20% Then Set 'Hearth-5-Lamplinc' Fast On Set 'Hearth-3-West Light, by TV' Fast On Wait 1 second Set 'Hearth-5-Lamplinc' Fast Off Set 'Hearth-3-West Light, by TV' Fast Off Else Set 'Hearth-5-Lamplinc' Fast Off Set 'Hearth-3-West Light, by TV' Fast Off Wait 1 second Set 'Hearth-5-Lamplinc' Fast On Set 'Hearth-3-West Light, by TV' Fast On

how do you get the date in the schedule part of the program? I don't see that option there.

okay, I was able to get out of the loop. I tried it multiple different ways, but the way that finally worked was to unplug the ISY, then plug back in, then log in quickly and go into the program summary tab, then quickly highlight the programs that were the problem and click "disable". I believe that the reason I was able to do this was because the ISY was still getting warmed up and doing startup stuff and it hadn't gotten around to getting stuck in the loop yet.

I've got two programs that call each other and they are running over and over. I can't figure out how to stop them. I tried to uncheck the "enabled" box and save them, but it looks like they won't save while they are running, so this doesn't work. I tried going to the tab where the programs are listed and right clicking and clicking "stop" but this didn't work either. Does anyone have any ideas as to how to get me un-stuck?

There is your problem. You should be running the IF, not the THEN. By running THEN, you are skipping the condition check (if off), and going righ to your commands (turn on). Jim H. wow, thanks Jim H. for the quick reply. so, I should leave the first program as "run then" because there are no conditions, but change the second program to "run (if)"?

I've got 3 lights that do not go on reliably. I am currently working on figuring out how to get them to be more reliable. I believe that the signals aren't getting out to the third fuse panel in my garage reliably. I have found that if I hit "on" for the unreliable lights enough times, they go on. One of the problems is that when the ISY turns on the light, the status goes to "on" whether it is on or not. I have to query (or walk over to the window to look out to the yard) to see if the light is on. I decided to make a couple of programs that would query the lights and then turn them on if they weren't on. In theory, this could repeat iself until they went on. The problem is, they keep repeating over and over, even after the lights go on. here are the programs: this one is called "get those lights ON": If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Outside-9a-Malibu, Garage' Query Set 'Outside-9c-Behind shop' Query Set 'Outside-1-Garage Right' Query Wait 30 seconds Run Program 'get those lights ON 2' (Then Path) Else - No Actions - (To add one, press 'Action') This one is called "Get those lights ON 2": If Status 'Outside-9a-Malibu, Garage' is Off Or Status 'Outside-9c-Behind shop' is Off Or Status 'Outside-1-Garage Right' is Off Then Set 'Outside-9a-Malibu, Garage' On Set 'Outside-9c-Behind shop' On Set 'Outside-1-Garage Right' On Wait 5 seconds Run Program 'get those lights ON' (Then Path) Else Disable Program 'get those lights ON' Please note that both of these programs have the "enabled" box unchecked and the first program is "run then" when I try to turn on the lights. Any ideas as to how to get this to work. I know this is like child's play for most of you guys.

I've done quite a bit of research and I haven't been able to find the answer to what an insteon thermostat will do for me. Here is what I'm looking for: a thermostat that will run a program that sets the thermostat to a certain temperature in the morning, daytime, evening and night-time. I'd like to have this schedule change depending upon occupancy. The occupancy could be indicated to the thermostat by a motion sensor or a light switch. Here is what I mean: Would I be able to set the thermostat to 65 degrees during the daytime, but if someone came into the area, and tripped the motion sensor or turned on a light in the area, it would go to 70 degrees for a couple of hours, then return to 65 degrees. It should also go to the next scheduled temperature per the programming and then during that period of time, it might be set to 68 degrees and the motion sensor turns it up to 72 degrees. I'd also like to be able to have someone walk up to the thermostat and change the temperature setting and it stay there instead of having it switch to some other setting when someone turns on a lightswitch or walk past the motion sensor in the area. At night, I wouldn't want the motion sensors or the lightswitches to affect the settings. I'm sure the isy can handle this part easily. Will it work like this? Are there any other things that I can do with it that I might want to do? These are the two thermostats that I found, are they any good? http://www.smarthome.com/30412A/7-Day-P ... 900/p.aspx http://www.smarthome.com/2491T7/Venstar ... ble/p.aspx

I have a garden-variety alarm system in my house and there are a couple of motion sensors that MIGHT be useable for my insteon system. How hard would it be to figure out how to make one of these motion sensors turn on an insteon light? I do have an EZio2x4 that I could use, but not sure how. For clarification, my alarm is not an Elk alarm system. As a matter of fact, for perspective, I'm not even sure what an Elk alarm system is.

thanks for your help. Yes, I could talk to you and work this out tomorrow. I will send you a personal message for more details. this is a new Motion sensor, not a beta version.

Hi Michel: I tried "restore device" multiple times with the motion sensor in programming mode sitting a few inches from either of my access points. I tried it with three different batteries. It still didn't work. I also did wait more than 5 minutes after reinserting the battery. I removed the device from the ISY and then did a factory reset. Now I can't get it to add to the ISY list. When I put in the insteon address and either choose auto-discover or choose 2420, It gets to about 8% and then the diaglog box just vanishes. I have tried closing all browsers and deleting my java cache and nothing works. Any other ideas? Here is the funny thing, the motion sensor still turns on the lights that it was linked to before, but the status doesn't report to the ISY when they change from off to on or vice versa. edit: I tried putting it a few inches away from the other access point and I can now get it to go all of the way to 99%. This requires me to put the unit back into programming mode twice and when it gets past 99%, the dialog box vanishes and the motion sensor isn't in my list. Any ideas to fix this? 2nd edit: after I tried this about 10 times, we went out to a party and I came back and I had at least a dozen error windows open in the admin console. A few of them said "Socket Open Failed java.io.IOException: An established connection was aborted by the software in your host machine". most of them said "Socket Open Failed java.net.SocketTimeoutException" Michel: when I "restore device" it gives me the frustrating "request failed". When I press the set button on the motion sensor, it toggles the lights, but it does NOT change the status readout in the ISY admin console.

Michel: when I "restore device" it gives me the frustrating "request failed". When I press the set button on the motion sensor, it toggles the lights, but it does NOT change the status readout in the ISY admin console.

here is a bug that I found in this version and in the .12 version: when an Insteon Motion sensor turns a light on, the status goes to ON, then later when the light goes off (because the motion sensor turned it off), the status stays ON. The only way to get the status to switch back to off is to manually query it.

Michel: uh, oh. I've got a HL2 PLM. What are my options to switch it out? Is the process of switching it reasonable or is it frought with problems?

look here for some info: http://forum.universal-devices.com/view ... highlight=

I'm having another problem while using 2.6.12: I am trying to add a new EZSwitch30 and it will not correctly add it to "my lighting". when I click "new insteon device" and put in the insteon address and with either "automatic" or by selecting EZSwitch30, here is what it does: a dialog box pops up and it says "removing existing links" (there are none it is a new device) and when it gets to about 8% the dialog box just vanishes. no error message, no new device in my list. Any solutions?

My ISY is not aware of any links for any of my controlLinc buttons, but they all do something. I tried a factory reset and the buttons still cause various lights (that they used to be linked to) to go on and off. Do I need to restore the controlLinc, the lights that they are connected to? Do I need to factory reset all of the switches that they are connected to and then restore them?

If I have a switch that I "restore" without factory resetting it, what will that accomplish? will it remove any broken links? here is the scenario: I have a controllinc that is giving me some trouble, I'd like to factory reset it and then restore all of the previously linked switches in hopes that this would remove the controllinc association.

I was getting this all the time. It seem to help when the motion sensor was placed very close to one of the access points while programming. I tried this and I still get "request failed". Here is what is interesting: It seems as though the changes that I try to make that end in "request failed" take affect. When I change the off-timer to 7 minutes, it works properly and when I link the sensor to a light, it turns on that light. it seems as though the system thinks it is't getting the job done, but it is. Michel: any ideas here?

I am using 2.6.12 and I linked my 2420 motion sensor. I tried to add it to a scene as a controller and I get "Request Failed". I tried this multiple times, putting it in programming mode with one press and sometimes with two presses of the button. I even did a factory reset, removed it from the isy and then started over. I get the same "Request Failed" when I try to change the off timer.

I tried this and it didn't work. here is where I suspect that most of the discussion about this will be: http://forum.universal-devices.com/view ... 4453#14453

I upgraded from 2.6.8 to 2.6.12 and my insteon skylink motion sensor went from being called what it is to being called "unsupported device: 16.0". It also has a ramp rate and on level as this unsuported device. How shall I fix this?

My understanding is that houselinc 2 is able to modify the off-timer for the skylink 2420 insteon motion sensor. Can the ISY-99i do this? if so, how? if not, when will it be able to do so and what is the best work-around?

I also would like to know what an open auto demand/response unit is. When you say that this version supports i2, I'm guessing that this is a newer version of storing or communicating insteon information. (when I search for i2 in this forum, nothing comes up... must be too short of a word) Will the i2 support allow me to use the EZX10RF better? If not, what will the i2 suppport help me with?

here is what I get when I do that, how do I make sense of this. a couple of questions: I don't have anything that sends out X-10 D4. I don't even have a wireless receiver that is set to D house code. Where could I find out how my outside lights got left on this morning when the ISY is programmed to turn them off? here is what my log said: if it bugs you that it is so long, then please delete some or all of it. INSTEON Device Control Value Time User Log Type 0 null Sat 11/08/2008 07:36:53 AM System Start 0 null Sat 11/08/2008 07:36:54 AM System -7029 Scene:My Lighting Status 0% Sat 11/08/2008 06:35:45 AM Program Log X10 D4 Sat 11/08/2008 06:37:47 AM System Log X10 D4 On (3) Sat 11/08/2008 06:37:48 AM System Log X10 D5 Sat 11/08/2008 06:37:51 AM System Log X10 D5 On (3) Sat 11/08/2008 06:37:51 AM System Log X10 D5 Sat 11/08/2008 06:37:58 AM System Log X10 D5 Off (11) Sat 11/08/2008 06:37:58 AM System Log X10 D4 Sat 11/08/2008 06:38:18 AM System Log X10 D4 On (3) Sat 11/08/2008 06:38:18 AM System Log X10 D4 Sat 11/08/2008 06:38:26 AM System Log X10 D4 On (3) Sat 11/08/2008 06:38:26 AM System Log X10 D4 Sat 11/08/2008 06:38:32 AM System Log X10 D4 On (3) Sat 11/08/2008 06:38:32 AM System Log X10 D4 Sat 11/08/2008 06:38:39 AM System Log X10 D4 On (3) Sat 11/08/2008 06:38:39 AM System Log X10 D4 Sat 11/08/2008 06:38:51 AM System Log X10 D4 Sat 11/08/2008 06:39:03 AM System Log X10 D4 On (3) Sat 11/08/2008 06:39:03 AM System Log X10 D4 Sat 11/08/2008 06:39:59 AM System Log X10 D4 On (3) Sat 11/08/2008 06:39:59 AM System Log X10 D4 Sat 11/08/2008 06:40:07 AM System Log X10 D4 On (3) Sat 11/08/2008 06:40:08 AM System Log X10 D4 Sat 11/08/2008 06:40:15 AM System Log X10 D4 On (3) Sat 11/08/2008 06:40:15 AM System Log X10 D4 Sat 11/08/2008 06:40:24 AM System Log X10 D4 On (3) Sat 11/08/2008 06:40:24 AM System Log X10 D4 Sat 11/08/2008 06:40:32 AM System Log X10 D4 On (3) Sat 11/08/2008 06:40:32 AM System Log X10 D4 Sat 11/08/2008 06:40:50 AM System Log X10 D4 On (3) Sat 11/08/2008 06:40:51 AM System Log X10 D4 Sat 11/08/2008 06:41:00 AM System Log X10 D4 On (3) Sat 11/08/2008 06:41:01 AM System Log edit: to shorten the readout above