MikeB

If I create a program that contains both an 'and' and an 'or' in the IF statement, how does it get parsed? IF status "switch 1" is on and status of "switch 2" is on or status of "switch 3" is on Is it parsed like this: IF [status "switch 1" is on and status of "switch 2" is on] or status of "switch 3" is on or like this: IF status "switch 1" is on and [status of "switch 2" is on or status of "switch 3" is on] It might be nice to clarify that in the program content window when the commands are entered.

Thanks Michel. I've found i prefer using the secondary KPL to trigger an ISY-26 program that sets my scene anyway, so it's not going to be an issue for me.

LOL, just when I post this...

Want to make sure I understand this before I go too far - If I have a KPL with a load and an on-level of 100%, I can't create a scene controlled by one of its secondaries that sets that same load to 60%, correct? If I understand correctly, the work around would be to create a scene and trigger that scene by a program on the ISY-26, which executes when I press the secondary, correct? Thanks!

Awesome, thanks! Should I remove that ELSE command then? It seems like it's useless.

Thanks Chris. Just curious - any reason why the RESTORE PLM doesn't simply create PLM links in the devices for the new PLM, even if they don't have any existing PLM links?

Thanks for the clarification Chris. So, if I'm understanding this right: ..my understanding is that if you do a REMOVE PLM, and all your old PLM links are gone, and then you try to do a RESTORE PLM, it will not see the old PLM links in the devices, so it will not add the new PLM links in the devices. Correct?

One more question... Why isn't this ELSE statement in my first program working?: Else Set Scene 'OfficeStatusLight' Off With this ELSE statement, I would think that if someone accidentally pressed my KPL status light to turn it ON, and all my office lights were OFF, that the status light would turn itself back off. It doesn't seem to work like I would think, which is why I had to create my 'fix' program. Can someone clue me in?

OK, correction - my 2nd try is now working. I realized the ISY wasn't getting status updates from my KPL unless I did a query. I removed and re-added the device, and now it's working. So, here's what I've done, using my office as an example: Created a scene called "OfficeStatusLight" which contains the KPL secondary button "OfficeKeypadH". This button will be used to turn off my office lights. Its backlight will be on if any of my office lights are on. I also created a scene called "OfficeAll" which contains all of my office lights as responders. I created a program called "OfficeStatusProgram", which runs the following: If Status 'Office1' is On Or Status 'Office2' is On Or Status 'OfficeCounter' is On Then Set Scene 'OfficeStatusLight' On Else Set Scene 'OfficeStatusLight' Off This allows me to see the status of my office lights. If any are left on, my "OfficeKeypadH" button will be lit up. However, I still don't have control. All I want is to be able to turn all the office lights OFF. I DON'T want the ability to turn them all on. So, I created the following program: If Control 'OfficeKeypadH' is switched Off Then Set Scene 'OfficeAll' Off Else - No Actions - (To add one, press 'Action') This allows me to turn all of my office lights off simply by pressing my "OfficeKeypadH" button to turn it off. The only thing I didn't like about this is that if my office lights are off (which means the OfficeKeypadH is off), someone could accidentally press the keypad button to turn the backlight on, making it look like an office light was left on. To avoid this, I created the following "fix" program: If Control 'OfficeKeypadH' is switched On Then Set Scene 'OfficeStatusLight' Off Else - No Actions - (To add one, press 'Action') This will "correct" someone accidentally pressing that button, by immediately turning it back off. This seems to be working well for me (at least in my initial testing). Anyone have any comments on how I might do this more efficiently? Am I missing something? Also, if I wanted to have a single Keypad LED indicate if ANY light in my house was left on, I would have to create a huge program - with 60+ IF statements as conditions. Is this a problem for the ISY-26? Thanks guys...

I understand, but wouldn't you want that? Your new PLM will undoubtedly have a new address, so why would you want to keep links from the devices to your old PLM?

Comment and a question... Comment: I just replaced my PLM, and had a problem where the ISY kept coming back with an 'Request Failed' error. I didn't realize it was also trying to link my RemoteLincs to the PLM. If you have any RemoteLincs, be sure to put them into Linking Mode before restoring the PLM. Question: Just curious - if you're doing a 'restore PLM' anyway, what's the harm in removing links to your old PLM? What am I missing? Thanks

