Michel Kohanim

Hi Tim, Sincere apologies. Based on our records, we did reply to you on: 2011/07/28 0914PT Please do be kind enough to check your junkmail. In short, the answer is yes absolutely and we'll be delighted to ship an AC adapter to you at no charge. With kind regards, Michel

Hello j0dan, SSL and Safari are a little problematic since it seems that Safari has a problem reusing sessions. So, in essence, for every request, ISY has to create a new key (and go through negotiation) which take too long but will eventually work. This becomes more of a problem if you are using higher key strengths such as 1024 or 2048. Thus far, we have not been able to find a solution for this problem nor has Safari fixed it. With kind regards, Michel

Hi Mike, If your IOLinc (or any other device) is part of any scene, then that device will certainly respond to All On/Off. With kind regards, Michel

Hello j0dan, Can you copy and paste the contents of the body (Actual) that you are posting? With kind regards, Michel

Hi Eddie, got it. Thank you! I have added this requirement to our list. With kind regards, Michel

Hi Tom, Please send your code snippet to support@Universal-devices.com and we'll take a look. With kind regards, Michel

Hi LeeG, Thanks so very much. Are you using Link Management | Advanced Options | Automatic? Currently, the only devices that use Extended Commands are those that do response to i2 commands during calibration (if you are using Automatic). For some reason, your device is not responding to i2 data transfer commands and thus ISY sets it back ti i1. Please note that i2 data transfer commands are different than Set/Get but currently that's how ISY tries to figure out if a device supports i2 commands. With kind regards, Michel

Hello iostream212, I have seen first hand the improvement in performance. And, yes, you can replace your ISY's PLM with 2413S. Please note: 1. 2413S no longer provides power to ISY so you would need to a get a power supply (5-30v, 300 mA, 2mm barrel connector/center positive) 2. Reboot your ISY with the new PLM 3. If you have RF devices and if you have PRO series, make sure that the battery button is grayed out (this way ISY will not try to write to your RF devices; you will do them one at a time yourself) 4. Go to File | Restore Modem (PLM) With kind regards, Michel

Hi LeeG, As always, thanks so very much! Would you be kind enough to let me know the product subcat of your ICON dimmer? Is it 0x1E (30)? And, if so, do you above which version extended set/get commands are supported? With kind regards, Michel

Hello jsp, No, ISY would not turn things on/off on its own. To rule out ISY/programs, please disable all your programs: 1. My Programs 2. Click on If 3. Click on Schedule 4. Uncheck All 5. Save Changes Once this is done, retry your test please and let us know what you find. With kind regards, Michel

Hello j0dan, Here's the issue: The network module has a limited buffer size to process the contents of URLs. So, if you go to Universal Devices, the content length is larger than what we can store (for Network Modules) and thus the read/response error. As you have noted, this is not limited to HTTPS. You should see the same behavior for both HTTP/HTTPS. Furthermore, if you go to a URL that does not respond back with an HTTP response, then you are going to see the same error. The main question is whether or not calling the resource does actually do what it needs to do on the remote machine? With kind regards, Michel

Hi Tom, Sincere apologies. Indeed a bug (and a very bad one) and we just fixed it for the next release. Unfortunately the best way to fix for now would be to restore your backup. Please make sure your backup has your programs (/CONF/D2D folder with many .PGM files). With kind regards, Michel

Hello pdxcav, Please give me an example of the event you want inserted. We do have most of the in the drop down so perhaps there's one we have missed? With kind regards, Michel

Hello thefunconsultant, Would you please try using http://www.universal-devices.com/99i/admin.jnlp ... this should find your ISY on the network. http://isy might not work on non-Windows computers. As far as the on level/ramp rate for your switches, if you have older switches, then you MUST reboot your switch after you are done programming it. To reboot (air-gap), what you need to do is to pull out the set button and then just slip it back in (do NOT push and hold it in). With kind regards, Michel

Hello backinthelab, Thanks so very much for the update. I have recently gotten a lot of those as well. We are looking into it but, thus far, the problem seems to be on the WeatherBug side. At the same time, the fact that all these started with 3.1.5 is suspect so the investigation continues. With kind regards, Michel

Hello bocaray, Personally, I would use a different public port. I have not yet seen a router that does not allow different public-to-private port mapping. Are you certain it cannot be done on your router? Alternatively, you can change the HTTPS port on ISY to some other port (say 8443) and then do 8443 to 8443 (this can be done on Configuration | System | Network section of Admin Console). Once you do that, then your URL would be https://your.remote.ip.address:8443 (or some other port). With kind regards, Michel

Hello pdxcav, You can already do notifications with custom messages. Have you tried Notification/Customization? The other request is not that difficult but it will require the UIs to support other events. With kind regards, Michel

Hello Drew, If you do not have any programs or timers then ISY is in the Safe Mode. Is the RX light lit? You might want to try rebooting the PLM. With kind regards, Michel

Hello j0dan, LeeG's recommendation is 100% correct and right on. As far as performance, if all your devices are responding (there are no communications errors), this round trip should not take more than a second max. Other things that might contribute to the latency: 1. The switch you are turning on is actually turning on a scene which produces large traffic 2. You have other programs that might be running based on the same condition and they might be running before this program With kind regards, Michel

Hi Eddie, Thanks so very much for the feedback. In short, you want notifications for certain actions such that those notifications are presented on a UI of sorts, correct? If so, we could work with third party apps to come up with events (i.e. alerts) that can be generated from programs and are presented by the application (instead of email/SMS). Is this your use case? With kind regards, Michel

Hello Elvis, As I mentioned before, you have all the right in the world to be disappointed. As a matter of fact, I am quite disappointed at ourselves for letting this bug live without addressing it sooner. There are no excuses for this and it shall be fixed in the next release. We do not need any debugging information as we know precisely what's causing the system hang. Please do bear with us for a few more days and we'll have it fixed. With kind regards, Michel

Hi Drew, Please try http://www.universal-devices.com/99i/admin.jnlp and then click on the Add button on ISY finder and then enter the URL for your ISY (i.e. https://192.168.1.100). The Java certificate for the Admin Console on 26 has expired and thus the system will not allow you to do anything with the local Admin Console. With kind regards, Michel

Elvis, I had a hard time deciding whether or not to respond to your post. You have all the right in the world to be upset and I have already stated that not resolving the ELK issue was a complete oversight on our part. It shall be fixed in the next beta release. This said, your post gives the impression that we had designed and promoted ISY for personal safety/property protection and now we are hiding behind our lawyers and disclaimers. It does not require lawyers and disclaimers to clearly and unequivocally state that ISY IS NOT and WAS NOT designed with those applications in mind. Period. As far as reliability, your post gives the impression that you have other reliability issues above and beyond ELK. If so, please post them so that we would have the opportunity to investigate and fix them. If not, I'd appreciate it if you would not make general statements. As far as watchdog timers, I do not wish to get into a philosophical discussion. In our world, watchdog timers are good for hiding bugs (if something fails, reboot). Ideally, we would like to fix bugs and again I apologize for missing the ELK bug. With kind regards, Michel

Hello ryarber, Thank you. Please remove the ELK configuration from ISY temporarily. I think the combination of changing routers and ELK is the root cause of the crash. We should have a fix shortly. With kind regards, Michel

Hi Brad, thanks so very much for the update and your vote of confidence. I really do appreciate it. ELK module should be out soon but, in any case, we are going to have a fix for this crash much sooner. It was completely and oversight on our part not knowing the extent to which this problem affects our customers. Again, sincere apologies. With kind regards, Michel