Mark Sanctuary

I did a “Factory Reset†on the keypadlinc's and the sliders are still snapping back to 100% in the scenes that are using the keypadlinc “All Off†workaround where you drop in the "load" and a "non-load" into the same scene. I have not done a "Factory Reset" on the ISY before and have had lots of fiddling and testing since I first bought my ISY which started at firmware update 1.7 I think. I could have done something to corrupt my database (restoring an older ISY backup in a newer firmware version) in the past. I think I might just do a "Factory Reset" on my ISY and start from scratch, what do you think?

I am going to try doing a "Factory Reset" and "Restore Device" on the keypadlinc's I have to see if I can clear up the issues I am seeing.

That does not work for me putting the main dimmer light in the same scene. It always takes on the keypadlinc default level. And in the ISY the load's slider in the scene always pops back to 100% when I try to change it in the scene. So should having the load in the scene let me set the level in the scene? If so we got a bug then.

The Status bar and programs use am/pm standard time and the program summary run time stamps use military time.

----- The new way ----- This version is much more reliable and has much less wait time. This version came about from much discussion below and I brought it up to the top of the post. The ISY is using this program as a pass-through which it is making the (A) and ( buttons virtual controllers for the scene. The reason to do this is the ISY will set all the lights according to its local levels thus avoiding the issue that the keypadlinc can only have one level for all the buttons on board. Lastly I have it check for both Off and On switched states so if for some reason the LED ends up off it will still work and return the LED back to an On state. If Control 'Family Main (A) Evening Time' is switched On Or Control 'Family Main (A) Evening Time' is switched Off Then Set Scene 'Family Evening Time Scene' On If Control 'Family Main ( Movie Time' is switched On Or Control 'Family Main ( Movie Time' is switched Off Then Set Scene 'Family Movie Time Scene' On ----- The old way ----- The keypadlinc has that darn quark that it can not store a different level for each button that has its LED turned on. So here is an example of some simple workaround programs to fix it. If Control 'Family Main (A)' is On Then Wait 5 seconds Set 'Family Main' 60% If Control 'Family Main (B)' is On Then Wait 5 seconds Set 'Family Main' 20% This is working in parallel with the scenes that are also associated with these keypad buttons. Buttons © and (D) are both used for different off scenes so they don't need programs they just need the LED off on each button. There is a small delay for the light level to change but it at least works. The 5 second wait is needed to let the linked scene complete first before turning on the load.

Here batter, batter, batter ... commme onnn Friday beta drop ...

When trying to update a clause the node selected and all its arguments reset. Here is the steps to the bug I am seeing... [*:3k9a13if]Select an existing program that you want to change [*:3k9a13if]Select a 'If' clause that you want to update [*:3k9a13if]Mine says 'Control' and I change it to 'Status' After doing this the node combo box and all the argument combo boxes jump to the top entries and does not stay on the already existing node and arguments. If it could stay on the existing node this would be very helpful. I understand that the lists sizes change from selection to selection. So if it could capture the selected node and arguments, and try to keep them selected unless they are not there on the new lists, otherwise they could jump to the top entry in the combo boxes. If you go to say 'X10' that does not have it and you decide to come back to 'Status' would be nice if it still had the same previous info from before. Why this suggestion; because when your trying to just adjust one item then hit the Update button you don't notice that your node and all its arguments has just changed too. And when you’re updating a program condition you more than likely will not be changing the node and all its arguments.

I could be a choice between using "else" or "finally" but not both at the same time.

I noticed that last night when I was experimenting. I will try status instead. Thanks!

That works great. These little programs really just need a lightest touch approach.

Good idea, good question. I will try the program without the turning on part. I just need the timer to turn it off after the time is run out. Thanks Guys.

Well I found a workaround but I am wondering if you can check in the background for the parallel scene vs program; if there is already the same controller switch in the program, and the same scene as the program, then you could add a small delay to that program. If Control 'Guest Bath Main' is On Then Wait 1 second Set 'Guest Bath Main' On Wait 1 hour Set 'Guest Bath Main' Off

Yes there was already links to that scene on the switch. I can see them work right away. [*:1cmkiu81]I tap the light on, the scene comes on [*:1cmkiu81]I split second later tap it off, the scene goes off [*:1cmkiu81]Then about a half second later the program turns it back on. [*:1cmkiu81]And now that I added a finally it flashes back off. So what I get is an echo of the switch. I guess I could run without the switch links and just the ISY program but then the scene would not function if the ISY was out of the loop. I think it might be that the ISY is trying to execute the program ASAP so there is no time to get feedback back before the split second off tap. How big of a hit is it to wait for the second tap response?

Here is the code and I know your going to say use a Finally but this causes the light to blink on then back off after the split second on-off usage. If Control 'Guest Bath Main' is On Then Set 'Guest Bath Main' On Wait 1 hour Set 'Guest Bath Main' Off

I have noticed in the Admin Console that the code is not evenly indented it is also noticeable in the code pasted in other posts. Also the more than one spaces in code is sometimes a bit wierd too. Could it be tweaked to use 4 or 5 spaces per nesting and nix the extra spaces? First example: If Status AC is Off And ( Time is 5:00PM Or Time is 4:00PM And Temp > 90 ) Then Set AC on Another example: If On Mon, Tue, Wed, Thu, Fri From 9:00:00AM To 5:30:00PM (same day) Or On Sat From 10:00:00AM To 2:00:00PM (same day) Then - No Actions - (To add one, press 'Action') Finally - No Actions - (To add one, press 'Action') One more example: If-( | Receive X10 House Code 'A' Unit Code '2' Command '3 - on' | Or-( | | Status '04.BF.8D.1' is On | | And From Sunset | | For 3 hours | | And( | | | -( | | | | Program 'Office Hours' is True | | | | And Program 'Office Hours' is False | | | -) | | | Or Control '07.EB.6D.1' is Fast On | | | Or From Sunset | | | For 4 hours | | -) | -) -) If ( Receive X10 House Code 'A' Unit Code '2' Command '3 - on' Or ( Status '04.BF.8D.1' is On And From Sunset For 3 hours And( ( Program 'Office Hours' is True And Program 'Office Hours' is False ) Or Control '07.EB.6D.1' is Fast On Or From Sunset For 4 hours ) ) )

If I turn on a switch then I change my mind in a split second and turn it back off before a program starts the program turns them back on. I found it on my bathroom timer program.

When you do a change then press Save Changes all the folders close down. Then you have to open them back up to where they where open before.

I forgot this one was redundant thanks for replying anyways.

Oooh I see; its a scale check you have that limits movement when your widgets on the left and right are small. Thanks for adding it.

Thanks I understand. The global control is helpful but individual control is needed too.

Good news that the upgrade went fine. The Off instead of On in the old schedules is fixed in next beta drop. The null also has been fixed in the next beta drop. Not to bad of an idea but it may expand the gui widgets apart a lot. Copy has been added to the upcoming beta drop. Bug "No Fast On/Fast Off relay devices" and "Dimmer Fast On/Fast Off tripple click" has been fixed in the next beta drop. Showing device ID when looking at a single device has been added to the beta drop too.

Ooh good one to note. Thanks

The execute test run would be helpful when creating and testing a program. The Reset to Idle is a nice option to stop a program when needed.

I also would like to request the else statement. It is much cleaner code than adding more nested if statements to get an else result.

One other note; if I do a "triple-click super fast off" then it does work. I think the first click of the triple-click is actually setting the dimmer off (even though it is already off) and then it does a fast off with the last two clicks of the triple-click. What do you think is up?