Michel Kohanim

FLBoy and Brian H, Thanks so very much for your input. This has now been added as bug and shall be tracked as such. With kind regards, Michel

Hi Jim, We are working on it as an optional module. As you can imagine, things get a little more complicated as soon as the URLs can be "POST"ed and PUT in addition to GET. But, we are working on it. With kind regards, Michel

Hi Gary, We are now trying to figure out how to support EZIO again as everything seems to be broken. Once we have this fixed, We will have the capabilities which will allow you to set the timers in EZIO. With kind regards, Michel

Hi Michaelv, It's quite simple: Go to Link Management -> Add a Button to IRLinc and follow the instructions on the screen. It's always best if you start fresh (Remove existing links). With kind regards, Michel

Hi DEGoodrich, Due to limited resources, we are still awaiting someone to develop an iPhone app for us! With kind regards, Michel

Hi to_lighter, All you need is the Wait (every 5 minutes) in the Action part of your program. Your condition could be anything you wish: i.e. from 5 AM to 5 PM. etc. I am sure you do not need dummy variable just to run a program every 5 minutes. With kind regards, Michel

upstatemike, Come to think of it, you have a very large installation. The last time we checked, you had about 900 links in your PLM. One way to test is: 1. Go to Tools->Diagnostics->Show Device Link Table 2. Choose your SWL 3. Click on Start and then click Ok on the subsequent dialog 4. Look for E2 01 N.N.N 00 00 1 where N.N.N is your PLM id (Tools->Diagnostics->PLM Info/Status) If you do NOT find this record, the we either have a bug in ISY or ISY was not able to write this record into your PLM. If you do have this record, then the problem is either the PLM or the switch itself (we have ruled out noise, right). To see if it's not the PLM, please 1. Go to Tools->Show PLMs Link Table, click on Start 2. Look for A2 01 M.M.M WW KK 1 where M.M.M is your SWL's address and WW and KK are immaterial 3. Click on the Count button to see how many records you have If you do not find this record, then in all likelihood you have a defective PLM or one which overwrites others. With kind regards, Michel

GDN, Our pleasure. Please do keep us posted. With kind regards, Michel

Hello aLf, We'll do all we can to support both: in computer science/programming, there's nothing you cannot do; it's just how ugly the solution will look (it's going to be a little ugly inside our code). With kind regards, Michel

Hello me23, d_l already provided you with great info on question #2. As far as question #1, ISY is not privy to anything you do manually. As such, would you be kind enough to redo the same thing within ISY? With kind regards, Michel

Hi upstatemike, Unfortunately, I do not have that information. With kind regards, Michel

Hi someguy, Can you send us your remote URL? or, if you wish, please call our tech support line and we'll try to fix it over the phone (818-631-0333). With kind regards, Michel

Hi Matt, If possible, please enable remote access and send us your URL and credentials to support@universal-devices.com. I really do think this is a firewall related issue since Invalid Length means: 1. The client told ISY that it was going to send a file of length x 2. ISY waited to receive the file but received a fraction (or 0) of the x With kind regards, Michel

Hello GDN, I do apologize for the inconvenience. If you don't mind, please do send us your URL and credentials to support@universal-devices.com . I still suspect firewall but the only way to prove it is to actually try the upgrade remotely. Please note that since you do not have a PLM, ISY is running in the SAFE MODE. In SAFE MODE some of the features are disabled such as programs, triggers, and schedules and you will get request failed if you tried any one of them. With kind regards, Michel

upstatemike, Option 1 (having a table) that the users use to pick devices sounds good. The main is not building the table; the main problem is NOT knowing what each table should have. Option 2, wow, I don't want to even think about it Stowaway I shall surely keep everyone appraised of our progress. Rand Yes! All we need is to keep PEEK/POKE around. That solves most of the problems. Then again, I was playing with extended messages again and I must say that they are NOT reliable at all. In more than one occasion, the TimerLinc did not receive the whole packet and wrote the data in the wrong memory locations. My RemoteLinc simply crashed so badly that I had to factory reset it to revive it. Currently, using i2 commands, and using only i2 products, I have a system which is not manageable nor is it in synch with what the devices think. I am sure we'll find a way! Thanks so very much, With kind regards, Michel

