Chris Jahn

For this release the full date is required. We will be adding support for monthly, and annual entries in a follow on release.

There are date ranges and time ranges. Just click the 'Schedule' button, and change the drop down box from 'Time is' to 'From'. Another entry will appear allowing you to have your range go 'To' a specific time or date, or 'For' a specific period of time. To use dates, uncheck the 'Daily' checkbox

Sub-Routine, No problem, we will make 2.4.12 available tomorrow.

The feedback all of you have given has been invaluable, thank you! The fixes we have made are listed here: http://forum.universal-devices.com/viewtopic.php?t=266 We are unaware of any other bugs in the beta, although there are some features that need to be added to a future release (such as better 'Request Failed' message, custom notifications, user defined SMTP).

Good to see you are up and running again. We have not updated the infamous generic 'Request Failed' message, but it is clear that we need to do this at some point in the future.

This is very odd because nothing we added to 2.4.11 should affect device communication. How long were you running 2.4.11? Has anyone else experienced this problem with 2.4.11?

Do NOT do 'Remove Modem' as this will remove PLM links from all your devices, and you can't get them back unless you have an ISY backup file you can use to restore the ISY. 1. Unplug ISY 2. Unplug the old PLM 3. Unplug the cable from the old PLM 4. Plug the cable into the new PLM 5. Plug in the new PLM 6. Plug in ISY 7. Login to the ISY and do a "Restore Modem (PLM)"

Leaving this on should not be a problem, but it does increase the traffic between the box and java client. I typically turn it on only when I'm using it, but it shouldn't really matter.

Are you using the new triggers/schedules that are in beta, or the current triggers and schedules? If you are using the new triggers/schedules then please post your program here (right-click on the program name and 'Copy to Clipboard').

Those are all good ideas, and in fact we do have built-in retries for unsuccesful Insteon commands. It is currently only used for long running commands such as crawl, restore devices, adding devices to scenes etc. At some point in the future we anticipate retries for all Insteon commands issued from ISY, but this requires a little rework.

This is fixed in 2.4.12 --------------------------- For Release 2.4.11 or older Please do not use an 'On Never' schedule entry as this may hang your ISY (i.e. unchecking 'All' for weekdays, and not specifying any weekdays). To recover, you must log into the box using the 'My ISY' link on the Universal Devices home page, then do a 'Restore ISY' with your most recent backup. This has been fixed for the next drop.

That is a good idea but I don't think it will make it into the first release. This is a significant amount of work, and at this point we really just want to stabilize the current functionality so we can officially release it. We'll add it to the list of requirements.

Regarding the issues with programs in 2.4.11 ... If the 'Program Summary' window does not include a 'Run at Reboot' column, then you are using a 2.4.10 or earlier version of the client. In this case, the rest of the settings on that page (eg. Enabled) will not show the correct values. You will need to close your browser, clear your java cache and start it again. The 'Run at Reboot' setting is not being updated in the GUI, although it is being set properly in the box itself. Therefore, until the next drop, hit the 'Refresh' button after changing these values. I'll have a look at the AM/PM problem for the last run/finish time columns.

Thank you all for the kind words, they are very much appreciated!

I wasn't going to make this change, but after playing with it a bit I agree that it would nicer if it retained the combo box values. I'll put the fix in the next drop.

Thanks, I'm glad to hear this is working well for you! You are correct in your assumption, here is a more complete description: 'Run' - 'Then' is run - Program is set 'True' 'Run Else' - 'Else' is run - Program is set 'False' 'Stop' - Stops 'Then' or 'Else' (if one of them is running) - Program true/false setting is not changed The 'If' comes into play again whenever a relevant event occurs. Therefore, while the program is running its possible that it may be stopped, restarted, etc. if the 'If' condition changes. Relevant events: - Button press (button + action match) - X10 message (house/unit/command match) - Status change (device/button matches) - Enter a time range/Time (From/Time is) - leaving a time range (To/For)

I pretty sure it is the same issue; the key here is it may occur when you delete a program. The program only had to be referenced once, even for a brief time, then if it was deleted anytime after that you would see the problem. The good news is the fix will work regardless of what caused it (i.e. referencing a program, deleting a program, etc.).

Your PLM is certainly ok to use with ISY-26, although as you have experienced, X10 may fail once in awhile. I'm not sure if SmartHome has fixed the problem with the PLM in later firmware versions, but as I get information I'll let you know.

Yes, you can telnet over IP, just use port 126 and it is basically the same as connecting throught the serial port.

A couple of you have experienced a bug that causes schedules to start running at 00:00:00 instead of their specified time. This problem will only occur if: 1. You reference a program in another program 2. You delete the referenced program. You will not notice the problem right away; the schedule will run correctly once more, and then the next time after that it will run at 00:00:00. This problem is fixed in the next code drop.

I think this is basicaly what you are trying to accomplish; run something at 8:00AM on weekends and days off, otherwise run at 6:00AM. Days Off is set when the '07.EB.6D.1' button is On. Although you could use 'Control' to make 'Days Off' work, it is much easier using 'Status'. Essentially, the status of the button determines whether or not its a day off or not. Control is more suited to performing an action at the time the control is pressed, rather than retaining a certain on/off state over a period of time. There is a schedule bug (already fixed for the next drop), where the Time continues to be true long after the time has passed. To temporarily fix this, change the 'Time is 8:00am' to 'From 8:00am to 8:00am (same day)' for the 'Day Off' program. Note: For this workaround, you do not need to change simple schedules, only those with a combination of conditions. Program 'Day Off' If Status '07.EB.6D.1' is On And Time is 8:00:00AM Then Run program 'Weekend' Else - No Actions - (To add one, press 'Action') Program 'Weekday': If Status '07.EB.6D.1' is Off And On Mon, Tue, Wed, Thu, Fri Time is 6:00:00AM Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Program 'Weekend': If On Sat, Sun Time is 8:00:00AM Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

I think we should leave this as is, mainly because I'd like it to be clear whether its a folder or a program when people cut and paste to the forum or e-mail messages. Its also a lot easier to delete a couple of lines you don't want, then to add a couple that you do.

I have sent a note to Smarthome, but it sounds like this is a known problem with 4A. I'm not sure if it has been fixed in the current version, but in my own experience with X10, I have only had it fail using 4A.

To log key presses/X10 messages received to the java console, do the folliowing: 1. Telnet to the ISY and login 2. Type 'DBG 1'; this tells the box to send key presses to the GUI 3. Login into the ISY Admin Console, and click the 'Program Summary' Tab 4. Open the Java console 5. Close Telnet session (optional) A line surrounded by square brackets is written to the Java console whenever a button is pressed, an X10 message is received, or a status change occurs. This is useful for determining whether or not the PLM has sent a button press or X10 message to the ISY. To turn it off, 1. Telnet to the box and login 2. Type 'DBG 0', this tells the box to stop sending key presses to the GUI 3. Close the Java console (optional) 4. Close Telnet session (optional)

Theres no "official" 'End Repeat' entry, but there is a way to do it. 'Repeat' repeats everything to the end of the list, or to the next 'Repeat' statement. Therefore, just put 'Repeat 1 time' at the end of your loop. This essentially runs the remaining actions one time (or up to the next Repeat if you have another one).