Chris Jahn

Thanks for the update Rand, 1. At this point there is no way to comment out lines in a program, you'll have delete the lines and add them back. 2. In a future release we will likely add a right-click popup menu to the the summary page, allowing you to do all the actions from that menu, including edit. 3. We maintain the next scheduled runtime for each schedule line in the program. We don't show the program next scheduled runtime because it is non-trivial to find it (a program could have many schedules anded/or'd together). I suppose we could piggyback the next schedule runtime along with the true/false state of sub-expressions, but I think that will have to wait for a future release. Can you elaborate on this one? I'm not I understand what is happening.

I think you looking for the 'Repeat' action. This repeats all actions following it, or up to the next Repeat. You can either repeat a specified number of times, or repeat indefinitely on an interval.

The program status is true when the 'Then' runs, and is false when the 'Else' runs. The behaviour is the same regardless of whether the list of actions in the 'Then' and/or 'Else' is empty or not. It retains its true/false state until either the 'Then' or 'Else' is run again. Adding a true/false column to the table is a good idea, I'll add it to the list.

I haven't looked into yet, but have noticed a couple of posts on the Smarthome forum. I'll contact Smarthome next week, and see what their recommendation is.

Although it is in the plans, the JSDK has not yet been updated with the new trigger interface. You will need this new release for fast on/off because the current release only tests for device status.

Its a problem with the PLM. I had a similar situation here, but it corrected itself after awhile. I tried turning the PLM on/off, and it still didn't work. I then held down my X10 transmitter, flooding the network with X10 messages, and this seemed to "wake up" my PLM and its all working again.

Yes, you can do that in the next release (currently in beta). A button press can send either an On/Off/Fast On/Fast Off/Brighten/Dim. Using the new triggers (now called 'programs'), you can have a switch operate a single light using on/off, but have it operate a whole room using Fast On/Fast Off. You can have it do it only at certain times, or even have it operate differently at different times.

You say the PLM flashes, but what about the ISY? I have noticed at times that although the signal goes out on the line, and the Insteon devices flash (including the PLM), the PLM does not forward that signal to ISY (ISY does not flash in this case).

Do the LEDs on the ISY flash when you send an X10 signal? If they do flash then ISY is getting the X10 message and not processing it properly (By the way, there is no known problem with ISY processing X10 messages). If they don't flash then the PLM is not sending the X10 message to ISY (for any number of reasons).

Random adds from 0 to the amount specified. eg. 'wait 60 seconds (Random)' This will wait from 0 to 60 seconds.

I think this is what you are looking for ... If the 'Outdoor Light' is off between 11pm and sunrise, and the X10 motion sensor is tripped, the lights will come on for 5 minutes. If the light is already on, it does nothing. If From 11:00:00PM To Sunrise (next day) And X10 'B.2 - On (3)' is Received And Status 'Outdoor Light' is Off Then Run program 'Security Lights' Else - No Actions - (To add one, press 'Action') Program 'Security Lights' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Outdoor Light' On Wait 5 minutes Set 'Outdoor Light' Off Else - No Actions - (To add one, press 'Action')

I would like to keep the command number in there, just in case people are debugging a program and need to know the actual number. We only store the A.1.3 on the box itself, so there is no memory problem with longer messages. Based on your ideas, I think the following is probably the best way to go: If X10 'A.2 - On (3)' is Received Or X10 'A.2 - All Lights On (5) ' is Received Then Send X10 'C.4 - On (3)'

If the node is Red then it is being used as a controller for that scene If the node is Blue then it is a responder for the scene.

Good Question! The big change from 2.4.8 is that there are no longer inferred events. This is the primary reason for replacing 'Finally' with 'Else'. The key here is that the true/false status, and whether a program runs (either the Then or the Else) is dependent on a recognized event. For Controls and X10 messages, events must match exactly, meaning: - For Controls, both the switch and value must match - For X10 Messages, the house code/unit code and command must match. The 'is not' allows you to test for the negative (i.e. false if the button is pressed) Therefore the following program will only change state if 'Keypad A' is switched On, or switched Off. If you press 'Fast On' or 'Brighten' on 'Keypad A', the program will not change because these events are not relevant to the program. If Control 'Keypad A' is switched On And Control 'Keypad A' is not switched Off FYI ... As discussed in another thread, if you explicitly run a program, its status becomes true. If you explicitly Run the else its status becomes false. Not all of these changes are in the code drop you are using now; but they will be in the next code drop.

The order of the IF statements does not matter. In your second program, you should be testing the 'Status' of the button. I think part of your confusion are the bugs in the current beta drop (not being able to test status of KPL, program true/false not set consistently). These have been fixed for the next drop. In general though, I would use a folder condition instead. Folder 'Away' - Allows programs in the folder to run if 'Keypad A' is pressed On, stops them from running when it is pressed 'Off' Folder Conditions for 'Away' Add conditions to limit when programs in this folder are allowed to run. If Control 'Keypad A' is switched On And Control 'Keypad A' is not switched Off Then Allow the programs in this folder to run. Then just put your 'Welcome Home' program in your 'Away' folder Program 'Welcome Home' If Time is Sunset Then Set Scene 'Welcome Home Evening' On Else - No Actions - (To add one, press 'Action')

The right-click menu was added to the last beta drop. How many buttons do you see in the lower left corner (with the 'Save Program','Undo Changes' etc. buttons). If you see 6 buttons then you do not have the newest beta drop.

If a program is explicitly run (using 'Run') then its status becomes True, if the Else is explicitly run (using 'Run Else') then its status becomes False. The True/False status of a program also changes when an event occurs or a time arrives that makes one or more of the 'If' conditions true or false (which subsequently causes the 'Then' or 'Else' to run). Scenes do not have status. I thought the way you used a program to essentially assign it a status was a great idea! Basically, you have scene that only the program will call, and you test the true/false of the program to determine if the scene is on or off. So in these sense, the status of a scene is a toggle.

In the next drop, you can log to the java console the key presses/X10 messages received by ISY from the PLM. This should help diagnose problems with your programs vs. problems with the network. On a side note ... Looking for opinions on displaying X10. We currently have the format in Program B, but I prefer Program A. I just wanted to get a couple of opinions before changing it. Program A If ( X10 'A.1.3 - On' is Received Or X10 'A.2.3 - On' is Received Or Control 'Keypad' is switched On ) And X10 A.1.11 - Off is not Received And X10 A.2.11 - Off is not Received And Control 'Keypad' is not switched Fast On Then Send X10 'C.4.3 - On' Set '0A.B9.44.1' On Else Set '0A.B9.44.1' Off Send X10 'C.4.11 - Off' Program B If ( X10 House 'A' Unit '1' Command '3 - On' is Received Or X10 House 'A' Unit '2' Command '3 - On' is Received Or Control 'Keypad' is switched On ) And X10 House 'A' Unit '1' Command '11 - Off' is not Received And X10 House 'A' Unit '2' Command '11 - Off' is not Received And Control 'Keypad' is not switched Fast On Then Send X10 House 'C' Unit '4' Command '3 - On' Set '0A.B9.44.1' On Else Set '0A.B9.44.1' Off Send X10 House 'C' Unit '4' Command '11 - Off'

The wiki entry is a good start, but some of it is outdated since I wrote it at the start of the Beta. When everything has settled down, which hopefully will be by the next drop, I will update the Wiki with a more detailed tutorial. By the way, in some cases the true/false status of a program is not being set correctly. This is fixed in the next beta drop, along with the keypad button status/actions.

There are still a few glitches in the true/false status of a program, but this has been fixed for the next code drop. You can track the status of a scene using a program, but only if that program is the only thing that can turn that scene on or off. I'm not exactly sure what you are trying to accomplish, but hopefully these examples will help (unfortunately you'll have to wait for the next drop to use them). In our next drop, 'Finally' is replaced by 'Else' (by the way, if you right-click on the program in the program tree, you can 'Copy to Clipboard' and paste it into your post) Program 'GoodNitePgm' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'GoodNite' On Else Set Scene 'GoodNite' Off This program will turn scene 'GoodNite' On if B.1.3-On is received and the scene is not already on. If X10 House 'B' Unit '1' Command '3 - On' is Received And Program 'GoodNitePgm' is False Then Run program 'GoodNitePgm' Else - No Actions - (To add one, press 'Action') This program will turn scene 'GoodNite' Off if B.1.11-Off is received or at 11:00PM, and the scene is not already off. If ( X10 House 'B' Unit '1' Command '11 - Off' is Received Or Time is 11:00:00PM ) And Program 'GoodNitePgm' is True Then Run program 'GoodNitePgm' (Else Path) Else - No Actions - (To add one, press 'Action')

