Michel Kohanim

Hello GMD99, Do you have any firewall software on your computer. Some firewall software prevent your computer to communicate with devices that are not in their trusted zone. You might want to try https://your.isy.ip address instead. Some firewall software are more lenient on HTTPS communications. With kind regards, Michel

Hello flemingmike, Unfortunately not fully integrated. This said, you can use Network Resources to send commands to pretty much any camera. With kind regards, Michel

Hello sanders2222, I am so very sorry to hear. Do you remember what's your ISY's firmware version? Also, do you have access to your router? If so, can you ping ISY? With kind regards, Michel

Hello ScottAvery, Thanks so very much for your feedback and, as I mentioned in my reply back to you, you are 100% correct. With kind regards, Michel

Hi morgan4x4, Try DIM and BRT commands. With kind regards, Michel

MikeBro, I do hope that you are aware of the fact that we do have a dedicated tech support team ready to help you. Please either call us or Submit a ticket (link below) and we'll be delighted to schedule a time most convenient for you to walk through your setup and figure out what's going on. With kind regards, Michel

Hi LeeG and gviliunas, I think we have found the bug with IOLinc ... as we had expected, supporting i2cs in combination with i1 and i2 is basically a nightmare. We should have a build hopefully by Friday. Hi molney, if you have PLM version 98, that's the root cause. If not, would you please use Event Viewer on the last level (Device Communications), retry and paste the contents on a reply. With kind regards, Michel

Hello jamesddelaney, If you do not mind an alpha, please send an email to support@universal-devices.com ... I think we may have found some of the issues with random i1, i2, i2cs communications. With kind regards, Michel

Hello strahan001, Actually, your question made me think so, now, every time cycle complete is called, we send an update to the UI + have programs re-evaluate. Forecast is indeed on our list but we have not had good and reliable information from WB. With kind regards, Michel

Hello strahan001, Currently there's no easy way of doing this since things are happening based on the polling cycles. With kind regards, Michel

At least they did get an answer. We never got one! With kind regards, Michel

Hello ekuzmack, The main problem with using network resources is that it's a one way street: it can send commands but it cannot receive commands. Furthermore, as far as I know, Vera does not have an HTTPS server so the commands you send to it from ISY would not be encrypted. This is a little scary for me especially since we are talking about door locks. But, I must confess that I do not know much about Vera except bits and pieces of information I receive from customers such as yourself. To report door lock status to ISY, you can use one State Variable and then - and if possible - call ISY's REST interface from Vera. This said, I strongly suggest using HTTPS (not HTTP) as all your credentials and door status are going to be transmitted in the clear otherwise. With kind regards, Michel

Hi Tim, precisely but with one note: the actual change takes place immediately. The event generated to be sent to the Admin Console takes place at each poll (to reduce network traffic). With kind regards, Michel

Unfortunately not. We did send them a request for APIs but never heard back. With kind regards, Michel

Hello dennisric, It would really be best to contact our support so that we can figure out what's going on. Please note that in recent editions, you DO NEED to have an Access Code (any 4 or 6 digit number) filled out otherwise ISY cannot communicate with ELK. With kind regards, Michel

Hi Andy, thank you. I think the problem is isolated to v95 thermostats. With kind regards, Michel

Hi Andy, Is your thermostat v95? As far as the MAC issue, I have looked into it and can't reproduce here. It does not happen all the time, correct? Are there any specific instances that it does happen: for instance, when everything is collapsed or when some are expanded and others collapsed, etc. With kind regards, Michel

Hello HokiePerogi, What's your ISY's firmware version? If not 3.2.2, I strongly suggest upgrading it so that we have the same point of reference. Once upgraded, please remove those devices from ISY, and add them back in. With kind regards, Michel

Hello all, excessivechaos, The process is almost correct: you have to make sure your thermostat is in the Off position before you start linking. Teken, my pleasure. andyf0, can you tell me what version of Linux and what version of Java you are running? With kind regards, Michel

Hi Teken, I am so very sorry to hear this. SWL Timer must be one of those in-between devices that reports as I2CS but does not really support i2cs. We shall have a closer look to see if can add some traps for specific devices. Hi excessivechaos, I think the problem is that the links were not added properly to your PLM. Please remove the thermostat and register it back in. This should solve the status issue. With kind regards, Michel

Hello Xathros, Thanks so very much for the update. Please do be kind enough to keep and eye and let us know if you see any more anomalies. With kind regards, Michel

Hello Teken, Please right mouse click on the device | Diagnostics | Query Insteon Engine. After you are done with that, retry and let me know if you are still having problems. Writing 0 bytes to devices does not mean anything significant: it just means that there was nothing to write. If you wish, you can try restoring your device. With kind regards, Michel

Hello all, Release 3.2.2 (Beta) is now available. With kind regards, Michel

Hello all, Release 3.2.2 (Beta) is now available. With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.2.2 release! For a list of changes, please take a look at this post. This is a minor release to fixed the bugs introduced in 3.2.0/1 when we introduced support for I2CS devices (including FanLinc). In addition, we added support for a couple of new INSTEON devices. Know Issues None Things to test: - Overall performance - Register and manage I2CS devices, FanLinc, TempLinc, and v95 Thermosats Important Information 1. Important If you have already installed a self signed certificate and your current firmware is 2.7.10 and below, you must reinstall a new one before the upgrade. 2. 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. 3. 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 4. 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 5. 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. 99/994i - http://isy/admin - applet (Windows only) b. 99/994i - http://isy/admin.jnlp - Java application (Windows only) c. http://your.isy.ip.address/admin - applet d. http://your.isy.ip.address/admin.jnlp - Java application e. http://www.universal-devices.com/99i/3.2.2 - applet f. http://www.universal-devices.com/99i/3.2.2/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel