MikeB

Sorry, maybe I'm not being clear with what I'm saying. The problem isn't that it's querying the other devices - it's not. Like you said, the ISY already knows the status of those devices. The ISY simply re-evaluates the program if the state of ANY of the devices in the IF statement changes. If the program is once again true, it runs the THEN part. If the program becomes false, it runs the ELSE part.

Correct. The problem is that the ISY re-evaluates every time something in the IF condition changes. So, in your example here: If ( Status 'Dining' is not Off Or Status 'Dining.Table' is not Off Or Status 'Dining.Wall' is not Off Or Status 'Down.Land.Slave' is not Off Or Status 'Down.Land.Wall' is not Off Or Status 'Entry' is not Off Or Status 'Entry.Wall' is not Off Or Status 'Entry.Down.Land' is not Off Or Status 'Entry.Up.Land' is not Off Or Status 'Livingroom' is not 20% Or Status 'Livingroom.Wall' is not Off Or Status 'Livingroom.Mantle' is not Off Or Status 'Up.Land.Heart' is not Off Or Status 'Up.Land.Slave' is not Off ) Then Set Scene '-Living.Movie.C.State' Off Else Set Scene '-Living.Movie.C.State' On Let's say that your program becomes TRUE because, say, the 'Dining' room light gets turned on. Your program then sends an OFF command to the '-Living.Movie.C.State' button. Then, let's say the 'Dining.Table' light gets turned on as well. The ISY sees this, the program is re-evaluated, and the OFF command is once again sent to the '-Living.Movie.C.State' button. By checking the status of the KPL button in the IF statement, you can reduce that redundant traffic.

Definitely like Rand said, create a scene and add the lights you want to control to that scene. Then, in your IR programs, control the single scene (and not the individual devices). Good luck!

Hey Greg - My programs will only do it once either way (on to off or off to on). 1 - With powerline protocols, and specifically Insteon, there are potential problems any time there is simultaneous powerline traffic. Like, for example, pressing 2 switches at precisely the same time. 2 - The delay is more to separate the traffic rather than decrease it. But, it does save traffic if, for instance, my entire 1st floor is off but I turn a single light on for only 2 seconds - the ISY won't bother turning on the 1st floor status LED (because of the WAIT command).

