Michel Kohanim

Hi telljcl, If you are looking to support ZWave devices, then you should NOT get 994iZ ... you should get 994i series and then wait for our Zigbee expansion/dongle which plugs into 994i. We will only support RCS ZWave thermostats in our initial release. With kind regards, Michel

mitch236, No, you should never open port 80; that's completely insecure. Are you sure port 443 is not forwarded to something else in your house? With kind regards, Michel

Hi KenN, What's your operating system including 32 vs. 64 bit? Have you tried https instead of http? If it works with https, then the problem is Kaspersky. With kind regards, Michel

Hello foxcob, Can you tell me whether or not you are still having problems? I suspect that your Java cache has not been cleared and perhaps you are not on the right UI (http://www.universal-devices.com/99i/3.3.5/admin.jnlp). With kind regards, Michel

Hi jmwking, I strongly recommend replacing your PLM as well. If you indeed have Access Points (not SignaLincs), those should be OK. With kind regards, Michel

Hi raydoc, Do you have a MAC? Have you given your ISY a static IP address? If not, please check your router's DHCP client list to see whether or not ISY is even listed. If it is, try using the URL directly in a browser. What do you see? With kind regards, Michel

Hi hackwright, High on our list! With kind regards, Michel

Hi apostolakisl, The URL you are using (I am not sure where you got it from) is not correct. There's a '-' between universal and devices. So, http://www.universal-devices.com/99i/3. ... board.jnlp With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.3.5 (RC1) release! For a list of changes, please take a look at this post. Although a minor release, it's packed with important enhancements such as SSL communications with ELK (requires ISY994 PRO series), UI Themes for accessibility, and improved file system performance. Know Issues - None Things to test: - SSL Communications with ELK which requires ISY994 PRO Series (Configuration instructions) - File | Themes - File system and programs - Din Rail Dimmer/Relay - Micro On/Off and Dimmer 994i ZS Series - Invalid attributes Important Information 1. Important Brultech module is no longer supported on ISY99 Series. Please contact sales@universal-devices.com for options 2. Important NetBios removed from ISY99 Series. You can no longer access ISY by going to http://isy on Windows 3. Important If you have a 994, you will need to re-install a certificate. Please review ISY994 Series Advanced Network Security Configuration for more information. 4. Important We have removed SSLv2 support (very insecure) from ISY99/ISY994. Unfortunately, the only protocol supported by MAC with Java 1.6 is SSLv2. As such, you MUST upgrade your MAC to Java 1.7 (Software Update) 4. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari. 5. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion 6. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly 7. For a discussion of variables, please look at our Program Variables forum. Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series ISY 994i Series 3. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 4. Choose the file saved in step 2 5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://your.isy.ip.address/admin - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d b. http://your.isy.ip.address/admin.jnlp - Java application c. http://www.universal-devices.com/99i/3.3.5 - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d d. http://www.universal-devices.com/99i/3.3.5/admin.jnlp - Java application Best method to access Admin Console Dashboard - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel

Thanks. Did you accept the security warning for Bouncy Castle library? With kind regards, Michel

Hello mad_scot, Is this a 99 or 994? Are you using https://www.universal-devices.com/ssl/insteon? Are you certain that you have accepted the security warning for Bouncy Castle library? With kind regards, Michel

Hi mad_scot, Are you local to your ISY? With kind regards, Michel

Hello mrjimmystewart, In all likelihood, your router does not support UPnP. In all cases, it's better to create manual port forwarding rules: http://www.universal-devices.com/mwiki/ ... PnP_Router With kind regards, Michel

Hello remedy1234, Unfortunately a know issue with Java 1.7 and MAC. I am so very sorry. With kind regards, Michel

Hi Matt, If you do not see ANYTHING in the event viewer, then it's certainly firewall related. ISY listens to ports 80 (http) and 443 (https). Clients, such as Admin Console, subscribe to ISY (depending on http/https) and then keep the subscription socket open for further communications. Some firewalls, do not like persistently open sockets and thus sever the subscription channel. So, in short, the destination port from Admin Console to ISY should be ports 80 and 443. Some firewalls are more lenient with https traffic. So, what you might want to try instead is: 1. Go to http://www.universal-devices.com/99i/admin.jnlp ... This should install an icon on your desktop 2. When Admin Console comes up, minimize it 3. Click on the Add button in the Finder dialog 4. Use the IP address for your ISY in https://your.isy.ip.address 5. Close Admin Console, double click on the icon on step 1, and choose the entry with https With kind regards, Michel

Hi PLCGuy, What's in the body? If nothing, you might want to add a something to the body. -19 means Write Failed. In short, the server didn't let ISY write the body of notification. With kind regards, Michel

Hello mzanni, Since we have never seen/experienced this problem before, I would have to first rule out firewall issues and, if so, then I will conclude the PLM is defective. Here's how we can make sure you don't have any problem with your firewall. Please open up the Event Viewer again and change it to level 3. Go to Configuration | System tab | Clock and click on Synchronize Now button. If you see anything in the Event Viewer, then you do not have any firewall issues and I would strongly suggest getting a new PLM. On the other hand, if you do not see anything in the event viewer then the problem is firewall which will have to figure out the resolutions to. With kind regards, Michel

Hi Rich, I am sure you will find applications that will provide you with that functionality though I am against it for security reasons (you'll open your computer up to almost anything). I am still not clear why activating the camera directly from ISY takes more time than the batch file. With kind regards, Michel

Hi mzanni, Quite odd. 1. Can you tell me what's your ISY's firmware version? 2. Can you tell me what's your Java version? 3. Can you tell me whether or not you have a firewall software on your computer? If so, which? With kind regards, Michel

Hello rschneid, Please increase the timeout. Read error only means that ISY didn't get a response within the timeout period. And, as you mentioned, ISY cannot handle Javascript so this method is not going to work at all because Javascript is processed by the client (in this case ISY). With kind regards, Michel

Hello mzanni, Please unplug your PLM, wait for a minute, and then plug it back in. Once that's done, reboot ISY. Once rebooted, please login to the Admin Console and go to Tools | Diagnostics | Event Viewer. Change the level to 3. If you see any traffic at all, please paste the contents. If not, click on Start Linking and then paste the contents. With kind regards, Michel

Hi mikeiud, Actually, it's the other way around. It's DirecTV that indiscriminately floods the network with UPnP packets and then, again indiscriminately and without regards to type, contacts those devices that respond. In some cases, the problem is so severe that ISY might lock up. We have not been able to figure out what causes these burst from DirecTV. With kind regards, Michel

Vyrolan, No, not true. LeeG's comment is 100% true: viewtopic.php?f=28&t=10009&p=75777#p75777 For non-I2CS devices, we used to allow devices to be added by forcing their type. Releases 3.3.x do not allow you to add device X as device Y. We can debate whether or not this should be the case, but we did have multiple support issues + I2CS things that propelled us to take this direction. With kind regards, Michel

Hello deirwin, LeeG is 100% correct on both counts. Please go to Configuration | Networking | Network Resources and make sure you have a Resource with ID=1. If you do have it, please open it with Resource Editor and make sure it has contents and re-save it. If that does not work: 1. telnet to ISY 2. login and at the prompt type: RF CONF/NET/1.RES With kind regards, Michel

Hi Phil, ISY has two ports: one for http (unsecure) and one for https (secure) both of which you can change in Admin Console | Configuration | System | Network Settings. First of all, please do NOT ever forward to the unsecure port. As far as the secure port, usually anything above 2000 should be OK and not used by well-known services. For your reference, please take a look at instructions here: http://www.universal-devices.com/mwiki/ ... PnP_Router With kind regards, Michel