OK - here we go... I've been playing with this a bit today, and haven't had much luck. Like I said, to turn entire floors off at night I simply have a KeypadLinc Secondary linked as a controller to a scene containing the entire floor. This button is set to non-toggle mode off, so at night we simply press "1ST FLOOR OFF" and the entire first floor turns off. Since the button is a non-toggle off, you can't accidentally turn on an entire floor. Exactly what I want, with one limitation - we don't really know if there's anything actually left on. 1ST TRY: First I created a scene called 1stFloorStatus. I added the button KPLH as a responder of that scene. I then tried creating a group called 1stFloorAll. I added all my 1st floor lights to this group, and also added KPLH as a controller. I set this button to non-toggle OFF. I tested it's operation - the backlight is always off, and when I press the button it turns everything on the 1st floor off. Exactly what I want for control, but still no status. I then created a program that said basically if any of the lights on the 1st floor had a status of ON, turn the 1stFloorStatus ON, else turn it OFF. This worked - if any of the lights were on, the KPLH button's backlight turned on. If I turned all the lights off, the backlight went off. However, if any lights (and backlight) are on, and I press the KPLH button, it sends an ON command to all the lights - which I don't want. I only want to be able to turn the lights OFF from KPLH. 2ND TRY: I again created the scene 1stFloorStatus containing KPLH, and created scene calle 1stFloorAll contraining all my 1st floor lights. However, this time, I didn't add KPLH to that scene. Instead, I created a program that said if KPLH control is turned OFF, then turn off 1stFloorAll. I also kept the program that turned 1stFloorStatus on or off based on the status of the lights. KPLH's backlight turns on and off depending on the status of the 1st floor lights - however, pressing the button to turn KPLH OFF doesn't do anything. I have a feeling this is because KPLH does not send a signal to the PLM when it is turned off. Is this correct? Any other suggestions?

My RemoteLincs (older silver ones, and a relatively new black one) all exit linking mode after 4 mins - no matter what.

Yes, do an ipconfig /all and write down all the values. Change the IP to whatever you want it to be, and keep the rest the same.

Windows XP? Make sure you're choosing the option on the left-hand side of My Network Places that says "Show icons for networked UPnP devices".

Thanks. I'm very interested in how you make out. If I get some time over the next few days, I may experiment here as well. Like I mentioned, in my master bedroom I have a KPL button that is a controller of the scene '1st floor off' that contains all of my 1st floor lights & vents. They are all responders of this scene. The KPL button is set to non-toggle off so that I can simply press it before going to bed, and have everything downstairs turn off. Works great, but there's no real indication that something is actually on down there. It would be nice to have that indication. An indicator light seems easy enough, I think... just make a program that says 'if light1 is on or light2 is on or light3 is on..." then scene "indicator1" is on. Else, it is off. But, how do you make that same button control that group of lights? If I had room in my KPL, I'd just keep 2 KPL buttons. I'd keep my current '1st floor off' and make a '1st floor status' KPL button right above it that acts as an indicator. Or is there a better way that I'm missing?

I currently have a couple buttons that I use for "1st floor off" and "2nd floor off". They're simply KPL buttons in non-toggle off mode that are controllers of all my switches. I'd love to have some kind of indication that a light was left on, but I believe I'd need to take the button out of non-toggle mode to get that. I don't really like the idea of accidentally pushing a single button and turning all the lights/vents on. Maybe if I had some extra buttons available on my KPL I could make one button an indicator like you're suggesting, but use a 2nd button in non-toggle mode off to actually turn the lights off. What are your plans?

Hey Thom - Good luck! There is hope. I may not have as many as you, but I have surge strips everywhere, 5 UPSs throughout the house, a Monster line conditioner, a dozen or so CFLs, a bunch of fluorescents, 9 PCs, a bunch of servers, outdoor low voltage landscape lighting, etc.... and my reliability has been great. Once I got a decent amount of Insteon installed my reliability has been almost perfect. I had ONE KPL that intermittently did not receive a command, and it turned out to be a cheap surge strip causing noise on my line. Go figure. I ended up just ditching and replacing it. I do have a few FilterLincs installed in key places "just in case". Good luck, and please let us know how you make out.

Keep in mind that there are 2 PLM issues we are dealing with here. 1 - Updated firmware. This should help lockup issues. 2 - Additional memory. This should help users who are exceeding the PLM's 417 link limit. We may see an updated firmware before we see a unit with additional memory. Again, I'm just guessing, but I wouldn't be surprised if a PLM with more memory was released as an additional product - above the existing PLM in the product line - for users who need the ability to store over 417 links.

Yeah, I'm sure FilterLincs in the right place would help. BUT - be sure to throw one of your AccessPoints onto your PLM as well. If you don't already have one there, that change alone might be enough to overcome any noise issues. Please let me know your results.

Haha, I'm sure you'll love it!

My day 3 report is up: http://www.techav.com/ehx/ehxfall2007.htm Not too much to add, but a few more pictures.

Hey Thom - Sounds like your Insteon communication is just a bit shaky. Do you have AccessPoints installed to bridge your phases? If you do, throw one on top of your PLM (then make sure the other one is still on an opposite phase). If you don't have AccessPoints, you should purchase 2 or 3 and install them. I'd personally go with 3 (2 to bridge your phases, the 3rd to throw on the PLM).

My Elk is still unopened, was away at EHX most of last week. I'm hoping to get to it sometime over the next 2-3 weeks.

Try plugging one of the AccessPoints onto the back of the PLM to help your signal.