Xathros

Palmer082- It is not necessary to get rid of the folder, just the folder conditions. Folders are very useful for organizing your programs. I have many folders in my programs tree - very few with folder conditions. -Xathros

BriG- Here is a thought, If you change your first program to: If Control 'Closet Lights' is Switched On It will work the same way BUT if you turn on the already on light, it will reset the countdown for another full 30. -Xathros

wired64- Since you are using Keypads to control your scenes, you can use the "Control" and "Status" of your KPL buttons to fire programs that manages the security light. Here is my thoughts: Assuming 3 KPLs (KPL-1,KPL-2 & KPL-3) and assuming the Party scene is Button C on each of those. If Control KPL-1-C is Switched On or Control KPL-2-C is Switched On or Control KPL-3-C is Switched On Then Set Security Light Off If Status KPL-1-C is Off Then Set Security Light On -Xathros

arw01- What is the rating on the Microwave? You may have exceeded the rating of the filterlinc. Tha AF-120 is a good filter up to 15A but is better than twice the size of a filterlinc. It also has a user replaceable fuse unlike the filterlinc. -Xathros

Happy to help anytime I can. -Xathros

jmed999- I believe (LeeG may have to correct me) that the PLM (assuming 2413S Dualband) sends both Powerline and RF. Any non-battery powered Insteon device receiving this transmission that isn't the Addressee, will decrement the hop count by one and retransmit on both the powerline and RF (If dualband). So the powerline can very well still be involved even if the PLM is addressing an RF only device since the bridging devices in between can be communicating via powerline. -Xathros

Yeah. I just looked over Mobilinc on my Galaxy Tab and I'm afraid you are quite correct. The Android version seems to be somewhat less mature than the iOS and these features, I'm fairly sure, will come with time. For those on the iOS version of Mobilinc, here are some screenshots: FWIW, The Very Pretty iPad MobilincHD falls short on the custom program icons too! Mobilinc Tip: The "." prefix in .Dad-Open-Close and .Mom-Open-Close is to force these two favorites to sort to the top of the list. Seems the only way to force things to the bottom is to prefix with a "z". -Xathros

I set the custom Icon on the favorite to "Garage Door Reversed" and it represents the proper door status in its dual mode icon. One other tip: set the custom status for "Running Then" to "Door in motion" -Xathros

Hi PLCGuy- I don't know much of anything about Elk but I can tell you that a CAI board has a lot to offer. Digital and Analog IO along with a OneWire input for temp sensors and a Humidity sensor input. Fairly inexpensive, newer versions have direct support setting ISY variables via REST and rock solid stable. Only thing better would be if they brought all the connections to screw terminals and put it in an enclosure but that would likely increase the cost significantly. The CAI board will certainly work for your current need and leave you with a lot of additional capabilities for expansion down the road. -Xathros

LeeG, Michel, MWareman- Dunno if this helps or not but the Wayback Machine found it for me. http://web.archive.org/web/201211241041 ... n_time.htm -Xathros

It's an Integer NOT a state variable for that and a few other reasons. Note the i.Dad... instead of s.Dad... -Xathros

All- Sorry for the delay, been distracted over the last week or so. I have this working well with Mobilinc. It took me a while to work out the details. Here is how it works: I did not use any scenes other than for managing KPL button statuses. (Scene 'Garage / Garage-Dad') My Favorite in Mobilinc is a program. I run Then as the favorite press. I use an integer variable that follows door status. Open = 1, Closed = 0 The If Statement in the program only looks at the integer variable. I turn the relay off after 10 seconds because I like it to say off - doesn't need to be there. This is my Open Close program (Run then from Mobilinc) If $i.Dad_GD_Status is 1 Then Set 'Garage / Garage Door IOLinks / GD- Dad Garage Door Relay' 100% Wait 10 seconds Set 'Garage / Garage Door IOLinks / GD- Dad Garage Door Relay' Off Else - No Actions - (To add one, press 'Action') This Program Monitors Door Status: If Status 'Garage / Garage Door IOLinks / GD- Dad Garage Door Sensor' is Off Then Set Scene 'Garage / Garage-Dad' Off Resource 'Syslog-SECRTY - Dad Garage Door Closed' $i.Dad_GD_Status = 0 $i.Dad_GD_Status Init To $i.Dad_GD_Status Run Program '.Dad-Open-Close' (Else Path) Else Set Scene 'Garage / Garage-Dad' 100% Resource 'Syslog-SECRTY - Dad Garage Door Opened' $i.Dad_GD_Status = 1 $i.Dad_GD_Status Init To $i.Dad_GD_Status The whole point of the $i.Dad_GD_Status mvar is to allow the initial program status to be true or false for mobilinc status feedback. The program runs true whenever you run then. Status monitor runs Else (False) when door is fully closed. I have set custom statuses in ML that say Opened for True and Closed For False. Hope that makes sense. -Xathros

Andy- I'm pretty sure this is a bug in the OS X 10.8.3 finder. The Java file chooser didn't work on 10.8.3 so UDI reverted back to using the MAC finder. At least we can easily work around this until Apple fixes it. -Xathros

