Michel Kohanim

sun-sense, It's mostly due to our desire to keep the applet size small. Light bulbs signify "responders" and buttons signify "controllers". With kind regards, Michel

SteveSBE, If you are using Windows Vista/7 with Office 2007-2010, then please do make sure that the MACROS are enabled. If not, you will see nothing in Excel. As a test, you could ask ISY not to show the logs in Excel and instead save it to a file. With kind regards, Michel

Hello johnnyt, Programs not showing is mostly related to ISY running in safe mode because it cannot communicate with the PLM. The next time this happens please go to Tools | Diagnostics | PLM Status/Info and let us know the status. sfurman, MEM/ERR light blinking could be due to ISY not being provided a DHCP lease. The first thing I recommend is upgrading to 2.8.4 in which we added some workaround for routers that might refuse to give a lease to a device. With kind regards, Michel

Hello RatRanch, There were couple of drops on the 13th. Please do be kind enough to download and install again. Or, if you wish, you can wait for 2.8.5 which should be out shortly. Candide, that's really odd because the basic changes in 2.8.4 were non-INSTOEN/x10 related. Please do keep us posted with what you find. With kind regards, Michel

Hello RatRanch! Apologies for the inconvenience. When did you update the firmware? If it's more than 3 days ago, please re-download and re-install the firmware. There were some issues with the initial releases which are fixed now. Hello Candide, I have 2.8.4 running here in the lab and I have a program that sends an X10 off command every minute. It has been working fine thus far. With kind regards, Michel

Hi Billy, This news is bascially the highlight of my work-week!!! Thanks so very much for the update and your patience throughout the troubleshooting. With kind regards, Michel

Hello kyleohme, You need a new/repalcement PLM! With kind regards, Michel

Hello kyleohme, Please go to Tools | Diagnostics | PLM Status/Info and make sure the status is Connected. If not, then you have PLM issues ==> ISY is in Safe Mode and that's the reason you cannot save any programs. With kind regards, Michel

Thanks Illusion. Looking forward to it. In the meantime, I received a new KPL and it's also working fine. With kind regards, Michel

Hi Illlusion, thanks so very much for the update. So, it was the PLM causing all the issues? With kind regards, Michel

Hi Guys, Just wanted to let you know that, as always, LeeG has helped us with the Motion Sensor light issue. We are going to fix it and put a patch out soon. LeeG, thanks so very much! With kind regards, Michel

Hi kaplansa, Yes, you are correct. Once you install the humidity modules, you should be able to get humidity readings for both of your thermostats. The only word of caution is that only the 7 day programmable thermostats supported humidity (as far as I remember). With kind regards, Michel

Hello gfridland, Light data is basically quite limited in WB and it all depends on the weather station and it's position. Unfortunately, when it gets to dusk/dawn, the numbers get even more inaccurate (between 0 and 2) and therefore I strongly recommend using this information in conjunction with sunrise/sunset times. With kind regards, Michel

Hi Brian H, Apologies for a tardy reply. The errors you are seeing are related to the first fix (file system access) and should be completey fixed in the latest 2.8.4 drop. If you have not upgraded your 2.8.4 to the latest (yesterday), may I humbly suggest that you do so? With kind regards, Michel

Hello Robin, Thanks so very much for the update! To answer your question: the issue with the program tabs being blank impacted MOSTLY those who accessed the Admin Console directly from ISY (instead of /99i/.. on our website). Now, to access anything in ISY, we have to communicate with our file system which, recently, we made a minor modification thereto to improve performance. So, 1. In the first instance (of not being able to get program tabs), the issue was that the performance improvement patch although improved performance but, in rare cases and for larger configurations, actually caused file open errors. So, in the first fix (firmware only) we removed the performance patch 2. During the build process - and unfortunately so - there were some Java mismatch errors that were not reported and thus the full version of #1 above had compile errors. This caused the applet to throw an exception while loading All and all, the problems could have been completely avoided with more diligence on our side. I do very much apologize for the inconvenience this has caused all those who had to go through multiple firmware updates. With kind regards, Michel

Hi all, Thanks to a lot of help from gfridland, we found the problem with the invisible programs: Java issues on our side caused invisible compilation errors which were propagated into the firmware. This has now been fixed. Please download and upgrade again IF AND ONLY IF you have blank Program Summary/Details tabs. Here's the link: http://www.universal-devices.com/update ... _2.8.4.zip . With kind regards, Michel

Robin, yes, please let me access your system remotely. Please reset your userid/password and send the URL to support@universal-devices.com . gfridland, I would like to the same with your system if possible. Thanks and with kind regards, Michel

Hello hbsh01, If you wish, you can send us the error log to support@universal-devices.com and we'll review it. Again, as long as you do NOT have any -50001 errors, then the problem is either logic related OR junk mail related. What version of the firmware are you on? With kind regards, Michel

Hello hbsh01, Apologies for not being clear. You should look at the last column. And, no, -5012 is not the same error. I do not recommend changing the timeout simply because: a. If there are indeed connection errors, this value does not help b. No errors are reported in your log Please check your Junk mail. Also, you might want to try to simulate the events while looking at Program Summary tab to see whether or not the programs get actually called. With kind regards, Michel

Hello kaplansa, If you are talking about the sensor part of IOLinc, then, NO, this is not the normal behavior: IOLinc should report its sensor status to ISY. What you might want to do is to do a Restore on the IOLinc and then use the Event Viewer to see if there's any traffic when the sensor status changes. If you are talking about the Relay, and if the relay is controlled by anything outside of ISY, then yes, this is normal. With kind regards, Michel

LeeG, You are 100% correct. The issue appears to happen more often when the Admin Console is accessed via ISY. It has to do with the file system. I strongly recommed installing the firmware only build. Tim, you are welcome. Yes, please do install the firmware only build. With kind regards, Michel

Hello k7zpj, Sincere apologies for the inconvenience. Please see the post right above yours. With kind regards, Michel

Hello to both, Please check your error logs for -5000x errors. If you have any of those, it means that ISY could not send the email for the reason described here: http://www.universal-devices.com/mwiki/ ... MTP_Errors With kind regards, Michel

Hello all, Sincere apologies for the inconvenience. This problem is repeatable and it's due to a bug in the firmware. Please either reinstall 2.8.4 (by downloading it again) OR, you can install the firmware only (which is much smaller and quicker to install): http://www.universal-devices.com/update ... _2.8.4.zip Again, sincere apologies. With kind regards, Michel

Hello Robin, Apologies for the inconvenience. We did find the bug (with many thanks to silverton38) and now it should be fixed and working smoothly and reliably. Please do be kind enough to download and reinstall the 2.8.4 firmware and let me know. With kind regards, Michel