Michel Kohanim

Hi mitch236, Please post the segment of the log relating to this + 5 records before/after. With kind regards, Michel

Hello upstatemike, As of late, we have noticed that when you are adding an RL to ISY, if you use any of the 1-6 buttons to get OUT of programming mode, then that button does not report its status to ISY. With kind regards, Michel

Hello geekinc, Is it really your ELK IP address or your ISY IP address? If ELK IP address, then it means that your router is either assigning the same IP to both ISY and ELK or that either one of these devices are sharing the same IP address. Can you try unplugging M1XEP and see if you still have this issue? With kind regards, Michel

Hello mflieger, Before any of the programs working, you have to make sure that ISY actually "hears" the button presses on your RL. As such, please open the Tools | Diagnostics | Event Viewer, change the level to 3, then click each and every one of your RL buttons and let me know if you see any "DON" or "DOF" records. If not, I strongly recommend removing the RL from ISY, doing a factory reset on it, and then add it back in. Please do ensure that you do NOT use any of the 1..6 buttons to take the RL out of programming mode since, by doing so, that button will never report its status to ISY. With kind regards, Michel

Hello bktong, Apologies for the inconvenience. Can you tell me which firmware version you are running and which URL do you use to access it? You might want to try: http://www.universal-devices.com/99i/2.7.15/admin.jnlp With kind regards, Michel

Hello gshub77, The main issue is that in Program Auto and Day mode, we could not query the thermostat properly. In some cases, it would return 0 and in others 16 or some values completely foreign to us. As such, we disabled the query and made those values invisible in the UI. This is something that we are tracking and once we figure out the cause, it shall be fixed (perhaps it might require new thermostat dongle). And, finally, we do not at all intend to force anyone to use ISY for everything especially when the device supports it natively. With kind regards, Michel

Hello johnradams, Thanks so very much for the update and I am so very glad that you got your Internet access working. You are correct that the menu item is misleading ... since most routers do not have UPnP enabled by default, and since UPnP has not proven as reliable, we might even do away with it. Still investigating ... Thanks again and with kind regards, Michel

Hello johnradams, Two comments: 1. If the static IP address is dedicated to ISY does this mean that you have configured ISY with that IP address? If so, then the only way to get to ISY would be through that IP address (not 192.xx.xx.xx) 2. If not, then you DO need port mapping regardless of ports 80/443 being overloaded. And, in this case, you do not even need a static IP address dedicated to your ISY since your router (assuming sonic wall) will do all the NAT translation between your ISP's IP address and your ISY's local IP address. So, what I suggest is: a. You do NOT need to use File | Enable Internet Access at all since your router does NOT support UPnP. So, since you have already enabled it, please disable it using File | Disable Internet Access b. Please do be kind enough to follow the instructions here to create a port forwarding rule, in your router, and to ISY: http://www.universal-devices.com/mwiki/ ... PnP_Router And, yes, you can have many simultaneous HTTP/HTTPS connections to your ISY. With kind regards, Michel

Hi Ken, Please try using httpS://your.isy.ip.address on your MAC and let us know if you are still experiencing the same issue. On PC, the source of most of these issues is firewall software. With kind regards, Michel

Hi Nick, We are going to look into it and see if it's a trivial UI issue and, if so, it shall be fixed. Otherwise we will have to leave it for the next cycle. someguy, that was quite funny! apostolakis, hopefully as we are currently working on it! With kind regards, Michel

Hi kingwr, The PLM stores the link records for everything that has been linked to it + all the scenes and devices within those scenes. With kind regards, Michel

Hi guy! The problem is not the number of nodes in ISY but the total number of links in the PLM which is doubled. You can do almost anything you can do with the Admin Console through the JSDK. You can add/remove/move devices and change the scene settings. You can get status updates when a device status changes. You cannot copy links because ISY is going to think it's a PLM replacement and then replace all the links to the original PLM with the new one. I really do not think you would want to take this route. If you can explain in a little more detail what you want accomplished (above and beyond making use of something that might be useless otherwise), I might have better suggestions! With kind regards, Michel Thank you.

Hi Brian, I tried your procedure which is equal to the procedure I found on the SmartHome website and still I cannot get the sub button to turn off the load. Factory reset did not help and still the memory locations are equal to what ISY does. There must be something we are missing and I suspect it's KPL firmware related. Would you be kind enough to: 1. Go to Tools | Diagnostics | Show Device Links Table and choose one of the KPLs that work 2. Use 0x02A0 for the Start Address and 0x0252 for the End Address. Click on Save and rename it to OL_RR.belias.xml 3. Click on Start again, choose your KPL, and this time choose 0x0248 for both Start/End Addresses. Click on Save and rename it to ON.belias.xml 4. Click on Start again, choose your KPL, and this time choose 0x0251 for both Start/End Addresses. Click on Save and rename it to OFF.belias.xml Once done, please send me the files to tech@universal-devices.com. Thanks so very much in advance. With kind regards, Michel

