Michel Kohanim

upstatemike, I thought we were going to test this BEFORE restoring the PLM. The main reason was to see whether or not the number of links in the PLM have any impact. Would you be kind enough to factory reset your OLD PLM, reboot your ISY with the old plm, link the switch into it, and let me know? With kind regards, Michel

Excellent. In this case, your ports are indeed 80 and 443. What happens if you try File->Enable Internet Access in the Admin Console? With kind regards, Michel

bbb2008, 2.1??? Would you please go to Help->About and let me know the number after v. ? Number is 818-631-0333. We do not have phone support over the weekends but we can call you tomorrow. With kind regards, Michel

Hello ggodding, Yes, I have seen this problem very many times. In most cases, factory reset fixes this issue but in some cases only a replacement will fix it. i2 problems do exacerbate the issue. My first question is: what version of ISY firmware do you have? If 2.6.8 and below, then I strongly recommend getting a replacement. If not, then I recommend the following: 1. Remove your RL from ISY 2. Do a factory reset on it 3. Link Management -> Advanced Options -> i1 Only Mode 4. Add back the RL to ISY 5. Link Management -> Advanced Options -> Automatic 6. Try adding it to a scene With kind regards, Michel

Hello bbb2008, What version of ISY firmware do you have? I think it would be best to call our tech support to get this situation resolved. With kind regards, Michel

Hello upstatemike, Yes, I know precisely what you mean. Please do keep us posted. With kind regards, Michel

upstatemike, Wow, this is quite interesting and I cannot really discount it mostly because you have one of the larger installations. Can you do me a huge favor? 1. Factory reset your old PLM 2. Reboot your ISY with the old PLM 3. Add one of the troubled switches 4. Let me know if it reports the status If it does, then your theory is correct and needs further investigation. Also, when you get the newest PLM, please perform the same test as above before restoring it. Thanks so very much, With kind regards, Michel

Hi upstatemike, In 2.6.13 and above, and due to some bugs (no ID Req), we are forcing CL/RL additions to be done by address. That's why you do not have to press any of the buttons. You have followed the correct procedure. The only reason ISY would try to remove links to devices is if those links are in ISY's table. The only possibilities when you would have links in ISY links table but not represented in scenes: 1. ISY bug (you had those links, removed them, but ISY didn't remove them from the links table) 2. Import ... you imported the links for your original CL and they have lived on Now, as far as your new CL not controlling anything any longer, would you be kind enough to click on any of the buttons and make sure they are indeed controllers for the scene (check the tree to your right). If you have an extra button, would you be kind enough to add it to a test scene? And, finally, during the programming process, did you get any other failure messages which might have indicated failed communications to any of the other devices? With kind regards, Michel

upstatemike, Thanks so very much for the update. Please do keep me posted. This has been going on long enough and we have to get to the bottom of it as soon as possible. One question that I keep wanting to ask and I keep forgetting: Did ANYTHING change in your environment before you started experiencing these issues? Anything at all? Or, was this a problem from the get go? With kind regards, Michel

Hi Zellarman, The new KPLs, SWLs, ALs, and LLs are all i2 (not a comprehensive list). And, yes, they might interfere with existing installations especially if: 1. you use SignaLincs 2. you are programming them via ISY With kind regards, Michel

Hello CompKing, Thanks so very much for the update. I shall have it checked out again though I have not been able to reproduce it under 2.6.13. If another query resolves this, then perhaps we can also move the AccessPoint close to the thermostat to see if it helps the issue. With kind regards, Michel I confirm this DOES impact my programs in 2.6.13 (as confirmed with Help -> About) My Product is ISY99/IR Pro (1050) The zero value both triggers a program, shows up in Admin Console device status, and under regular device status on the web interface. Keep in mind I am running in Celcius, not Farenheit. It is intermittent, and a subsequent query of the thermostat will typically clear up the zero value to the proper room temperature.

Hello Mr. Sullivan, I will check into this and, if a bug, we'll add it to our bugs. If not, I will respond back with the cause. With kind regards, Michel

Hi George, Yes. We are slowly starting to work on it again. With kind regards, Michel

Hello bbb2008, Please go to Help->About and check My URL. If you do not see :port at the end of the URL, then the port is 80. Otherwise, the port will be indicated. With kind regards, Michel

Hello bbb2008, Please go to Help->About and check My URL. If you do not see :port at the end of the URL, then the port is 80. Otherwise, the port will be indicated. With kind regards, Michel

Hi Joe, Boy, you do get the strangest problems. Was this Error and Mem blinking or just MEM? If so, do you have screen capture of the error? I checked our error codes and we do not have I/O error messages. Are you talking about "-2" errors? With kind regards, Michel

Hello RLIKWARTZ, Are you still having intermittent issues with your older devices after going through all this? With kind regards, Michel

upstatemike, Apologies for the inconvenience. I will have to check into the PLM links table issue as it seems to be a bug. Indeed, there can only be 4 issues contributing to this problem: 1. Noise ... not ruled out yet 2. i2 .... which is ruled out (because you are using old switches) 3. PLM ... not ruled out yet 4. ISY ... not ruled out yet So, may I humbly suggest actually replacing the PLM? We do have a spare one that I can send you for your testing purposes. With kind regards, Michel

Hi RichTJ99, Yes and yes. If you really want to do it, make sure you use scenes. With kind regards, Michel

CompKing! I just had to post because you just made my day .... after a LOOOONG day, I needed this laugh! LOL. With kind regards, Michel

Hello Bill, Thanks so very much for the update. This is not good at all. Has anything else changed in your environment? A new computer, an older monitor, anything at all. I really do not think the difference between version would cause such drastic problems unless the PLM is not handling the i2 commands (and is becoming deaf/dumb). This is very possible if you have PLMs version 58 and below. Please do be kind enough to keep me posted. With kind regards, Michel

Hi Zellarman, All programs refer to addresses of devices and NOT names. So, even if you have renamed and moved them to different scenes, they should automatically be reflected. This said, however, if you have replaced a device with a new device, you will see an Unknown in the programs referring to a device that no longer exists. With kind regards, Michel

Hello RLIKWARTZ, Are these devices new? Specifically, are they the SWLs and LampLincs? With kind regards, Michel

Hi Rich, Yes, absolutely! With kind regards, Michel

Hello Zellarman, Were you aware that SignaLincs do not support i2? Have you recently added new i2 devices? With kind regards, Michel