Chris Jahn

Hi awzulich, If you are not in batch mode, then the reason you still see the green arrows is that it tried to write the data to those devices but couldn't. Whenever you make any further changes to any device, or whenever you toggle batch mode, it will try to write them again. If you are having problems with the device and don't want ISY to keep trying to write out the changes to it, then you can disable the device until you have resolved the problem with it.

I can't explain the 127.5, we'll have to look into that, but it does explain the program running twice. In your program if either the status of the Bedroom t-stat or Living Room t-stat changes the program will run. - The program ran the Then the first time when the living room temperature changed to 127.5. - The program ran the Then the second time because the bedroom temperature changed (still in the normal range), but the overall condition was still true because the status of the living room was still 127.5 The timestamps in the log are created when the log entry is created and may be off from the actual notification timestamp.

Hi Xathros, Your question makes perfect sense, and you are correct; you simply disable the program you and use Run (If). We've been considering renaming "Is enabled" to "Automatically triggered" to more accurately describe what that flag does.

You're welcome, glad to be of help.

One thing to remember is that you don't have to manually change each one, you can replace all instances of a device in all programs by using the "Find/Replace" function (from the Right-Click menu on the programs page).

You can use multiple programs to do a sequence, where each program tests for the next condition in the sequence. In addition, each program has a condition based on the true/false state of the previous program in the sequence (essentially creating a state machine). There are a couple of ways to set up a time window: 1) Have a program run its Then path when the start condition occurs, have it wait however long the time window is, then have it run the Else path. Folder conditions can use the true/false state of this program as a condition. 2) Use "last run time" in a schedule condition. Folder conditions can use the true/false state of this program as a condition.

You still leave the program in the folder, it is just a means of running a program when the folder becomes true. Once you put that condition in the program, you still only have one place to make adjustments. The simple reason for doing it this way is to give the user the option having programs in the folder run or not when the folder condition becomes true.

You should just need to test whether the Folder is True to have the program run when the Folder becomes True. If Folder 'Hourly 0900 to 1700' is True And From Sunrise To Sunset (same day) Then Set Scene 'Back Light' Off Set Scene 'Front Porch' Off Set Scene 'Living Room Light' On Send Notification to All Else - No Actions - (To add one, press 'Action')

Here's a description on how to this, you use 'Adjust Scene': http://forum.universal-devices.com/view ... 0667#10667

You actually can do example 2., you just add another Repeat action, having it only repeat once. eg. Repeat 3 times action action Repeat 1 time action action