In scenario 2, the 1st line in my example exists to check the status of the KPL button. If it's already OFF, it won't try to turn it off again. If the 1st line is deleted, the program will still work but it will create excess powerline traffic because the ISY will send a command to turn that KPL button off every time a light in my theater changes (and it's not set to those exact levels). In scenario 3, I use separate programs to monitor the status of areas in my home because I use those programs with other buttons that turn off different groups of lights. For example, at my garage entrance I have a single button that monitors the majority of my house (minus my theater room and office) and turns off the majority of my house with a single press. Here are the programs I use for that: FLOOR1+2+MB STATUS ON If Status 'GarageControls2F' is not On And ( Program 'Floor 1 Status' is True Or Program 'Floor 2 Status' is True Or Program 'MasterBedArea Status' is True ) Then Wait 8 seconds Set Scene 'Floor1+2StatusLight' On Else - No Actions - (To add one, press 'Action') FLOOR1+2+MB STATUS OFF If Status 'GarageControls2F' is not Off And Program 'Floor 1 Status' is False And Program 'Floor 2 Status' is False And Program 'MasterBedArea Status' is False Then Wait 8 seconds Set Scene 'Floor1+2StatusLight' Off Else - No Actions - (To add one, press 'Action') FLOOR1+2+MB CONTROL OFF If Control 'GarageControls2F' is switched Off Then Set Scene 'MasterBedAreaAll' Off Set Scene 'Floor2All' Off Set Scene 'Floor1All' Off Else - No Actions - (To add one, press 'Action') Note 2 things about my status programs: - I use a WAIT command before I turn on/off status lights because I don't want the ISY to bother changing the status light if someone quickly turns a light on or off for a second or two. This also helps make sure the powerline is clear of traffic before the ISY changes the status button. - I stagger the length of the WAIT for different buttons to ensure there are no powerline collisions. I don't want to turn on/off multiple status buttons too close together, or the function may become a bit less reliable. Again, only problem I see with your example is that every time your lights change, but your program is still true, your ISY will send another command to turn that KPL off. Might not be a problem for you, but I personally try to minimize powerline traffic as much as possible to improve reliability. Multiple things going on on the powerline at once can/will cause issues. Hope this clarifies what I'm doing for you.

That's all up to you, and I do a variety of things depending on what I want to accomplish in my home. Scenario 1: I have a bunch of KPL buttons that all control a single light or group of lights in the same manner. For example, I have 4 KPL secondary buttons that control my front door lights around my house (foyer, garage, theater room, master bedroom). To accomplish this, I simply create a scene called "Front Door Lights" and make all KPL secondaries controllers of that scene. Mission accomplished. When the front door lights are turned off from any location, all KPL buttons turn off. If they are turned on, all KPL buttons turn on. Scenario 2: I have a KPL secondary buttons that set different lighting scenes or "moods" in many of the rooms in our house. For example, in my theater room I have a "dinner" scene button, a "movie" scene button and a "party" scene button. Each button sets the lights in the room to different levels. I want to make sure then if I hit the "dinner" scene button, lights turn on to specific levels - but if the lights are changed, either manually or by pressing a different scene button, I want the "dinner" button to turn off. I accomplish this by creating scenes in the ISY and making the KPL secondary a controller of that scene. I set the levels how I want them so that when the KPL secondary is pressed, the lights change to how I want them. To keep the KPL buttons "accurate" I use programs to turn the buttons OFF if the lighting levels change. For example, my theater room "movie" scene sets my table lights to 30% and my main lights to 20%. I use the following program to turn the button (TheaterMovieStatus) off if the lighting levels change: If Status 'TheaterControls1G' is not Off And ( Status 'TheaterControls1A-Table' is not 30% Or Status 'TheaterMain1' is not 20% Or Status 'TheaterMain2' is not 20% ) Then Set Scene 'TheaterMovieStatus' Off Else - No Actions - (To add one, press 'Action') Scenario 3: I have a few locations (garage entrance, foyer entrance, master bedroom) where I have KPL buttons that are able to turn off entire floors of my home (before bed or when we're leaving). I also want the KPL buttons to light up if any lights are on, and NOT be lit up if all lights are off. I tried accomplishing this a few different ways, but the way that is working best for me is as follows. I grouped areas of my house such as "1st floor", "2nd floor", "master bed area". I then created programs that monitor whether or not a light is on in those areas. For example, to monitor my 1st floor lights I use the following program: If Status 'Bathroom1stLaundry1' is not Off Or Status 'Bathroom1stMirror1' is not Off Or Status 'Bathroom1stVent1' is not Off Or Status 'FoyerMain1' is not Off Or Status 'KitchenBar1' is not Off Or Status 'KitchenMain1' is not Off Or Status 'KitchenSink1' is not Off Or Status 'KitchenTable1' is not Off Or Status 'LivingRoomControls1A' is not Off Or Status 'LivingRoomMain1' is not Off Or Status 'PlayRoomMain1' is not Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') This program is TRUE if anything is left ON on my 1st floor. If it is FALSE, all devices are off. I have a KPL button in my master bedroom that is set to 'non-toggle off' mode. I use these programs to light the button if the program is TRUE, but turn off the button if the program is false: If Status 'MasterBedControls1G' is not On Program 'Floor 1 Status' is True Then Wait 4 seconds Set Scene 'Floor1StatusLight' On Else - No Actions - (To add one, press 'Action') If Status 'MasterBedControls1G' is not Off Program 'Floor 1 Status' is False Then Wait 4 seconds Set Scene 'Floor1StatusLight' Off Else - No Actions - (To add one, press 'Action') Finally, I use the following program to turn all my 1st floor lights OFF if that button is pressed: If Control 'MasterBedControls1G' is switched Off Then Set Scene 'Floor1All' Off Else - No Actions - (To add one, press 'Action') Hope this help. Please let me know if you have any questions or need more detail.

The Linksys and Windows firewalls would not cause your problems, but Kaspersky (and other 3rd party firewalls) might, as they tend to be overbearing. Check out this thread: http://forum.universal-devices.com/view ... =kaspersky

Yes. Or, if you want to be sure the prorgam runs if the device is turned ON by a scene, use status for both.

Just confirmed it - it works fine.

Now that I think of it, I could probably combine the first 2 programs like this: THEATER ON/OFF If IR '1' is Pressed And IR '2' is not Pressed Then Set Scene 'TheaterMain' On Else Set Scene 'TheaterMain' Off I haven't tested this...

