MikeB

Absolutely just add a 2nd controller to your scene - saves time and links. So, you have a scene containing 2476D dimmers and a RemoteLinc as a controller, but hitting the RemoteLinc button ON does not turn on the 2476Ds? That should work. In the scene, click on the RemoteLinc controller button and make sure the on levels are set correctly.

I haven't used the ToggleLincs, but even with SwitchLincs it takes some practice to get the timing right. You need to be about as quick as a standard mouse double-click.

Sounds like you just need to create a scene, with both the KPL secondary and InlineLinc as responders. Unless I'm misunderstanding, in your scenario there are no true controllers - the ISY is the only controller. When the ISY turns on the scene, the KPL lights up and the InlineLinc goes on. When the ISY turns off the scene, both go off. You could also create a program on the ISY that checks the status of the KPL secondary and turns it back off if someone accidentally presses it.

Yes - the ISY-99's current beta firmware (2.6.3) has an HTML interface.

You can use the IP address of the ISY. Make sure you are running the latest firmware (beta 2.6.3).

You can access the ISY through its HTML interface from the Nokia N800's web browser. As for Java on the N800, check out Jalimo. We have a front-end for the ISY coming out shortly specifically written for the Nokia N800. Check out the link in my sig.

To apply the ramp rate/on level changes to a SwitchLinc all you need to do is pull the air gap out for 5-10 seconds, then pop it back in to its normal position - do not push and hold it fully in. You do not lose any existing links with the above described soft reboot.

The only way would be to create a separate scene for each KPL secondary button you want to control. Call the scenes "KPL Button B", "KPL Button C", etc..

I had access to an older Blackberry 7250 today, so thought I'd give it a try. I was able to control my lights OK, did about 10-12 ON/OFFs through the HTML interface and didn't experience a lockup. This is on an ISY-99/IR Pro running firmware 2.6.3. This was a Verizon Blackberry.

Anyone heading down this week?

Definitely try closing and restarting your browser, also clear out your Java cache.

My opinion - factory reset each device and recreate your links. You'll be sure to have a clean system. The ISY makes it so easy to recreate your scenes, you'll be back up and running in no time..

Do you have the latest Java installed on your PC? http://www.java.com

True, but then if my son has his lamps on when I hit my '2nd floor off' button, his lamps will go off but his KPL secondaries will not. Unless of course I keep my 'fix' programs, which will have to run every time I use my '2nd floor off' button and his lamps are on. So, I think I will keep my KPL secondaries in the scene, and my 'fix' program will only run of someone accidentally presses my '2nd floor off' button ON (which really should never happen). Here is what I'm running. I tested it a bit last night, and it seems good. I'm going to adjust my WAIT values a bit, but wanted to start a bit high: FLOOR 2 STATUS If Status 'AndyBedCloset1' is not Off Or Status 'AndyBedControls1C' is not Off Or Status 'AndyBedControls1D' is not Off Or Status 'AndyBedLamp1' is not Off Or Status 'Bathroom2ndMain1' is not Off Or Status 'Bathroom2ndMirror1' is not Off Or Status 'Bathroom2ndVent1' is not Off Or Status 'MikeyBedCloset1' is not Off Or Status 'MikeyBedLamp1' is not Off Or Status 'SpareBedCloset1' is not Off Or Status 'SpareBedLamp1' is not Off Or Status 'Stairway1' is not Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') FLOOR 2 STATUS OFF If Status 'MasterBedControls1H' is not Off And Program 'Floor 2 Status' is False Then Wait 4 seconds Set Scene 'Floor2StatusLight' Off Else - No Actions - (To add one, press 'Action') FLOOR 2 STATUS ON If Status 'MasterBedControls1H' is Off And Program 'Floor 2 Status' is True Then Wait 4 seconds Set Scene 'Floor2StatusLight' On Else - No Actions - (To add one, press 'Action') ANDYBEDLAMPB FIX If Status 'AndyBedLampModule2' is Off And Status 'AndyBedControls1C' is not Off Then Wait 1 second Set Scene 'AndyBedLampB' Off Else - No Actions - (To add one, press 'Action') ANDYBEDLAMPC FIX If Status 'AndyBedLampModule3' is Off And Status 'AndyBedControls1D' is not Off Then Wait 1 second Set Scene 'AndyBedLampC' Off Else - No Actions - (To add one, press 'Action') Thanks again Joe!

