Chris Jahn

If the user had subsequently pressed 'Fast On', 'Fast Off', or anything other than 'On' then the 'If' condition would no longer be true. If this was done, say, 7 minutes into waiting the 10 minutes, the 'Then' immediately stops running, and the 'Finally' starts running. If you didn't have an 'Off' in the Finally the light would just stay on. As sfhutchi correctly points out, this is overkill for Insteon switches because the program does everything. The simpler (and preferable) solution is to link the control to the light (using scenes etc. on the main page), and use a simple program like this: If Control is 'On' Then Wait 5 minutes Set Light Off In this case, the switch directly controls the light, and the only thing the program has to do is shut it off after 5 minutes.

You are absolutely right, if the switch itself controls the load either directly or through a scene then this is all you need. In fact this is preferred if you can do it because if the ISY is powered off, the switch itself will still work. The program I posted shows how to use a pure program solution, which is only required if you use the receipt of X10 message (for example) instead of pressing an Insteon button.

Yes, the problem with non-toggle buttons has been fixed and is in the next beta drop. http://forum.universal-devices.com/viewtopic.php?t=266

I understand the frustration with losing your changes. The changes aren't saved immediately because it would slow down the interface, and when you save, it resets the trigger, possibly restarting it (if its a schedule for example). I think the right balance here is to say "Not Saved" in the summary, and have a warning popup appear prior to closing the application (similar to an editor such as NotePad, Word etc.).

Mark, Glad to hear they are working for you now. It sounds like the original problem may have been that you forgot to "Save Changes". That would explain why your triggers didn't run in the first place, and why they weren't there when restarted the "Administrative Console". If the arrow on the program Icon in the tree is green, that means the program has changes that have not been saved.

Go to the 'Program Summary' Tab 1. Be sure the program is enabled. 2. When you press the On button you should see the program in 'Running' mode. There is a bug that is fixed in the next Beta drop for Non-toggle buttons. For now, if the button you are using is non-toggle, then change it to toggle. There is an existing general problem where in some cases ISY is not updated with events from devices not in a group. To be sure it is getting updated, do the following: 1. Add the device to a group 2. Do a 'Restore device' on that device.

This programming is totally independent of device links, and thus will not override them.

'Finally' is similar to 'Else' with one exception: 'Finally' never runs unless the 'Then' had run. This means that the conditions in the 'If' had to become true, and then become false.

Good Idea Mark, This has been a common request ... I'll add it to the list.

Release 2.6 Officially Released. ----------------------------------------------------------------------------------- For Release 2.5 (RC1) Fixes - Fix: Schedule 'Time is' entries run intermittently - Fix: Cannot enable programs - 'Replace Device' now updates all remoteLincs first - 'Replace Device' does not require exact device type/subtype match - '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 - Less aggressive network crawl (now ignores inactive links) - Missing PLM links added when device added to ISY - For Linux, Log can be saved to filesystem - Updated User Guide Features - Detailed progress in Java console for long running commands (Restore Devices, etc.) Known Bugs - None ----------------------------------------------------------------------------------- For 2.4.15 - Fixes - Or (...)/And (...) logic in programs - 'New Insteon Device' now removes old links immediately (as currently done if linked instead) - Sunset/Sunrise now recalculated at DST changeover - Device now working correctly after 'Replace Device' - Move 'True/False' to own column in Program Summary - Widen h/m/s input dropboxes (showed '...' in some browsers) - Proper file cleanup when removing a device from ISY and device communication fails. - Device firmware levels in GUI - Regression: ELK/Notification setting are not saved - Progress bar when saving programs - Sunrise/set "Same Day" now working correctly when the From is a fixed time or lastrun time, and the To is a sunrise/set. Known Bugs - Documentation is still at 2.4 level ----------------------------------------------------------------------------------- For 2.4.13 - Fixes - Overwrite existing links now immediately overwrites links when the device is added - 00 in the middle of Insteon address - Removed notification settings from Configuration tab - 'Repeat 0 times' entry fixed - Program Summary shows True/False state of programs - Various minor bug fixes ----------------------------------------------------------------------------------- For 2.4.12 - Fixes New Triggers/Schedules - 'On Never' schedule entry fixed (no longer hangs the box) - AM/PM in Summary table displays and sorts correctly - Changes to 'Run at Reboot' automatically updated in summary screen ----------------------------------------------------------------------------------- For 2.4.11 - Fixes - Last run times would show 00:00:00 Enhancements - Show [Applied Locally], in Red for local scene controllers - Maintain the state of program GUI - Added "Run at Bootup" to address the power failure issues - Retain combobox values between Status/Control ----------------------------------------------------------------------------------- For 2.4.10 - Fixes New Triggers/Schedules - Newlines preserved in Program Comment field - 'Finally' replaced by 'Else'; semantic difference is 'Else' runs independent of whether 'Then' ran - Fixed program true/false status, and various logic bugs in programs. - Added 'is not received' to X10 conditions - Keypad buttons available in Status conditions and actions - Log key presses/X10 messages received to the java console (turned on/off in the shell) ----------------------------------------------------------------------------------- For 2.4.9 - Here is the list of fixes going into the next beta drop, we'll be updating this as more bugs are found and fixes are made: Fixes Main Application - INSTEON address is now shown on the Device View next to Device Type - Now, the same on level and ramp rate can be applied to all the devices within a scene New Triggers/Schedules - Clicking on 'New Folder', now uses 'New Folder' as default name instead of 'New Program'. - 'My Lighting' now included in drop down lists - Fix for non-toggle buttons. An event occurs whenever a button is pressed (i.e. not just when the current value of the button changes) - Configuration fix for Relay devices; now allows Fast On/Off etc. - Node combo boxes widened to accomodate long names - Schedule migration no longer turns lights Off instead of On - Copy readable contents of program to clipboard - Copy program - Program tree has popup menu - Fix for box hanging when deleting all contents of a folder and the folder itself - Fix for intermittent save/delete program errors - Fix for null references to programs and nodes within a program Regression - Fixed not being able to change the userid/password - Removing devices from a scene, left residue and in some cases the device would still respond to commands from the scene it previously belonged to

