Michel Kohanim

Hello all, Thanks so very much for all your help in this beta cycle. If no serious bugs are found, 2.8.11 shall become our official release. Please do be kind enough to : 1. Test Network Resource delays 2. Retrieving logs 3. iMeter Solo Beep 4. Importing Network Resources does not overwrite IDs For a list of changes, please take a look at this post: http://forum.universal-devices.com/view ... =6475#6475 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 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 ... 2.8.11.zip OR 992i Series: http://www.universal-devices.com/update ... 2.8.11.zip OR 994i Series: http://www.universal-devices.com/update ... 2.8.11.zip 3. Important Due to invalid Java certificate chain in releases 2.8.5 and above, 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 ) f. Go to http://www.universal-devices.com/99i/2.8.11/admin.jnlp 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. 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.11 - applet f. http://www.universal-devices.com/99i/2.8.11/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 Thanks and with kind regards, Michel

Hello fkoplik, You should still be able to add this device ... the problems you are having has A LOT to do with the fact that ISY cannot communicate with your device. We added support for 2477DH in 2.8.11 which should be out shortly. With kind regards, Michel

Hello jtara92101, Your conclusions are not correct so I MUST retract your Heads Up to other users. ISY subscriptions are invalidated when ISY cannot communicate with the subscriber (in this case Admin Console). The problems of not being able to communicate with your devices preceded whatever state you found your Admin Console in (in this case, loss of subscription channel with is NOT automatically renewed). I cannot explain why your scenes were not working but I am 99.9999% confident it had nothing to do with Admin Console being on. I suspect whatever caused the communication issues will come back and I do not want you to think it has anything to do with the Admin Console. With kind regards, Michel

killervette, You have to press and hold the motion sensor set button till it starts blinking. Then, click it one more time. It seems that ISY cannot communicate with the motion sensor. Can you communicate with other devices? With kind regards, Michel

Hello killervette, My first recommendation: 1. Please make sure your Java cache is cleared ( http://www.universal-devices.com/mwiki/ ... Java_Cache ) and that you are using the correct URL for 2.8.10: http://your.isy.ip.address/admin or admin.jnlp http://www.universal-devices.com/99i/2.8.10 or /2.8.10/admin.jnlp 2. Make sure you do NOT have any green 0101 icons next to any of your devices. This is VERY important. If you do, disable them With kind regards, Michel

jtara92101, It means that while ISY was trying to publish something to the subscriber with the given subscriber ID, the subscription was expired since the subscriber was NO LONGER communicating. With kind regards, Michel

jtara92101, Please upgrade to 2.8.10 and MAKE SURE you using 2.8.10 URLs (http://your.isy.ip.address/admin or admin.jnlp or http://www.universal-devices.com/99i/2.8.10/ or http://www.universal-devices.com/99i/2.8.10/admin.jnlp ). With kind regards, Michel

RLIKWARTZ, How long has the Admin Console been up when you do the test? In all cases, the time on the program summary is MUCH more accurate than the time on top of the Admin Console. With kind regards, Michel

Walrus, Please either use Link Management | Start Linking OR use the Auto Discover from the drop down list in Add New INSTEON device. With kind regards, Michel

Hello Avonlea22, What is your firmware version and which URL are you using? This bug has been fixed in 2.8.10. With kind regards, Michel

Illusion, This reminds of my early days of testing KPLs versions 2A and 2D both of which intermittently caused other devices to turn on. Do yo have any of those in your system? With kind regards, Michel

Hello fkoplik, The problem is communications. Please do the following: 1. Factory reset your switch 2. Go to Link Management | Start Linking 3. Press and hold the set button on your switch With kind regards, Michel

Hi Joe, Please upgrade to 2.8.10 ... I think there may have been an IP conflict: http://forum.universal-devices.com/viewtopic.php?t=5613 This should fix the certificate error. As far as not having My Lighting on your computer, I think the problem may be related to your firewall software. Please make sure ISY is in the trusted zone/white list. You can get your ISY's IP address by going to Help | About. With kind regards, Michel

jtara92101, What happens if you query the thermostat from ISY. Will it then compute? The fundamental problem is this: there's only one interface to get the cool/heat setpoints from the thermostat. This is irrespective of the mode and therefore we are 100% reliant on what the thermostat sends back when queried. If the query fixes the problem, then we can add a query to the code after you change the mode from program auto to something else. If it does not, then we are basically out of luck. With kind regards, Michel

Hello mmknox, That's to be expected since ControLinc is a controller only and does not respond to group commands. With kind regards, Michel

Hello apostolakisl, The problem with that was that if you had too many devices, then some would be chopped (not fitting in the screen). With kind regards, Michel

Moshe, Scene Test in previous versions did not turn on the scene before doing the test. This could explain the scene test issue but this does not explain why your programs do not run. mlennox, Please post your program here. With kind regards, Michel

Hello Joe, ISY has a hard time communicating with your router. If the cables are OK, then the problem could be any of the following: 1. ISY cannot get a DHCP address from the router 2. There are other devices with the same IP address on the network Does rebooting ISY fixes the problem? If so, what version of firmware is ISY running? With kind regards, Michel

Hello Mike R., We have tried numerous techniques to make this faster but, unfortunately, Java is not cooperating! With kind regards, Michel

Hello jp5150, This error occurs when ISY cannot communicate with the device. I recommend removing the KPL from ISY, doing a factory reset on it, and then add it back. If that does not help the situation then the problem is either a defective switch or signal related. With kind regards, Michel

Hello bocaray, Where do you see C instead of F? ficklma1, If the REST interface becomes slow or stops working that's a known issue. If you have communications errors with one or more of your devices, first we have to figure out whether or not the problem is scene related or device related. i.e. do you have the same problem when you query the devices. If you do not have status present in the Admin Console, this points to firewall issues. Would you be kind enough to make sure that ISY is in the trusted/white zone of your firewall. Please note that disabling firewall does NOT help this situation. With kind regards, Michel

Hello Moshe, I have to be clear here since there's absolutely no correlation between 2.8.10 and "some" devices in "some" scenes not responding. ISY does not at all distinguish between sending a command to scene A or scene B. What you might want to try is to disable all your programs and see if this helps the issue. If it does, then you have a program that is causing a conflict. With kind regards, Michel

Hi Tim, Please see my comments below. With kind regards, Michel Thanks! Depends on the type of the socket. For instance, HTTP/HTTPS sockets have a timeout which is configurable in the shell (CWT). Subscription sockets are closed if the subscriber cannot be reached. This said, if the client continues sending HTTP requests, then after a while, all HTTP tasks will be consumed and it might take a while for them to release (backlog of 20) the sockets. I suspect that AtHome, although asleep, is still communicating with ISY and is exhausting the HTTP tasks. No, ISY only closes the socket if there's either timeout or subscriber is not responding. What I think is that AtHome has multiple requests queued up and thus exhausting the HTTP tasks. All sockets are closed and discarded when the system is rebooted.

Hi Tim, Thanks so very much for the update. We really need to know what is AtHome doing when in sleep mode or when it wakes up. From your logs, it seems that multiple threads start communicating with ISY (which is normal) but they never close the socket when AtHome goes to sleep. Do you have access to AtHome developers? If so, please do be kind enough to have them contact us at support@universal-devices.com and we'll figure it out. With kind regards, Michel

Hi Joe, Thank you. This means that ISY is no longer connected to your router/network or the cable from Network to the router is not plugged in correctly. Would you please make sure that the connection from the router to your ISY is secure? With kind regards, Michel