Michel Kohanim

mohansen, Please make sure you do not have any programs with "Run at Reboot" ... if you do, that might explain why all your lights come on when ISY is rebooted. With kind regards, Michel

Hello blartyo, Yes: anything that has to do with the underlying protocol (INSTEON) and common functionality (NTP/SMTP/SSL) will be released on all platforms (26 and 99). Otherwise, they will have their own schedules. With kind regards, Michel

Charlie, We are hoping to have this supported in our 2.7/8 release which would mean as soon as 45 days or as late as 120 days. With kind regards, Michel

Jim, Now I totally understand what you are saying ... apologies for the misunderstanding. I am thinking that it would be great if someone decided to spend a few hours to come up with Holidays programs (say for the next 5 years) which everyone can reuse and therefore also simplify what you are trying to accomplish. In any case, you are on the right path. Please do keep us posted with your progress. With kind regards, Michel

AnthemAVM, You do need the 126 at the end so: telnet 192.168.1.102 126 With kind regards, Michel MikeB, I got that, but when I put it in the command it comes back with a message Could not open connection with host, on port 23: Connection Failed. Sorry to ask so many questions.

Jim, Folder conditions just limit what programs are run within the folder and, based on what I gather, I don't think you want to use Folder Conditions. You are simply looking for a way to reuse the status of a program to constrain another program. So, I think, you would want to create standalone programs to be used as conditions in any other programs. Right? With kind regards, Michel And then I use it for folder control: Same thing for the 'Weekend' programs folder. What I'm not crazy about is that if anything happens between the 'from' and 'to' and either flag goes low, there is nothing to reset it until its initial start time again. I guess I could do some code: if both flags are low (actually they both will be low during the changeover), that is not a legitimate condition, I could do something with that. I'm also having a little trouble deciding how to do the manual override, which is the whole point of this. If a holiday occurs on a weekday, I want to enable the 'weekend' folder and disable the 'weekday' folder, ie, run the weekend schedule on the holiday. I'm sure nobody wants to get sucked into this one. I'm even wondering if it is worth the trouble!

d_l, Don't worry! I am almost as paranoid as you are: though we cannot really do much about denial of service attacks but in our next release will incorporate SSL/HTTPS to make the in/out bound more secure. At the moment, the only problem is the high cost of SSL certificates. With kind regards, Michel Thanks Michel. If I'm accessing the ISY without the "/0/x" , that must mean my dual WAN router's local loopback is working which is something that I wasn't certain about and haven't found a way to disable that function. Actually once I discovered this, I became a little concerned about anyone on the internet being able to partially access my ISY if the "/0/x" was not required. My thinking was that anyone could stumble across sending an http probe to my IP and its unique port without the "/0/x" and be able to see my ISY's main page contents in the background behind the login window. Although they could not access the ISY without passing the login, the positive response from the ISY might encourage intensive login cracking attempts. The "/0/x" in the address adds an extra little security twist. Lest anyone think I'm paranoid, I review my router logs regularly and do see what I think are hacking attempts and not simplistic trojan attacks on occasion.

Hi Mike, What's the difference between the two codes? In both cases, this should work fine. With kind regards, Michel

Jim, Hi, my only comment is that you do need the From and To in your first example. Have you given that a try? With kind regards, Michel This folder condition enables a program every 4 am that allows a motion sensor to turn on the den lights when motion is detected, but only the first one after 4 am. It won't turn on the lights every time during the day when it detects motion. When 4 am rolls around the next day, it will enable it again. This has worked 100% perfectly since I put it in. Even my wife likes it . The X10 is there just as a manual trigger for testing, etc. It seems like the schedule I have in the original post is pretty similar. Any comments anyone? Thanks.

d_l, /0/p is no longer needed ... we removed it a long time ago but we have left it there for backward compatibility. If you are accessing ISY remotely, you do need the /0/x otherwise you will get socket errors as Admin console will try to open a port to a local address as advertised by ISY. With kind regards, Michel

Hello all, Thanks so very much for your most invaluable feedback. We have a requirement for "Proper support of X10" which we'll be working on shortly. We'll surely take all this input into consideration while designing/implementing. This said, however, since we have not yet designed the solution we cannot really ascertain to what degree the solution will look like JAJ's Artistic Creation! With kind regards, Michel Thanks for the kind comments, one and all! I really hope Michel and/or Chris will chime in and let us know how much they would like to implement!