Here is an example of how to automatically turn off a Closet light after 10 minutes. Incomplete: If Control 'Closet' is On Then Set 'Closet Light' On Wait 10 minutes Set 'Closet Light' Off In this scenario, when you press the 'Closet' button to 'On' the trigger starts running the 'Then' actions. When the 'If' condition is no longer true, the 'Then' actions stop running (even if not complete), and the 'Finally' actions start running. So in this case, if after 5 minutes you hit the 'Closet' button 'Off', the 'Then' stops running immediately and the Closet light will not go off at all (even after 10 minutes). The way to fix this is to add a 'Finally' action. When you hit 'Off', the 'Then' stops running, and the 'Finally' starts running, which turns off the light. Correct program: If Control 'Closet' is On Then Set 'Closet Light' On Wait 10 minutes Set 'Closet Light' Off Finally Set 'Closet Light' Off You essentially have 2 ways for the light to turn off: 1) 10 minutes after its turned on 2) When you turn the control off Whenever you turn the 'Closet' button 'On', it restarts the trigger thus if you don't hit the button again, it will wait 10 minutes from that point to turn off the light. Having said that, there is a bug that will be fixed for the next upgrade. If your button is non-Toggle (i.e. always sends 'On' when you press it), it assumes that nothing has changed and thus will not turn on the light. This obviously severely inhibits non-Toggle buttons, but it will be fixed during this beta period.

Hi George, I'm not sure what would have caused this; could you send me the backup you made prior to upgrading to the new version so I can try to recreate the problem here.

Thanks Rand! You are right, 'My Lighting' should be there but isn't. This caused the 'null' in that schedule. I'll put that on the fix list. I agree the new features look great! I see this as well. This used to be the Query My Lights at 3 AM. I cannot find My Lights in the list. No backup errors here. Rand

Yes, I'd like to get a little more feedback on this one. Here's the reasoning for where the "Update" button is now ... The "Remove Line", "move line up", and "move line down" buttons do not use any information from the 'Add To Program' area below. The "Update" button, just like the "Add to 'If'"/"Add to 'Then'"/"Add to 'Finally'" buttons, does use all the information in the 'Add To Program' area, thus they are grouped together there. [/b]

Thanks Steve, You are right, ... one more to add to the list.

Thanks George! A lot of effort went into this and I'm glad to see the initial response is positive. You can delete, move, rename, or edit any of the programs in "My Old Schedules" or "My Old Triggers"; they are just like regular programs. You can even delete the folders if you'd like. Did you get the backup errors when backing up with new code on the box, or was this when you did backup prior to upgrading the box?

Adding the Right-Clicking on Program Folders and Programs, and an option to remove an entire folder and its contents are good ideas, we'll add them to the list. As for the the width of the 'Set' box, we can increase that as well (possibly make it variable on the length of the largest entry). Program Summary The 'Last Run Time' is set the moment the program starts, so in this case it looks like the program did not run. I'd have to see the program to see why it isn't running. Random Random is between zero and the number you selected. Therefore if you want to go from 15 to 25 minutes, you would create a non-random wait of 15 minutes, followed by a random wait of 10 minutes.

Mark, GPG, We have just been heads down putting the finishing touches and last minute enhancements into the beta for the new triggers. Its going well, and we should have it out to you soon.

Yes, you will be able to use received X10 commands as criteria for running a trigger. You will also be able to send X10 commands out as well. You can do different actions based on a variety of criteria, including the last run time of a trigger for a specified duration. For example, you could have a trigger that runs if an 'A 1 On' X10 message is received, and have another trigger that runs if the first trigger has run in the past 5 seconds and another 'A 1 On' X10 message is received.

I just realized one other thing. If at least one device is not restored you will get the beautifully cryptic "Request Failed" message. In this case it means just that, it could not update every device, but did update all the ones it could find. I guess the feature request would be to display a more informative message, indicating which devices were not restored.

Hi Sub-Routine, This feature is already there, so it must a bug for your scenario. Normally, while Restore Devices runs it will skip over devices it cannot find/update. Can you provide the exact details? I'd like to try to recreate the problem you are having.

marksanctuary, Thanks for starting this FAQ, it should prove quite useful. Here's a few comments ... >Is there a way to find all my Insteon devices? >On an existing Insteon setup do I need to start over when I first get my ISY? The "Add devices found in links" option does crawl (spider) the network. We add all the devices we find in those links, but do not add the actual links and groups in ISY. Therefore if you link a light that is linked to a keypad, that is linked to another light etc. then all those devices will be added to ISY. > I already have the ISY programmed but some of my devices have lost their way; how can I fix them? "Restore Devices" loops through all the devices that are in ISY and reprograms them with the settings in ISY. This can take a long time, but does ensure ISY and the Insteon devices on the network match. If you select a device in ISY and right click, you can "Restore Device". This will reprogram that individual device instead of reprogramming all of the devices on the network. "Restore Devices"/"Restore Device" comes in handy if you are: 1) Restoring the devices on the network after Restoring an ISY Backup 2) Recovering from curious friends who have accidently manually reset or changed settings/links to some of the devices on your network.