Michel Kohanim

Hello ketchup318, Please go to https://www.universal-devices.com/ssl/insteon and reinstall a self signed certificate for your ISY. The old certificate no longer works with the new firmware. With kind regards, Michel

Hello junkycosmos, The problem is: Body: ${alert.event} at ${alert.date} ${alert.time24} You see, alert.event is the event that caused the program to run. What you want instead (to be consistent with the version without variables) is program.name. With kind regards, Michel

Hello, That's quite odd ... the programs use device address and NOT the name to present the name. So, are you certain that the not specified device is actually the one you are renaming? Also, please note that programs should reflect the new name. With kind regards, Michel

Hello wrj0, I think you installed the module before upgrading to 3.1.4. Please do be kind enough to send your uuid to support@universal-devices.com and we'll reactivate it again for you. Hi Brian, that usually happens if ISY cannot communicate with a client (in this case Admin Console). In some cases, after clearing Java cache, the computer may be too busy starting to run the new code and thus ISY will not get the acks as quickly as it would want. This will cause ISY to expire the subscriptions and thus those errors and lack of device state on the UI. With kind regards, Michel

Hello junkycosmos, -5011 means that a client (such as Admin Console) which has subscribed to ISY is not longer accessible. So, if you have a mobile device such as iPhone or Droid which might go to sleep mode, then you will see these errors because they do not unsubscribe. With kind regards, Michel

Hi Lee, Thanks so very much! Verified as bug and already fixed for the next release. With kind regards, Michel

Hi johnnyt, What firmware version were you using. The scene UI does NOT allow a sensor node to be added as a responder. With kind regards, Michel

Hi Illusion, Thanks so very much. Verified as bug and unfortunately it has to wait till 3.1.5. With kind regards, Michel

Hello all, Release 3.1.4 (Beta) is now available: viewtopic.php?f=25&t=6547 With kind regards, Michel

Hello all, Release 3.1.4 (Beta) is now available: viewtopic.php?f=25&t=6547 With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.4 release! For a list of changes, please take a look at this post. Things to test: - Irrigation Module -- Help | Purchase Modules | Irrigation Module ... you can use coupon code irrigation-promo-11 for $15.00 off (total will be $4.00) - New supported devices For a discussion of variables, please look at the new Program Variables forum viewforum.php?f=68 Notes: 1. ISY-26 is no longer included in the firmware builds 2. 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 3. 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: http://www.universal-devices.com/mwiki/ ... rtificates 4. IMPORTANT - 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 Instructions: 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip ISY 99i Series: http://www.universal-devices.com/update ... _3.1.4.zip OR 994i Series: http://www.universal-devices.com/update ... _3.1.4.zip 3. Important (If upgrading from 2.8.5 through 2.8.14) Due to invalid Java certificate chain, please make sure to remove all Universal Devices certificates from Java: a. Close all browser sessions b. Open Java Control Panel (Java Preferences on MAC) c. Click on the Security tab. Remove all Universal Devices certificates (on MAC, click on the '-' button at the bottom) e. Clear your Java Cache ( http://www.universal-devices.com/mwiki/ ... Java_Cache ) 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file saved in step 2 MAC users: if upgrade fails, please add https://your.isy.ip.address to ISY Finder (see 3f above) 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. 99i - http://isy/admin - applet (Windows only) b. 99i - http://isy/admin.jnlp - Java application (Windows only) a. 994i - http://or/admin - applet (Windows only) b. 994i - http://or/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.1.4 - applet f. http://www.universal-devices.com/99i/3.1.4/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp Thanks and with kind regards, Michel

Hi johnnyt, Thanks so very much for the update. You cannot add a sensor as a responder since they DO NOT respond; they are controller's only. You can put the Relay in a scene as a responder. With kind regards, Michel

LeeG, thanks so very much for all your help. johnnyt, I am getting a little confused. I thought the problem is that you have devices that respond on their own to another IOLinc to which they were once linked. I am not sure I understand what the "bad" IOLinc got to do with everything else. In any case, this is what you have to do to get rid of bad IOLinc responder link: 1. Find out in which scene Basement Dampers S is a controller 2. Add the bad IOLinc in that scene as a responder 3. Check the Link records and make sure you still see the bad record 4. Remove the bad IOLinc from the scene If this does not work, then I suspect that we have a corrupted database file on ISY. With kind regards, Michel

Hello bktong, I am so very sorry to hear. Would you be kind enough to do the following: 1. Please send me both your error as well as system logs (support@universal-devices.com) 2. If possible, remove ELK configuration from ISY (Configuration | System) by clearing out the IP address and port settings under ELK section With kind regards, Michel

Hi johnnyt, This is extremely odd. Would you be kind enough to print your topology (Tools | Topology) and see if those responders belong to any other scenes at all? If so, to what other scenes? As you have noted, the problem is the responder links ... they should have been removed but they have not been. Can you also tell me your firmware version please? With kind regards, Michel

Hi johnnyt, This is extremely odd. Would you be kind enough to print your topology (Tools | Topology) and see if those responders belong to any other scenes at all? If so, to what other scenes? As you have noted, the problem is the responder links ... they should have been removed but they have not been. Can you also tell me your firmware version please? With kind regards, Michel

Hello junkycosmos, I think the problem with MobiLinc has already been addressed by a new version of MobiLinc. As far as the error log entries, those errors do NOT necessarily mean lack of Internet connection. They mean different things based on the error codes such as: - The server did not respond - The server responded with bad status - Can't resolve server name etc. For a list of errors and what they mean please consult: http://www.universal-devices.com/mwiki/ ... r_Messages With kind regards, Michel

Hello johnnyt, On the responder IOLincs, if you go to Tools | Diagnostics | Show ISY Links Table for each, does the controller IOLinc address show up in there? With kind regards, Michel

Hello bktong, Not really ... the main issue is that since our code base (point of reference for debugging) is now at 3.1.3 (and soon 3.1.4), it's easier for us to pinpoint/isolate issues. With kind regards, Michel

Hello RBC, Yes, ISY/PLM should be able to restart without the need for network connection. With kind regards, Michel

Thanks bktong, please do keep us posted. Lately, we have also seen at least a couple of cases of EZxxx devices bombarding the network to the point that the PLM/ISY become VERY VERY slow to unresponsive. In case of ISY, you will see UDQFull which indicates queues are getting filled up. ISY recovers if EZxx is removed. So, if you have EZxxx devices, please check your error logs. Furthermore, you will find a lot of information in error log which might help with diagnosis. With kind regards, Michel

Mr. Burtis, ISY keeps a running tab of where it stopped during any operation and that's the reason for green 01010 icons (pending operations). Updating link records in ISY manually might cause your system to crash. With kind regards, Michel

Hello RBC, ISY should work independent of any network connection. The only functions that would not work are those relating to network such as email/notification, synchronizing time with NTP, etc. If you have a lot of email notifications then if you do not have network connection, ISY might run a little slower since it queues up all the emails to be sent out. I am not sure why your lights didn't work ... is it possible that the time was off a little (no NTP)? With kind regards, Michel

Hello bktong, Sincere apologies for the inconvenience. First, please do be kind enough to upgrade to 3.1.3. Secondly, if you have ELK hooked up to ISY, AND IF you use ELK RP, that's when the unit locks up. This is a known issue which should be fixed shortly. With kind regards, Michel

Hi thruster999, Thanks so very much for the update and I am very sorry we could not find the root cause. Good luck and with kind regards, Michel