Hey Michael - I do that using 4 programs. The following example uses a scene, but a signle device would be the same. THEATER ON If IR '1' is Pressed Then Set Scene 'TheaterMain' On Else - No Actions - (To add one, press 'Action') THEATER OFF If IR '2' is Pressed Then Set Scene 'TheaterMain' Off Else - No Actions - (To add one, press 'Action') THEATER BRIGHT If IR '1' is Held And IR '1' is not Released Then Set Scene 'TheaterMain' Fade Up Else Set Scene 'TheaterMain' Fade Stop THEATER DIM If IR '2' is Held And IR '2' is not Released Then Set Scene 'TheaterMain' Fade Down Else Set Scene 'TheaterMain' Fade Stop

Hey Michel - FYI, firmware I am running seems to be working OK with notifications to my own internal SMTP server (port 25).

Yes, your motherboard needs to support 'wake on USB'. Pretty much any fairly modern motherboard should I would think. Glad it worked for you!

You can setup your PC to power down into S3 standby mode. When in this mode, your PC can be woken up via remote control. I know this from first-hand experience - I have 4 home theater PCs in my home configured in this way. I power them down with a MediaCenter PC power button, and power them up with the same. While S3 standby is not technically OFF, it's close enough. No noise, no fans, etc.

Universal Devices is working on a native IR transmitter for the ISY. Also, Smarthome's IR transmitter is soon to be released: http://www.techmall.com/topic.asp?TOPIC_ID=4957

I have a few programs that run based on the press of a KPL secondary, such as: These still seem to be working fine here. Let me know if I can try to duplicate the issue here.

I am set to automatic here. Just to test the fuction, I took the 1st device in my list (a SwitchLinc Relay v.2C) and read the device table links (came up with 4). I ran a compare and the ISY shows 3 (marked the last one as an 'extra record'. BUT that last one is: [Extra record] 0FE0 : 00 06 09.92.84 00 1F 01 Doesn't the 00 mean it's a 'deleted' record? I then right-clicked and restored the device, and the table does not change - it still shows that 4th record. If I am correct and that is a deleted record, perhaps in the link table when doing a comparison the gui should mark it as 'deleted - ignore' or something similar.

When I open the Admin Console, I'm also seeing blank weather data in the STATUS box under the CLIMATE tab. The only thing there is the "WeatherBug RSS" link. HOWEVER, if I open up the HTML version of the ISY's weather page in a new tab, the weather information instantly populates in my Admin Console. So, to duplicate, you should be able to: - open Admin Console, observe blank weather data - go back to your browser's ISY page, right-click "Weather" and choose OPEN IN NEW TAB Once the tab opens with the weather data, the Admin Console should also show weather data. PS - My Thermostat Adapter is still working well.

My Thermostat Adapter seemed a bit wonky at first too, but now it seems fine for some reason. Here's what happened: - performed a query, seemed to complete successfully but took about 15 seconds - which seemed exceptionally long - tried a setpoint down, dialog box came up and indicated an error communicating with my RemoteLinc (???), then sat there for 2-3 minutes on the progress bar - once that completed (without further error), the thermostat adapter now seems to be responding fine to queries and set point changes I rebooted my ISY, and tested again - it still seems good at this point. My Thermostat Adapter is reported as a v.24 on the ISY's Admin Console.

You should be able to do this: If Control 'Remote1' is switched On and Control 'Remote1' is not switched Off Then Set Scene 'Lights' On Else Set Scene 'Lights' Off But like Michel said, probably better to find the root of your problem.

That's an option. If you have an ISY-99, you would need to purchase a separate AC adapter to power the ISY (plugged into the UPS). You would need to keep the PLM on an outlet (do not plug it into a UPS). You might need a FilterLinc if the UPS will be plugged into an outlet next to the PLM as UPSs are known to sometimes cause communication issues.

Hey Mike - I think I asked you this before, but I just wanted to double-check. Do you have any devices that report their statuses to the ISY intermittently? If so, when they do not report their status, is there ANY traffic at all in the Event Viewer when you press the switch?

Do you have the Motion Sensor to "on only mode"? If so, I believe this would be normal. In it's normal on/off mode, the motion sensor will send an ON command when it sees motion, then will send an OFF command (which the ISY will show) when there is no motion for a specified period of time (default is 1 minute I believe).

The status of KeypadLinc secondary buttons are not queryable. The only way the ISY knows the status of these buttons is if they are pressed (or controlled from the ISY via a scene). Once this happens, the ISY 'remembers' the status of they button and tracks all future status changes. If the ISY was rebooted, for example, the status of all KeypadLinc secondaries would be blank until something turns them on or off. Are you rebooting your ISY for some reason?

Remember that the state will show blank until the button is pressed for the first time. If you're hitting the button, and it's still showing as blank, I would right-click the KPL and try a RESTORE DEVICE.