Michel Kohanim

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

Hi Guys, The main issue is that we do not have a MAC Book and instead we have an iMAC with a regular keyboard and mouse. We'll surely look into this since the Admin Console must act as natively as possible. With kind regards, Michel

Hello killervette, Not yet. All this is supposed to be in the upcoming ELK module which is taking much longer than I had anticipated. With kind regards, Michel

Hi Robin, Thanks so very much. It's quite odd that you cannot access ISY via MobiLinc but you can safely do so via the Admin Console. Admin console not showing status is related to the fact that ISY was not able to communicate with the Admin Console. It's very important to clear Java cache. If you are still having issues, please do let me know. Hi Tim, Please send an email to support@universal-devices.com. I would like to log in to your system to see what's going on. With kind regards, Michel

Hello all, For those with issues relating to 2.8.3, please do be kind enough to try 2.8.4: http://forum.universal-devices.com/view ... 8822#38822 With kind regards, Michel

Hello all, Release 2.8.4 Beta is now available. Although this firmware has been tested thoroughly, please note that this is still a beta firmware. Please do be kind enough to : 1. Test Linking/Adding Devices/Creating and/or Modifying Scenes and Adjusting Scenes within programs 2. Observe any type of network anomaly For a list of changes, please take a look at this post: http://forum.universal-devices.com/view ... =6475#6475 Please note that ISY-26 is no longer included in the firmware builds. Instructions 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip ISY 99 Only - http://www.universal-devices.com/update ... _2.8.4.zip 3. It is very important that you use your current ISY's Admin Console to perform the upgrade by going to your http://your.isy.ip.address/admin. For MAC users, if upgrade fails, please try https://your.isy.ip.address/admin 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file saved in step 2 6. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache: http://www.universal-devices.com/mwiki/ ... Java_Cache 7. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://isy/admin - applet (Windows only) b. 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/2.8.4 - applet f. http://www.universal-devices.com/99i/2.8.4/admin.jnlp - Java application 8. 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: http://www.universal-devices.com/mwiki/ ... rtificates IMPORTANT Due to the sensitive nature of supporting MorningLinc, users now must agree to terms and conditions upon Admin Console start up otherwise the dialog keeps popping up every time the Admin Console is started. Thanks and with kind regards, Michel

Hi Andrew, I do understand the usability issue. At the moment, there's basically no way around it unless we make the Admin Console keep polling ISY and thus cause other problems. As it stands now, when you lose connection with ISY, based on the advertised max-age information provided by ISY during authentication, Admin Console "assumes" the subscription is alive until either: 1. the keep-alive/max age duration is passed without an event 2. there's socket connection exception For the percentage of the time this is indeed an issue (not to mention that the system is usually left alone once configured), the workaround (keep polling ISY) is completely and utterly a very ugly solution. With kind regards, Michel

Hi Brian, I think these are all related to the fact that in 2.8.3, ISY prevents other tasks from running in case the database is locked. 2.8.4 should be out shortly. With kind regards, Michel

Hello nowandthen, You do NOT have to upgrade to 2.8.3 to be able to use the Motion Sensor functions. Simply use the link .... With kind regards, Michel

Hi Tim, Thank so very much for the update. I am not yet sure what the root cause is but most of the reports are related to communications issues. And, in 2.8.3, we added some safeguard mechanisms to reduce the risk of device database corruption which basically prevents one task from taking over while the PLM communications module is talking to the PLM. So, in short, if there are many communication errors (as it seems the case is for all involved), ISY does not let other tasks run that might require datbase access and thus all the slow and intermittent access issues. With kind regards, Michel

Hello kaplansa, At the minimum you need some type of energy monitoring devices (such as Brultech or iMeter Solo). Then, it's all up to you whether or not you want a portal provider: 1. If you want to have graphs/charts/history then you do need the Check-It portal module. The added advantage of this is that no longer would you need to do port forwarding 2. If you are not concerned with graphs/charts/history then all you need is the Brultech Module. This will enabled you to control your devices based on your electricity usage With kind regards, Michel

Hello Andrew, 5011/12 means that ISY could not communicate with the Admin Console. That explains why your statuses are blank or invalid. This is usually caused by firewall software on your machine blocking ISY. If you have firewall software, you MUST put ISY in the trusted zone or white list. Hello bocaray, You can already do this by using "Run at Startup" flag for any program you desire. This can be set in Program Summary tab. In effect, the program flagged as such runs at reboot no matter what. With kind regards, Michel

Hello kaplansa, GreenNet.com is an energy monitoring/control/audit provider which uses ISY to save energy. You do NOT need this module. Please do be kind enough to forward your Google receipt to sales@universal-devices.com with subject RMA and we'll immediately issue you a refund. With kind regards, Michel

Hello Billy, I truly apologize for all the trouble. I have not changed any of the jumper settings on the thermostat. What I would like to do is to give you access to our lab system so that you can test it out for yourself. We have two thermostats here one with a humidity sensor and the other without. Would you be kind enough to send an email to tech@universal-devices.com and I'll provide you with the URL to our system? With kind regards, Michel

Hello nowandthen, The new motion sensor capabilities are UI related only. So, you can safely use them by using any of the following URLs (as long as you have 2.7.15 and above): http://www.universal-devices.com/99i/2.8.3/ http://www.universal-devices.com/99i/2.8.3/admin.jnlp As far as the nasty bug, I am becoming more convinced that the problem is PLM related by the minute since most of those with the issue downgraded to older versions and with the same symptoms. So, it might not actually be a bug let alone a nasty one. With kind regards, Michel

Hello silverton38, At the moment, I must conclude that the problem is indeed PLM/device communications related. Before continuing with the downgrades, would you be kind enough to send an email to support@universal-devices.com and we'll schedule a call to see what's going on with your system. Sincere apologies for the inconvenience. With kind regards, Michel