I had a few I2CS devices do strange things like this after upgrading to 3.3.10 (I think) and in each case, I was able to resolve these issues by right clicking on the affected device and selecting Query Insteon Engine. Being that the ramp rate changed, you may also need to check and fix that setting as well. HTH -Xathros

Maybe consider pairing up the cans thus reducing the insteon investment to 3-4 rather than 6-8 devices. My preference would be a gang of Switchlinc Dimmers rather than inlinelincs. Either way, you could use a KPL for setting your scenes. -Xathros

I do it like this: If Then Repeat every 1 minute i.timecntr =+ 1 Very much the same concept as jmed999 posted. -Xathros

Michel- Isn't the address sales@universal-devices.com (plural) rather than sale@...? -Xathros

New MS is an I2CS device which requires ISY Firmware version 3.2.6 or later. What Firmware are you running? -Xathros

I really think that a simple delay would be easier to deal with rather than trying to track direction and count with non directional sensors. I think it would be cool to have the lights dissolve as you arrive at the opposite end of the staircase but that could likely be accomplished more easily by calculating the average traversal time for the stairs and using that for the delay. There are a number of problems that you would need to overcome in the counting of the sensor activations and avoiding false counts (multiple legs etc) and one of the bigger issues you may find is the process delay involved when you want your lights to respond instantly to a trigger activation. The more you try to do there, the longer the delay will be. The simple delay will help avoid the problems when two people pass on the stairs and with the current design, the delay would restart in the event two people headed downstairs say 8 seconds apart giving the second person the full delay with the lights on. -Xathros

easy enough to include the time and status of the other lights as conditions in your trigger program. I am assuming that the other lights will be Insteon as well. If Control BottomStairIOLincSensor is Switched On (Assuming here that you are using IOLincs to interface to your PIR Curtain sensors) and From Sunset to Sunrise (Next Day) and Status Upstairs Hall Lights is Off Then Run StartLighsUp Then Path If Control TopStairIOLincSensor is Switched On and From Sunset to Sunrise (Next Day) and Status Upstairs Hall Lights is Off Then Run StartLighsDown Then Path From My last post of programs, lets modify the StartLighsUp and StartLighsDown to include the trigger for turning them back off after 30 seconds: Program: StartLightsUp If Then Set i.direction=1 Set StepOne 40% Wait 30 seconds Run StairLightsDissolve Then Path Else -Xathros

Another option might be to upgrade to dimable LED lamps rather than CFL. -Xathros

Might be a good idea NOT to put the PLM in a box as that may limit it's RF range to other Insteon gear. In general, it's best to locate the PLM as close to the main breaker panel as possible. The ISY will want to be a short distance from the PLM as it is connected via a serial interface (not ethernet) Here is a box that might work: http://www.a1components.com/BVModules/ProductTemplates/Bvc5/Product.aspx?productid=a4f858e6-f770-45e1-b49f-45b3af605045&gclid=CPin162yzbYCFcVT4AodYAgAxQ You could cut a Plexi/Lexan cover for it. Plenty of others out there. Search for "Structured Wiring Cabinet". -Xathros

The >1% is basically saying "is not Off" As soon as the ISY requests the Set StepOne 40% that status should trigger the next step. The only delay will be in process/insteon traffic delay and I'm hopeful that it will be <= 1 second. Hard to say without actual testing in the final environment as some of this will likely be effected by Insteon communications quality. -Xathros

Hi Michel- My vote would be to go back to using the MAC finder for the file chooser. While it has a bug, it's easily worked around for the end user. -Xathros

Actually, your original idea may be workable if done like this (Assuming 14 steps): Program: StartLightsUp If Then Set i.direction=1 Set StepOne 40% Else Program: StartLightsDown If Then Set i.direction=0 Set StepFourteen 40% Else Program: StepTwoOn If ( Status StepOne > 1% and 1.Direction=1 ) Or (Status SetpThree > 1% and i.Direction = 0 ) Then Set StepTwo 40% Else Program: StepThreeOn If ( Status StepTwo > 1% and 1.Direction=1 ) Or (Status SetpFour > 1% and i.Direction = 0 ) Then Set StepThree 40% Else ... Program: StepThirteenOn If ( Status StepTwelve > 1% and 1.Direction=1 ) Or (Status SetpFourteen > 1% and i.Direction = 0 ) Then Set StepThirteen 40% Else Program:StepFourteenUp If ( Status StepThirteen > 1% and 1.Direction=1 ) Then Set StepFourteen 40% Else Program:StepOneDown If ( Status StepTwo > 1% and 1.Direction=0 ) Then Set StepOne 40% Else Trigger the Then Clause of StartLightsUp or StartLightsDown to begin the cascade. There should be enough process delay between the actuation of a step and the status checks to get about what you want. For turning off the steps, you might consider starting at the middle step and dissolving from the center in both up/dn directions at the same time. This way only a single direction needed and adds another effect. This method would also allow for changes to the local onlevel for the steps without recoding. Please post a video when you get this up and running. That and a Pic of your bank of InlineLinc's -Xathros