This is not correct; it should have been qualified as saying do not use exact time if the program is set to Run at Startup (we're looking into the bug). In all other cases, using exact time is fine. When you use an exact time, the Then Path will run when that time is reached (the program is set True). Nothing else happens, and thus the program will always remain True. When you use a time range, the Then Path will run when the From time is reached (the program is set True). When the To time is reached the Else Path is run (the program is set False). Note: If you add other conditions such as LampLinc status, etc.. this may affect which path is taken (Then or Else). --- ResIpsa, Unless your program is set to Run at Startup, you do not have to change anything.

You could also do this by having a set of programs that test climate, but are not enabled, and having a master program that does a Run (If) on each of these at a specific time (eg. 11:59 PM). Doing this, you would not need folder conditions. FYI ... Have a look at this post describing folder conditions; basically you can reference the folder in your 'If' conditions to have a program in the folder run when the folder condition becomes true. http://forum.universal-devices.com/view ... 0666#10666

If no event or schedule has occurred in the past 10 minutes, then a time event is sent. This is just a safety net to ensure program conditions are tested at least once every 10 minutes. Although its not actually needed, it does provide an extra layer of protection.

jrabin, I tested your program and a bunch of similiar programs and could not reproduce the problem. There must be something else going on because after taking a closer look at the code, if these programs didn't work then nobodys schedules would be working. Is it possible your program is in a Folder with Folder conditions?

I understand what you are saying, some of these can get tricky. I still think you would find it frustrating not to be able to stop a program during a repeat cycle, but there may be a way to do what you want. Not sure when this would be implemented: When a program runs, it may cause events, such as 'Fan On', 'Fan Off' etc.. This is problematic in your example because once the program is running, you only want it to stop if 'Fan On' or 'Fan Off' were done manually via the KPL, but not if the program itself did a 'Fan On' or 'Fan Off'. One answer to this would be to add an option that tells a program to ignore events that originated from itself, (or possibly any program), meaning that if a 'Fan On' or 'Fan Off' was sent by the program, the 'If' would ignore it. Not sure how this would eventually look in a program, but the following gets the idea across: Options Ignore events sent from This program If Status 'Ceiling Fan' is Off And From 9:00:00PM To 6:00:00AM (next day) Then Repeat Every 30 minutes Set Scene 'Ceiling Fan Scene' On Wait 30 seconds Set Scene 'Ceiling Fan Scene' Off This an Insteon limitation, the only way to turn a KPL button on/off is through a scene.

Ok, now I understand, if the scene is turned on by something else, you want to leave it on and not cycle on/off for 30 seconds. I would also assume that if the fan is on (during the 30 second cycle), that if the KPL button is pressed, you would want the fan to remain on after 30 seconds. The simplest way to solve this is base it on the status of the KPL button, basically when the KPL button A is off it cycles, otherwise it doesn't: Program: Fan Cycle --> Enabled If Status 'KPL Button A' is Off And From 9:00:00PM To 6:00:00AM (next day) Then Repeat Every 30 minutes Set Scene 'Ceiling Fan Scene' On Wait 30 seconds Set Scene 'Ceiling Fan Scene' Off Else Run Program 'Fan Cleanup' (If) Program: Fan Cleanup --> NOT enabled If Status 'KPL Button A' is Off Then Set Scene 'Ceiling Fan Scene' Off Else - No Actions - (To add one, press 'Action') Note: This program is needed to make sure the fan is shut off after the schedule ends, but not shut off if the KPL button is on. Essentially this is the same as saying there is no way to stop a program until the end of the repeat (without using an explicit Stop from html or admin console). This has undesirable effects if someone accidently starts something and wants to turn if off right away (such as away program random lighting, a sprinkler sequence etc.).

Congratulations on your baby girl! The reason your program is not working is that whenever the status of 'CielingFan-Motor' changes, the 'If' condition is evaluated and either the 'Then' or 'Else' is run. Therefore, it goes into a big loop: If -> Then -> scene on -> If -> Else -> scene off -> If -> Then -> scene on ... etc. The question is when do you want this to run? It appears as though it should always be running, and if that is the case I would implement it in this way, making sure to have it 'Run At Startup': If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 30 minutes Set 'Ceiling Fan Scene' On Wait 30 seconds Set 'Ceiling Fan Scene' Off Else - No Actions - (To add one, press 'Action') Now, if you wanted to put it on schedule of some kind, you would do this: If From 9:00:00PM To 6:00:00AM (next day) Then Repeat Every 30 minutes Set 'Ceiling Fan Scene' On Wait 30 seconds Set 'Ceiling Fan Scene' Off Else Set 'Ceiling Fan Scene' Off

Your logic is correct; if it is not working it is because of a bug. I'll try to reproduce the problem here, but in the meantime it looks like Michel posted a workaround for you.

Actually, it depends on what release you are running. In version 2.6, restore devices does the following: - 'Restore Device' now removes links to unknown devices - 'Restore Device' now removes duplicate links - 'Restore Device' now moves keypad led links to front of link database - 'Restore Device' now ensures link to PLM for responder only devices http://forum.universal-devices.com/viewtopic.php?t=266 As an alternative, if you notice an unwanted link that does not show up in the ISY, then do the following to remove it (or recognize it): http://forum.universal-devices.com/viewtopic.php?t=537

Hi Mark, Updates look good.

No, these are used for selecting the type of schedule to use eg. Time is, From/To, From/For. As for operators/values ... The set of operators, and set of comparable values depends on the type of device. For example, for a Dimmable device (eg. LampLinc): Operators: 'is', 'is not', '' Comparable values: 'Off', '1%', '2%' .. '99%', 'On' For example, for a Relay device (eg. ApplicanceLinc): Operators: 'is', 'is not' Comparable values: 'Off', 'On'

Hi Mark, Control XYZ is switched On vs Status XYZ is On I think it may be confusing to put 'is switched' in the wiki because it is not an operator and you don't see it in the input boxes. The operators are 'is', 'is not' etc. The values that may be selected are 'On', 'Off' etc. 'On' shows as 'switched on' when the condition uses 'Control'. Control - When you use 'Control' you are testing for how it was turned on, eg. On, Fast On, Off, Fast Off etc. You see the word 'switched' to emphasize that. - If the action listened for occurs (eg. Fast On) then this condition activates the program (causes program to run either then or else path). Status - When you use 'Status' you are testing for its current brightness level. - If the status changes then this condition activates the program (causes program to run either then or else path).

Hi Marko, This is a bug, basically when you change to/from DST the programs were using the old sunrise/sunset values. This has been fixed in 2.6.7

Hi Sub-Routine, I added an HTML role to the configuration page, which allows you to customize the level of access to programs when going through the HTML interface. This is a stopgap measure until we add support for multiple users with roles.

csetter911, This is quite odd, there is really no reason a program shouldn't be loaded unless the ISY is out of program memory (hence the 'Out of memory' message). With so few programs, it is more likely that one or more of your program files is corrupted. Questions: 1) What type/release are you running (e.g. ISY-26, version 2.6.6) 2) Are you bringing up the admin console by going directly to your ISY, or are you using the link on the www.universal-devices.com website? 3) Do any of these programs use a 'Run Then' action?