Jump to content
Alexa Skills down - Alexa Side (NOT UD ISSUE) - As of 5pm Eastern (7/10) ×
Alexa Skills down - Alexa Side (NOT UD ISSUE) - As of 5pm Eastern (7/10)

Michel Kohanim

Administrators
  • Posts

    26775
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. d_l, The programs are automatically evaluated and, if their conditions are true, are run. You can see their status on the summary page including their state. So, Running the 'If' makes it a little confusing. Does this mean: reevaluate the conditions? With kind regards, Michel Actually this was an idea about being able to make a program evaluate the "If" conditions when run from the Summary page or when run as a nested program. See: http://forum.universal-devices.com/view ... highlight=
  2. Frank, Yes, all ISYs come with that program preloaded. It's up to you not to re-add it. The worst case scenario is: if you have programs that depend on the correct status of the devices and if those devices do not have the correct status, then your programs will not run as desired. With kind regards, Michel Hello Michel: Did all ISY-26s ship with this program? I don't remember it ever being on my system. Of course, long ago when I first got the ISY, I was having many comm problems. I think I that at that time I performed a factory reset, and thereby may have removed it. But then again, life has been just fine without the "3 am" program. Why add it back and rock the boat? Most PLM-related Comm Errors occur "sporadically" (at least for me), I'd probably rather not run the program, the more that I think about it. For instance, if I do an entire network query, it's not uncommon to have 1 or 2 failures. But if I requery those devices that had a failure, they're usually communicating just fine. I attribute these the the general weakness of the PLMs Insteon communication. Since you've written the code for the ISY such that it "tells" you the failed devices the next time that you log on, why should I want to keep seeing failures that don't amount to anything every time I log on due to the "3 am" query. This brings up another topic that is related, so I'm going to start a new thread for it. Best wishes,
  3. Mark, What does Run If mean? With kind regards, Michel
  4. edfinley, Yes, this feature shall be provided as a part of our 2.7/8 release in conjunction with SSL. With kind regards, Michel
  5. Hi Rowland, We are going to provide this feature for KPLs 1.6 and above in the next release. With kind regards, Michel
  6. blartyo, Yes, you are 100% correct: - Run means "Run Then" regardless of the condition - Run at Reboot means "Run Then" regardless of the condition With kind regards, Michel
  7. Hello mohansen, Factory reset removes all the schedules. You might want to add back If Time is 3:00 A.M. Then Set My Lighting Query This code makes sure your ISY is in synch with your devices. Adding devices back one at a time and choosing the first option clears each device's database (unless there's a communication error) and, as such, you do not have to do a factory reset on your devices. What do you mean by " ... adding back my ELK configuration"? ISY should not be rebooted at any time and thus I consider this a bug. I'd appreciate as much input as possible. With kind regards, Michel
  8. blartyo, Running a program from the Program Summary tab runs the program regardless of the condition. This is mostly used to test the outcome of your program. You can also choose "Run Else" which runs the Else path. With kind regards, Michel
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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.
  14. 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!
  15. 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.
  16. Hi Mike, What's the difference between the two codes? In both cases, this should work fine. With kind regards, Michel
  17. 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.
  18. 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
  19. 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!
  20. 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
  21. 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
  22. 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
  23. jdva, Excellent idea .... yes! With kind regards, Michel
  24. 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,
  25. Mark, They are already Tab Delimited. With kind regards, Michel
×
×
  • Create New...