I thought you checked and your v1.75 labeled PLM had v63 firmware? Does seem odd... I'd give SmartHome a call to check what's up.

I'll try to explain... For example, in my son's bedroom I have a KPL at his bedside in a tabletop enclosure. 2 of the secondaries on that KPL are linked to 2 LampLincs in his room so he can control each of his lamps from his bed. Both the KPL secondaries and both LampLincs are members of my '2nd floor off' scene. The LampLincs are set with an 'on level' of 0 - that way, if my '2nd floor off' KPL secondary control button is off (becuase all the lights are off), and someone accidentally presses it ON, my lights will not go on. However, KPL secondaries do not have 'on levels', they will go ON when my '2nd floor off' scene is pressed ON. So, I have 2 problems if that '2nd floor off' button is pressed ON: 1 - Because my '2nd floor off' status program checks the status of those KPL secondaries, it shows as 'true'. This is easily fixable - I can simply not check the status of those secondaries, but check the LampLincs instead. 2 - The KPL secondaries controlling the lamps are left on, even though the LampLincs are off. I could write programs to say 'if LampLincA is off, and KPLSecondaryA is not off, then turn KPLSecondaryA off'. This should 'fix' the issue, but create some extra traffic and complexity. Does this make more sense?

Got my PLM in today, it is labeled v2.75. I'd bet that the v1.75 label is a type-o.

Hey Blue - Thanks for the reply. I was doing that as well for KPL secondary 'scene' buttons, but since I've upgraded to v1.65 KPLs I am now using the KPL secondary as a controller of the scene, but run ISY programs like to to turn the KPL secondary off when the scene is no longer true. However, the KPL secondaries I'm having issues with are not 'scene' controllers - they are linked 1 to 1 to control individual lamp modules, so I don't use any programs to control their status. I could write a program to 'fix' their status if they get out of sync however.. I'll have to put some thought into that. Thanks!

??? Not sure I follow you. I don't know if it will be different. Like I posted above I'll report back what the rev label and firmware version is.

Thanks for the reply, Joe. I read your post a few times, but I'm not sure I follow. I do have these KPL secondaries in my status check program, which is actually how I noticed the issue. I was racking my brain on this for a while, because what would happen is I would press my '2nd floor off' button ON, and it would stay on, and the status check program would stay true! A scan through My Lighting showed that all my 2nd floor lights were OFF, which meant the program should show false. After a while of playing with it, it finally dawned on my that the KPL secondaries don't show in My Lighting, and those were the devices that showed as ON. So, basically what happens in my system is if someone accidentally presses the '2nd floor off' button ON, the KPL secondaries go ON, and the status button stays ON as well, until it's pressed OFF. So, sorry for being dense, but could you explain your suggested workaround with a bit more detail? Thanks!

I have a unit coming in tomorrow, I'll post back with what it's labeled. My previous extended memory PLM was labeled Rev 2.75, and firmware was v63.

Check out this tool: http://busyrat.com/plmtest

One issue I've found so far with this method... I'm pretty anal about trying to make my lighting controls bulletproof. One thing that concerns me is if someone presses the '2nd floor off' KPL button ON. By setting the on levels for all devices to 0, theoretically that's OK - the lights will stay off and the button will turn itself back off because of the status check program. However, what won't work well is any KPL secondaries that are members of the '2nd floor off' scene. KPL secondaries do not have on levels, so they will turn ON when this button is pushed. This also throws off my status check program, which I use to check the status of a coulple KPL secondaries on the 2nd floor. I know this isn't a huge deal, but it's an annoyance for me....

When you create your program to turn on the LampLinc via IR, turn on the entire scene instead. This will ensure everything in the scene is turned on (the LampLinc and KPL secondary).

My understanding is that Rev 2.7 and lower have the standard memory, while Rev 2.75 (and above) are extended memory. I've never seen one labeled Rev 1.75 - I wonder if it's a type-o?