MikeB, Yes, we have a switching power supply - simply use the power supply that came with your 26 or send a request to sales@universal-devices.com for a new one. With kind regards, Michel

aLf et Al, We found a bug: http://forum.universal-devices.com/view ... =4697#4697 . With respect to your question, I really do not think it would be necessary: the most vulnerable piece is the PLM and not ISY or the router. With kind regards, Michel

Hello, For ISY 26/99 versions equal to and below 2.6/1.0 respectively, if you have a power failure and if your ISY boots up faster than your router: ISY tries to get an IP address 3 times and then it quits trying and thus leaves ISY IP-Less and therefore not discoverable and communicable. This was done for cases where the user wants to use ISY without a network connection. In 95% of the routers, 3 times is enough time to provide an IP address and everything succeeds. For others, ISY will no longer be on the network. This has been fixed for the next release. In the meantime, and as a work-around, please try using a static IP address for your ISY. Thanks and with kind regards, Michel

jdva, Excellent idea .... yes! With kind regards, Michel

Mark, Thanks so very much for the clarifications. If you see 0.0.0.0 on the console then it means any of the following: 1. ISY was on DHCP (which it is not) and it couldn't get an IP from the router 2. ISY is defective ... the network interface is damaged Although you've already stated that your neighbor cannot access ISY, I have no choice but to ask: if your neighbor can replace ISY, you can send me your backup file, I can upload it into a new ISY, assign your static IP address, and send it to your neighbor. All he has to do is to replace the cables on ISY. Please do let me know if this is a viable option. With kind regards, Michel With kind regards,

Mark, They are already Tab Delimited. With kind regards, Michel

Mark, We do not use XML in the logs. With kind regards,

DEGoodrich, This device is not supported! Brian H, please do let us know what you find. In most cases, for devices that are unsupported we simply use on/off metaphor. With kind regards, Michel

jgraziano, I don't think this is a CL issue simply because out of the two devices in your scene one works and one doesn't. I believe it has to do with the device itself not getting the group command (or not responding to it). My suggestions: 1. Check your logs for -2 and see if you have any for that device (device comm error) 2. If you do, try an airgap/reboot on the device in question and follow it up with 4 or 5 queries 3. If 1 does not fix the problem, try Restore Device Please do let me know what you find. With kind regards, Michel

d_l, I am so very sorry for the problems and issues. If you do not have Excel (and are running Windows), currently the only way to get to your logs is as jgraziano suggested. On MAC/Linux, you are given the log file as is. We do have a requirement to provide this function without Excel on Windows so, please do be kind enough to use jgraziano's suggestion as a workaround. With kind regards,

Hello maui4marko, I wished you had taken our advice (about 2 months ago) and upgraded your ISY to 2.6 which has a lot of work arounds for PLM spikes due to power outages (and especially those lasting more than 10 seconds). If we can get your system up and running again, the first thing we should do is the upgrade to 2.6. Secondly, please note that when there's a power outage your cable/dsl router is also impacted therefore it's always very important to make your ISY use static IP addresses and thus when it comes back on, it doesn't have to go and reconfigure your router. If your subsequent dim/bright do not work (you keep getting the system busy dialog) then, in all likelihood, your PLM is gone. To troubleshoot, unfortunately so, we have to have your neighbor power on/off and let us know the status of the RX/TX/MEM/ERR lights on ISY. If RX is blinking every 4 seconds, rest assured that your PLM is probably defective. Please do keep my posted. With kind regards, Michel

maui4marko, Thanks so very much for the update and so very sorry for the inconvenience. I have captured it as a bug and we shall take care of it as soon as possible. With kind regards, Michel

Hello gwarthur, Please find my comments below. With kind regards, Michel Yes! Mostly because otherwise you are going to have links in devices that ISY does not know anything about and therefore, upon programming, is going to overwrite links and thus cause unexplained behavior: lights that used to turn on no longer turn on or other lights that never turned on now turn on. With kind regards, Michel

evarsanyi, Now I understand! We shall be working on Trigger 2.0 and some X10 enhancements in the next releases! Thanks so very much, With kind regards, Michel