You can use a Folder condition and put the vacation programs in that folder. Whenever the 'Keypad A' button is switched On (your vacation button), the 'Vacation' folder will allow programs within it to run up until 6:00AM the next day. NOTE: The 'is not' part of 'Vacation On' may not work correctly for the current 2.4.9 beta. It will work for the next beta drop. Folder 'Vacation' (put your vacation programs in here): Folder Conditions for 'Vacation' Add conditions to limit when programs in this folder are allowed to run. If Program 'Vacation On' is True And From Last Run Time for 'Vacation On' To 6:00:00AM (next day) Then Allow the programs in this folder to run. Program 'Vacation On' -- do NOT put this program in Folder 'Vacation' If Control 'Keypad A' is switched On and Control 'Keypad A' is not switched Off Then - No Actions - (To add one, press 'Action') Finally - No Actions - (To add one, press 'Action')

Thanks Mark, I'll be sure its added for the next drop.

This was fixed for 2.4.9, but I suppose we may have missed some relay devices. This should be working for togglelinc, switchlinc, and keypadlinc relay devices. Can you please post the relay devices you have where 'Fast On'/'Fast Off' etc. is not being shown as part of a 'Control' condition. I'll make sure the 'Fast On'/'Fast Off' etc. that is missing for the scenes is added for the next drop. I'm not sure what we can do right away to get all 256 levels available in the programs, but its on the requirements list.

