Sixburg

Thanks, Lee. Powering down both the PLM and ISY first and then restarting the PLM first seems to have fixed the problem.

Hi Lee: 3 LEDs are on: Tx, Rx and Power. Glowing solid blue. The cable going from the ISY to the router is plugged on both ends and the indicator lights adjacent to the jacks are active. The router is configured for DHCP. The ISY does not appear the the wired devices table of the router (Netgear). It typically gets xxx.xxx.1.17. The cable from the ISY to the PLM is plugged in. No indicator lights on either end adjacent to the jacks themselves (I don't know if there are any or not). Now that I think about it, I did and power cycle on all the network gear today. I don't know for sure, but this could be related. It isn't the first time there's been planned or unplanned power outage so I'm skeptical that the cycling is the problem.

What was the resolution to this issue? I have what sounds like the exact same problem. Just today, lights weren't responding as they should so I tried to access the admin console and found it was blank. In the past a Java cache clear would solve this problem; however, the ISY doesn't even have an IP address. So it's impossible to follow the advice below (Tools | Error Log on the admin console) because it doesn't have an IP address. I've looked at all devices connected as per the router device table and the ISY is not there....it was yesterday and every other day for the past 2 years. Recap: blank admin console, no recent changes to the network, no static IPs, all DHCP Thanks for your help.

Thanks to everyone. LeeG nailed what I'm trying to do exactly. My apologies if my original intent was not clear to everyone. As LeeG stated the implementation for what I want is messy IF I control everything via program thereby resulting in unwanted delays. I'll either live with the delay, which allows me to more precisely control the light levels, or set specific levels regardless of what a user does with the paddle (i.e., "standard" = 60% and brighter = 100%...only allow 2 levels which works in my case). Re "writes to the MS", what I should have said is changes to what the MS does via "adjust scene". Thanks, again.

All: I have a situation in my kitchen wherein I have an MS and a 2477D dimmer switch. The MS sets light level to 60% upon motion sense. However, I'd like to use a program to handle the situation when someone either raises or lowers the light level manually on the switch paddle. Right now, the light level snaps back to 60% upon motion. To avoid this I'm thinking that if I can query the "new" light level set my the use of the switch, I can then set the MS to the new light level to avoid the MS either raising or lowering the level back to 60%. In effect, I want to write a program that says (pseudo): If status Kitchen Light is not 60% Then find out what the new light level is now In scene Kitchen MS set Kitchen light to new level Run the MS body program that has the wait x minutes Fade down Fade stop I understand that the writes to the MS will take 1-2 secs (WISH THERE WAS A FIX TO THAT DELAY), but I've no idea how to accomplish the above. Thanks! -Lloyd

Everyone, thanks for the inputs. Here's where I finally landed (it works for me and I can track and trigger off the state $vars!) in the event it could be helpful to anyone else. This very same structure is used throughout my house where an MS is used to trigger lighting... Kitchen Body 0 - Idle If $Kitchen_State is 0 Then Set Scene 'Scenes / Kitchen' Fade Down In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen KeyPad - Main' 55% (On Level) In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen Main' 55% (On Level) Else - No Actions - (To add one, press 'Action') Kitchen Body 2 - On (Note there is no Kitchen Body 1 since motion is handled in the Kitchen Cond 1 program) If $Kitchen_State is 2 Then Stop program 'Kitchen Cond 1 - Motion' In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen KeyPad - Main' 100% (On Level) In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen Main' 100% (On Level) Run Program 'Kitchen Cond 1 - Motion' (Then Path) Else - No Actions - (To add one, press 'Action') Kitchen Body 3 - Off If $Kitchen_State is 3 Then Set Scene 'Scenes / Kitchen' Fast Off Stop program 'Kitchen Cond 1 - Motion' In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen KeyPad - Main' 0% (On Level) In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen Main' 0% (On Level) $Kitchen_State = 0 Else - No Actions - (To add one, press 'Action') Kitchen Body 4 - FastOff If $Kitchen_State is 4 Then Set Scene 'Scenes / Kitchen' Fast Off Stop program 'Kitchen Cond 1 - Motion' In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen KeyPad - Main' 0% (On Level) In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen Main' 0% (On Level) Wait 15 minutes $Kitchen_State = 0 Else - No Actions - (To add one, press 'Action') Kitchen Cond 1 - Motion If Control 'Main Floor / Kitchen Motion-Sensor' is switched On Then $Kitchen_State = 1 Wait 3 minutes $Kitchen_State = 0 Else - No Actions - (To add one, press 'Action') Kitchen Cond 2 - On If Control 'Main Floor / Kitchen Main' is switched On Or Control 'Main Floor / Kitchen KeyPad - Main' is switched On Then $Kitchen_State = 2 Else - No Actions - (To add one, press 'Action') Kitchen Cond 3 - Off If Control 'Main Floor / Kitchen KeyPad - Main' is switched Off Or Control 'Main Floor / Kitchen Main' is switched Off Then $Kitchen_State = 3 Else - No Actions - (To add one, press 'Action') Kitchen Cond 4 - FastOff If Control 'Main Floor / Kitchen Main' is switched Fast Off Or Control 'Main Floor / Kitchen KeyPad - Main' is switched Fast Off Then $Garage_State = 4 Else - No Actions - (To add one, press 'Action') Kitchen Motion Light Level If Control 'Main Floor / Kitchen Motion-Sensor' is switched On And $Kitchen_State is 0 Then In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen Main' 55% (On Level) In Scene 'Main Floor / Kitchen Motion-Sensor' Set 'Main Floor / Kitchen KeyPad - Main' 55% (On Level) Else - No Actions - (To add one, press 'Action')

Hi Lee: The MS is in occupancy mode, sending On commands only, and has a time out of 30 seconds. I set the timeout at it's lowest so that it would send On commands at the fastest possible interval if it senses motion. By watching the LED I can see that the MS is registering movement and presumably sending additional On commands. By experiment I believe that my programs don't work because the Wait statement needs to be in the same program as the IF statement that tests for motion. In other words: If control ms is on then wait x mins set scene off else (empty) The additional On commands from the MS will trigger a test of this program and restart the wait statement. What I had done previously, which did not work, was to have 2 programs: one to test for the On condition of the MS and set a state variable flag =1, and an 2nd to test for that flag=1 and start the wait. It seems that even if motion is sensed the flag stays =1 and the wait statement just keeps on going without restarting. Let me know if I've diagnosed this correctly. Seems to work in testing. I'd also like to know if I should change the timeout on the MS. I assume I'm using this function properly given my programming set up. Thanks! -Lloyd

All, I thought I had this figured out, but evidently I do not. I have an MS (2842) to activate lights in my kitchen. The MS and switch are linked via scene. I have a SIMPLE pair of body and condition programs to control activities. The cond program checks for activity on the MS: Kitchen Cond 1 If Control 'Main Floor / Kitchen Motion-Sensor' is switched On Then $Kitchen_State = 1 Else - No Actions - (To add one, press 'Action') Kitchen Body 1 If $Kitchen_State is 1 Then Wait 1 minute $Kitchen_State = 0 Else - No Actions - (To add one, press 'Action') This works just fine in terms of being able to track the state of the "Kitchen" and the MS turns on the light. However, it doesn't seem like continued motion seen by the MS is causing the COND program to re-evaluate. I would expect that... - $Kitchen_State would stay = 1 (and it does) - The BODY program would reevaluate the IF as TRUE (seems to be since activity on Kitchen Body is "running then" and status is True) - And that the WAIT statement would restart the 1 minute countdown each time the MS registered motion. What is happening is the light goes out and comes right back on even if I'm waving my hand in front of the MS. What gives? Thanks! -Lloyd

Does anyone have any experience or information sources regarding iAqualink / Zodiac pool controls and Insteon / ISY? Would simply like to address common pool automation functions via ISY programs. Thanks!

There was a posting on this topic, but I never saw the resolution if any, so pardon the duplication here... In order to control the action of a 2420, say placed in a stairway with a SL dimmer, I've been writing ADJUST SCENE statements to determine whether or not the MS will actually light the SL at 100 or 0%. For example, sometimes when a user reaches the top of the stairwell they will reflexively switch off the SL. However, the MS still sees them and turns the light back on. With an ADJUST SCENE I can defeat the MS. But, not always in time for the user to clear the line of sight of the MS; therefore, the light turns right back on anyway. A few seconds later, giving ISY time to do the writes to the devices, and everything works fine. What's the resolution? Thanks!

There was a posting on this topic, but I never saw the resolution if any, so pardon the duplication here... In order to control the action of a 2420, say placed in a stairway with a SL dimmer, I've been writing ADJUST SCENE statements to determine whether or not the MS will actually light the SL at 100 or 0%. For example, sometimes when a user reaches the top of the stairwell they will reflexively switch off the SL. However, the MS still sees them and turns the light back on. With an ADJUST SCENE I can defeat the MS. But, not always in time for the user to clear the line of sight of the MS; therefore, the light turns right back on anyway. A few seconds later, giving ISY time to do the writes to the devices, and everything works fine. What's the resolution? Thanks!

Thanks again LeeG. Works like a charm. I didn't know that using IN SCENE in a program would control lighting levels AND preserve the speed given by linking the ms to sl in a scene. I've since seen other posts that address this, but none were as clear.

Im having trouble working with MS when it's included in a scene with a dimmer (sl). To achieve an immediate response upon motion I put both the ms and sl in the same scene. The ms is set to on only. A program controls the time until the light goes off. The light comes on to full power upon motion sense. What I can't figure out is how to "get between" the ms-sl link so that I get both an immediate response to motion AND have the ability to set various on levels or conditions. With a program that says "if control ms is on and dusk to dawn the next day, then adjust scene to 20% ..." all I get is instant on. It seems that the ma and sl in the same scene as I have it results in an instant on and no amount of programming can alter the scene before the light turns on. Is the trade off to take the ms out of the scene and live with the slow (1-2 sec) response time?

I have 2 rooms with identical devices set up the same, but acting differently. In each room there is a 2487s 6-button + 2477D (call it Bar and Kitchen). The bar and kitchen are 3-way switches. In the Bar, a press and hold of the On button (2487s) causes the lights to dim. Likewise, the 2477D dims the lights when holding the paddle for a short time. In the Kitchen, however, neither the 2477D nor the 2487S will dim the lights. Only fast on and off. The setups, done in the ISY is identical (or so it appears to be). Each room/devices are in a scene and both are controllers of the scene. But yet, one dims and the other doesn't (actually, I didn't think the dimming would work at all since one of the devices, the 6-button, doesn't have dimming capabilities). What gives? Maybe it has something to do with where the load is wired-in? Or, perhaps the scenes (which are very simple) constructed improperly? Thanks (again) for all the great advice and insight. -Lloyd

Thanks, LeeG. I followed your directions exactly and it works like a charm. The only other thing I added was to set the countdown timer on the MS to it's lowest setting (.5 mins). Even though it doesn't send an OFF command, I wanted to be certain that it "resets" or whatever it does during that .5 mins so that it's ready to sense any new motion. Additionally, I made sure the WAIT in the program is greater than the MS countdown. I'm not certain if my changes actually matter...my testing was inconclusive. Thanks again! Now it's off to a few more challenging set ups...