Michel Kohanim

Unfortunately not! With kind regards, Michel

Hello GregE, It's going to be problematic if you do not have Internet Access. With kind regards, Michel

Hello ficklma1, Thanks for the update. Still trying to figure out where the message is coming from to no avail. Would you please go to your programs and do a Find for all your motion sensors? Please let me know if you have any motion sensors in the Action section of any of your programs. With kind regards, Michel

Hi Bob, ISY blocks on making connections but this means that all other tasks start running while the TCP task is blocked. So, there's absolutely no way that the serial buffer (4K) would overflow. With kind regards, Michel

Hi LeeG, Excellent observation. I have no clue where that is coming from but will get to the bottom of it! Thanks so very much. With kind regards, Michel

Hello jcanter, Don't you have ECM1240 where the box that is next to the breaker panel communicates with EP-1 which is connected to your router? If that's the case, then they are communicating via Zigbee. I am not sure how Zigbee could interfere with INSTEON RF ... this is the first time I am hearing it. With kind regards, Michel

jcanter, If the problems are scene related, I strongly recommend doing a scene test on your scenes. The MS/Brultech issue is quite a mystery and it does not make sense UNLESS the Zigbee communications are impacting/interfering with INSTEON which is also quite doubtful. With kind regards, Michel

Hi jcanter, They are group address (scene) 00 00 nn where nn is the INSTEON group number. With kind regards, Michel

Hello jcanter, INST-ACK means that someone issues a scene command to ISY and this the ACK from the PLM that the command was received and executed. The ECM issue is a new one! Does it interfere with all your RF devices or only the MS? With kind regards, Michel

Hello fkoplik: Please checkout the last entry in this thread: http://forum.universal-devices.com/view ... 3948#43948 to have the ability to replace with 2477DH Hello Candide: It is VERY important for you to clear the cache. If you are on a MAC, sometimes you might have to reboot your MAC for the cache to be cleared. With kind regards, Michel

Hello jtara92101, this is not good and usually a sign of more of the same! With kind regards, Michel

For those who cannot upgrade: please NOTE that you will have to use http://www.universal-devices.com/99i/2.8.10/ or http://www.universal-devices.com/99i/2.8.10/admin.jnlp (or 2.8.11). You CAN NOT use your current version coming from ISY. For future versions, this should not be a problem. Polexian, no, this is not a bug. We did verify that we are sending the correct message/command. The LED brightness works ONLY on SWLs with BEEP. It does not work on others. With kind regards, Michel

Yes. Thank you! With kind regards, Michel

Hello majkman, Yes, you may! With kind regards, Michel

Hi All, Release 2.8.11 is now available: http://forum.universal-devices.com/viewtopic.php?t=5822 With kind regards, Michel

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