Hello all, Thank you for your support in helping us go through the alpha and beta stages of 2.7.8 and above. With the release of 2.7.15, we feel that we have an extremely stable system and we are entering a code freeze cycle of 10 days during which time no changes are made to the system unless absolutely critical. If no critical bugs are found, this release shall be our official release. As such, we would appreciate your help on ensuring that your system behaves as it should, it's stable, and you are happy with it! Please review the list of fixed bug and enhancements here: viewtopic.php?p=6475 Instructions 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip a. ISY 26 - http://www.universal-devices.com/update ... nsteon.zip b. ISY 99 - http://www.universal-devices.com/update ... nsteon.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.7.15 - applet f. http://www.universal-devices.com/99i/2.7.15/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 9. General instructions (especially for adding V2 thermostats) for the new features in 2.7.7+ can be found here: viewtopic.php?p=27368 Upgrading from 2.7.8 through 2.7.10 Upon reboot, ISY tries to migrate all configuration files to release 2.7.15 levels. This said, however, in the case of KeypadLincs, the following settings shall be lost (ISY will be out of synch with your devices) for those KPLs that were setup/configured in 2.7.8 or 2.7.9: a. Button toggle mode b. Button backlight c. Button groupings (in scenes or otherwise) d. Button mutual exclusivity As such, if you have setup any KPLs in 2.7.8 or 2.7.9, it's best to remove them from ISY, do a factory reset on them, add them back and reconfigure them. Alternatively - and you have not made massive changes using 2.7.8/9, you can restore your 2.7.7 backup (File | Restore ISY) and let ISY migrate everything. Thanks so very much for your help and support. With kind regards, Michel

Hi guy, Unfortunately you cannot for a variety of reasons the most important of which is the total number of PLM links it requires to have both of them synch with one another. If you just want to be notified of the changes on your computer, you can easily use the freely available JSDK which publishes all the changes to your computer instantaneously. With kind regards, Michel

Hi Brian, Would you be kind enough to post the procedure you are using to program this behavior manually? Thanks and with kind regards, Michel

Hi MarkJames, I am so very sorry to hear about the health issues. I hope all is well and everyone is healthy. 4428 tells me that the PLM has gone haywire ... basically, there's no way that the PLM can hold more than 2000 links and thus it's probably restarting at the top every time it reaches the end. What I recommend is for you to unplug your PLM, give it a little rest (maybe a minute or so), plug it back in and do the count again. Restoring KPLs, no matter how many times, should only overwrite the records for which there was a link; i.e. it simply updates the previous links if they exist, adds new ones if they don't, and removes those that no longer exist. Once you are done with the reboot and if your count is still high, I recommend doing a Restore Modem ... but, since I suspect your PLM is defective, I am afraid your PLM may die in the process. So, let's do the count first and then we'll decide what to do next. With kind regards, Michel

Hi MarkJames, Long time no see! For you to see the status of your motion sensor in ISY, there has to be 3 link records in the PLM for each node of the sensor. The first thing I would do is to do a count on PLM links (Tools | Diagnostics | Show PLM Links table). It might be that you have reached the maximum number of links supported by the PLM. If the PLM link count is low, then the next thing is to restore your MS. If that does not work, then I think it would be time for a new MS. All the above assumes that your MS is near an AccessPoint. With kind regards, Michel

Hello nickoonce, Unfortunately not. You can use the Network Module in addition to Global Caché GC100 to effectuate a change in your pool pump but currently we do not have support for bidirectional streams. With kind regards, Michel

Hi Brian, No, the relay does not turn off. Can you please try the same sequence on your 6 button KPL and let me know if it works. If so, please send me the manual steps you followed. I am not sure what this is related to but the memory locations are precisely the same as what ISY sets them. Perhaps there are some variables that are used internally and we do not know about. With kind regards, Michel

HI ryarber, Excellent idea! Thanks so very much and with kind regards, Michel

Hi mitch236, I think you may want to use a range (i.e. time is from 4:00 to 4:30) otherwise at 4:01 (and some grace period) your programs becomes false. With kind regards, Michel

Hi Brian, You are not missing anything and I appreciate your persistence simply because it will make our product better. I did test again with our KPL relay 5 button and it simply does not work even when I do it manually. The memory locations set the same way as ISY and confirm the previous understanding. Do you have 6 button or 8 button KPLs? With kind regards, Michel

Hi Doug, Please contact our tech support team and we'll help you out: http://www.universal-devices.com/contact.htm 818-631-0333 With kind regards, Michel

Hi Brian, The problem is that when you do the manual programming, the KPL does precisely what ISY does: instead of OFF it uses a very low on level. With kind regards, Michel