Hi Matt, I do apologize for the inconvenience. Some questions: 1. How do you know your ISY's IP address? 2. What port do you use to telnet? Did you also try 126? 3. Have you tried http://www.universal-devices.com/99i ? 4. What firewall software do you have? With kind regards, Michel

Hi Rand, Thanks so very much for the question and one which really does deserve an answer: - Yes, i2 allows for extended messages - In addition to extended messages, there are additional implicit things that also come with i2: -- PEEK and POKE are deprecated -- Setting scene attributes (on level/ramp rate) may require commands rather than PEEK POKE -- Setting other settings such as backlight, mutex buttons, button groups require commands rather than PEEK POKE Therefore, the crux of the problem is PEEK/POKE: had PEEK/POKE remained, then there would be NO problems whatsoever. I understand the reasoning behind deprecating PEEK/POKE: it removes SH from having to maintain or provide internal memory maps to developers since commands act as an abstraction thereof. Now, the problem gets even more complicated since we actually gut out all our code to support i2 and what we found was horrifying: Although there's a command to extract the engine version (i1 vs. i2), this flag is completely meaningless since there are devices that: 1) Are i2, support PEEK/POKE but do not support commands (RemoteLinc) 2) Are i2, support PEEK/POKE, support SOMEcommands (TimerLinc/KPL Relay) 3) Are i2, do not support PEEK/POKE, support SOME commands (Motion Sensor). Emphasis on "SOME" because this "some" is actually quite arbitrary. In short, there's no algorithm to figure out what are device capabilities except through brute force having a table with each one. Now, things get worse ... all the above may depend on the firmware version: the latest SWL 600 watts fits in category (1) above. So, we need a three dimensional array of device type, firmware version, capabilities. And, when new devices come, we have to test them, put them in the table, and figure out how to support them. In summary, I really doubt if we can ever be able to support mixed i1/i2 installations 100% accurately. As you might guess, our beloved SH rep (Steve Lee) already knows about this and I am 100% confident that he's doing as much as he can to resolve these issues. This said, however, I suspect there shall be no resolutions except slowly making i1 devices incompatible and ... With kind regards, Michel

Hi someguy, Please do not unplug ISY when this happens. Instead - and if your ISY is on the Internet - send us an email next time when this happens (support@universal-devices.com) so that we can rule out: 1. computer 2. router I suspect you have another device on your network with is port forwarded using either port 80 or 443: Please go to the Virtual Server tab in your router and let me know if you have any devices listed there and, if so, their settings. Thanks and with kind regards, Michel

Hi xev, Thanks for the update. The reason I work on Sundays is that we don't have good documentation! With kind regards, Michel

xev, It does take more than one program at a time: put your programs inside a folder and import/export the folder. With kind regards, Michel

Hi Bernhard, We are working on it ... it will be available hopefully early next year. With kind regards, Michel

Hello AnthemAVM, I am not sure I understand your question as we already do have that option (when you enter your userid/password, ISY assumes you need authentication). The only issue we have is that TLS might not work with some of the ISPs and we do not have any plans to make it work with ALL ISPs as it will require installation of certificates in ISY (TLS). With kind regards, Michel

Joe, It's always a pleasure and I would also like to thank all participating in our forum for their help, support, and feedback in getting us to where we are now. Thank you ALL. With kind regards, Michel

Hello FLBoy, Thanks so very much indeed. Would you be kind enough to test the same scenario one more time? We have not been able to reproduce this problem yet. Is it possible that you changed the Location between runs? There's a bug where changing location does not change the next run times as it should. This has been fixed in the next release. With kind regards, Michel

Hello petemurp, In addition to the post by AnthemAVM, please note that the error you are getting is DNS related (ISY cannot resolve smtp.comcast.net to an IP address). For your reference, here's the list of error codes and the meanings thereof (http://www.universal-devices.com/mwiki/ ... r_Messages). Now, if you are using a static IP address for your ISY, then I suspect your router is NOT providing DNS relay capabilities. With kind regards, Michel