Have you tried again since the 2.4.9 drop? Back in 2.4.8 the X10 messages had the same problem as non-toggle buttons, but this has been fixed in 2.4.9.

The 'Finally' clause is run when the 'If' is no longer true. This description pertains to Controls in conditions as well (eg. Fast On/Fast Off etc.) In this case, you received an X10 L.7.3 message, and thus the light goes on. It is not possible to make this 'If' false, therefore the 'Finally' won't run. If Receive X10 House Code 'L' Unit Code '7' Command '3 - On' Then Set 'Office - Test LL' On Finally Set 'Office - Test LL' Off There are two solutions First Solution The simplest is to just add another program and not use 'Finally' Program1: If Receive X10 House Code 'L' Unit Code '7' Command '3 - On' Then Set 'Office - Test LL' On Finally - No Actions - (To add one, press 'Action') Program2: If Receive X10 House Code 'L' Unit Code '7' Command '11 - Off' Then Set 'Office - Test LL' Off Finally - No Actions - (To add one, press 'Action') Second Solution Include the 'Off' button in the 'If', thus allowing the 'If' condition to change: If ( Receive X10 House Code 'L' Unit Code '7' Command '3 - On' Or Receive X10 House Code 'L' Unit Code '7' Command '11 - Off' ) And Receive X10 House Code 'L' Unit Code '7' Command '3 - On' Then Set 'Office - Test LL' On Finally Set 'Office - Test LL' Off Summary The thing to notice in the second one is that the 'If' condition is only dependent on L.7.11 (off) and L.7.3 (on). Therefore this program will only turn the light on/off if an On or Off is received; bright/dim/status request/etc. have no effect because they are not part of the 'If' condition. One difference between the first and second solution is if the 'Then' action is long running. The second solution handles it properly, but the first does not. In this case, to make the first solution equal to the second, you would have to add a 'Stop Program' as in this modified example: Program1: If Receive X10 House Code 'L' Unit Code '7' Command '3 - On' Then Repeat Every 1 minute Set 'Office - Test LL' On Wait 30 seconds Set 'Office - Test LL' Off Finally Set 'Office - Test LL' Off Program2: If Receive X10 House Code 'L' Unit Code '7' Command '11 - Off' Then Stop Program 'Program1' Finally - No Actions - (To add one, press 'Action') Another difference is that in the Second solution, the light will only Turn Off if that program turned it on. In the First solution, it will turn the light off whenever it receives an 'Off' command, regardless of how the light was originally turned on. Of course having just written out this explanation, this really does stoke the 'Else' vs 'Finally' debate. I guess thats one of the reasons we have a Beta for something like this.