Mark Sanctuary

I think all programs in the middle of running finish up first.

At this point it is only done by separate programs. You build your lowest IF program then add it to the next bigger IF program. I will try to build an example and paste it here, but we are getting ready to go to dinner soon, for my younger guy has just turned two, so off to the Spaghetti Factory we go.

No way to do the date without a year yet. There was metion to add it at a later date. I would like to know the status on this too, because I have yearly things I want to schedule without having to update them again and again.

Perfect! That would give full test capabilities of all three parts of a program and the full follow thru to end of execution.

I think there is a chance of buzz or hum but it does control them from what I understand. I have not tried a Insteon dimmer yet on a fan but going to soon. Can a switchlinc dimmer control (ramp) a ceiling fan? That is a hefty motor load for an electronic dimmer.

I think it's been there a while because I remember discussing the order of the database for the keypadlincs back months ago in the forum. It may show in one of the release notes on the ISY-26 Insteon section.

"Frist level program (runs)" --> "Second level program (evaluates IF and runs)" ... So your idea is when its run manually you want it to function correctly from your point all the way to the end of execution. Seems good to me.

Chris, dude that is a cool workaround...so it does exist. Sweet, Thanks!

Good attempt as a workaround but, as you said I think that when variables come in a release or two this will not be a needed.

The crazy thing is I have ~30 Insteon devices, two Accesspoints, and no filters, and I am in a old house that has some new grounded romex and the rest is the two wire tar paper wrapped stuff. Not the best circumstances, but I am able to get it all working great. Most of the quirkiness I have found has been me writing the programs wrong or the darn keypadlinc programming shortcomings, but that is eventually surpassable too. I also tried all that stuff Smarthome tried to make and call a controller with their PLC. Now that stuff was most unreliable that is for sure. If I was the reaction forgive me. Please hang in there buddy, it will come together.

When it’s dialed in I have to disagree. It works as good as if it was hardwired. In no way was my X10 setup close to my Insteon setup.

Oh guys this stuff is getting good. Please continue I can use the final result in the Wiki for the “Glossary†and “Creating a Scene†sections.

Yes I think this is correct because it just runs the "then" part of the program without evaluating the "if". There is also in the pulldown a "run else" choice to run the "else" part of the program. These two options give you the ability to just run part of the program, mostly for testing or occasional user use.

So are you saying when you run a sub button scene from the load Keypadlinc the load on that same Keypadlinc does not work correctly? If this is the case the local Keypadlinc load only follows the LED of the sub button. If the LED is on the light will be on and if off the light will be off. And the load will only use the dimmer local level. That means you can only have one dimmer level for any local sub buttons linked to that load. Otherwise I am confused with your description.

Did this ever get resolved? Maybe its gets in a loop because there is only the delay and no device action?

I am going to grab some of this info for the Wiki. ISY-26 Insteon:Working With Keypadlincs

I did a simular program for my Christmas tree. If From 6:00:00AM For 2 hours Or From Sunset To 11:30:00PM (same day) Then Set 'Christmas Tree' On Else Set 'Christmas Tree' Off

I do want to throw this out on the table, the thing about having the LED off when one or more devices in the scene is you would be re-launching the scene when you tap on it again. I have found in most cases the next time someone goes to use the button they want to turn off the lights so I keep the LEDs on even if only one light in that scene is still on. This is especially cool for the "All Lights" scene. There is no right way though, personal preference.

You mean, "Thanks for the info. I'll be eagerly waiting for 2.7." 2.6 is already out, you will have to wait until 2.7 for AutoUpdate.

I also added it to the Wiki in the Telnet To Your ISY how to.

Sweet another Wiki editor...I was starting to get lonely over there. Great job Mike!

This looks good. Should be solid. I have had an All Off button with similar programming like this for quite a while now and it always works great.

Also I have been working to add this entry in the Wiki. Create a Scene

Not sure if this helps, but there is this question/answer in the FAQ... What is a ISY scene? Scenes are simply a group of devices. A scene is equal to a group in Insteon vernacular. Also a scene is as small as two devices linked together and the more links you add the bigger the scene gets. I think there is a desire to think that just linking two devices is just a link and this is correct but it is still a scene. So if you want to create a link between two devices you will have to create a scene to do it.

You can't add the remote link that way. You have to use the "Link Management --> Link a Remotelinc" to do it. The ISY automatically prompts you when to put it in link mode when you do any programming that affects it. And when your programming any large scenes don't worry if the Remotelinc times out of link mode it gets programmed early on in the busy loop.