Michel Kohanim

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

Thanks LeeG. 3.2.2 shall be released today. With kind regards, Michel

Hello Xathros, Here's a list of SMTP errors: http://www.universal-devices.com/mwiki/ ... MTP_Errors I think I agree with you that it's not even trying to send the only reasons for which are: 1. Could not get the customization file in which case you should see -1100xx errors for that file 2. The subject/body evaluated to null for some reason With kind regards, Michel

Hi Brian H, No, we added those but they should show up only if the Event Viewer levels 3. We added this to track down a report of system performance issues: the unit was being bombarded by another device on the network but we just didn't know which! With kind regards, Michel

Hello Xathros, Can you please check your Error Log and let me know if you have any -5000xx errors? if so, can you copy paste here? With kind regards, Michel

dougos2, Thanks so very much! Got it. With kind regards, Michel

Precisely what is software correctable and how can you be so sure? The link between the doorlock and morninglinc is NOT accessible to ISY or any other programming interface. This is the only security feature for morninglinc. With kind regards, Michel

Hi Bob, This is so very odd and I think you may be developing a file system issue. Yes, you can use a program with one Action: Irrigation - Reset Variables This should reset the values in the file. If this does not work, please do let me know and we'll take even more drastic measures. With kind regards, Michel

Hello paauto, Yes, you do. It's really not that difficult ... all you need is the MAC address of your computer and the subnet. ISY calculates the rest. And please note that we have a 30 day, no questions asked, money back guarantee. In case the module does not meet your requirements, we'll fully refund your purchase. With kind regards, Michel

Hello dougos2, Thanks so very much for the explanations. I am a little confused since with 3.2.1, you can do what you are suggesting (with notifications) ... i.e. when the 3:00 AM query runs, if you have a program where all your devices are ORed (not responding) and the action is custom notification. Although a little ugly, but it does precisely (I think) what you are seeking till we implement an "any" condition. If this is not what you are looking for, can you please elaborate a little bit more as to what you need? With kind regards, Michel

Hello dougos2, We will surely take your input into consideration. To recap, you basically want a condition to test for "any" devices not responding, correct? aLf, query does indeed have a negative impact. For devices that ISY is not in charge of controlling while you are out, I would just add a program condition of not responding. For others, I do not think you would want to keep querying them. The 3:00 AM query should be fine. With kind regards, Michel

Hello mumpers, Can't reproduce here ... would it be possible for you to send a screenshot of your scene containing the templinc to support@Universal-devices.com? Thanks and with kind regards, Michel

Hello bryanlut, Sincere apologies for tardy reply. You can certainly downgrade the firmware but I seriously doubt it will solve the problem. RF communications go through the PLM only and ISY is not in the middle. If you are still having problems please do not hesitate to contact our tech support team (Submit a ticket link below) and we'll be delighted to login to you system and see what's causing all the trouble. With kind regards, Michel

Hello bpwwer, Is there any pattern (i.e. does it happen all the time for all your customers)? I just cannot reproduce it here but we have to get it fixed in case there's a bug. Would it be possible to change your station to see if you still get the invalid characters? RLIKWARTZ, thanks so very much for the update. There has been one report of system hang for which we have already implemented a fix. The issue was in the file system and I am thinking that perhaps the two issues are related (hopefully). LeeG, thanks as always for your detailed analysis and explanations which are 100% accurate. With kind regards, Michel

Hello bpwwer, This is quite strange. Does it revert to a good number after cycle complete? Does it ever correct itself? Is this an event or when you go to http://isy/rest/climate? Is this the same that you see in the Admin Console? I am not sure where those -- are coming from. We shall take a closer look. RLIKWARTZ, We have not tested restoring a 3.2.1 backup on 3.1.17 (we normally do not recommend this as it's very difficult to support forward compatibility). This said, I suspect it would not work since we had to modify the nodes to add information about I2CS characteristics. With kind regards, Michel

Hello Hermann, Unfortunately not and we do not have any plans mostly because with the installation of Smart Meters, it's very difficult to justify time/resources to implement integration with this device. With kind regards, Michel