Michel Kohanim

Hi, We have at least 3 other ISYers developing iPhone applications. They are all waiting for our REST interface which should be out shortly (few days). So, you will all have multiple applications to choose from! With kind regards, Michel

Hi oktane, Setting up ELK is quite easy: 1. here's the documentation: http://forum.universal-devices.com/viewtopic.php?t=634 2. here's our ELK forum: http://forum.universal-devices.com/viewforum.php?f=17 I am sure PowerHome adds some more flexibility ( I'm one of Dave's fans ). The issue is that ISY has never been tested with multiple PLMs and, as such, we wouldn't be able to provide you with accurate information. ISY has a running tally of group numbers that may be used. So, it starts from 17 (PLMs have had some issues with lower group numbers) and goes all the way to 254 (255 is all on). With kind regards, Michel

Hello Baypointe, Thanks so very much. This is a known bug and it shall be fixed. With kind regards, Michel

AD8BC, Thanks for the update. Would you be kind enough to check the version of your PLM (Tools->Diagnostics->PLM Status/Info). With kind regards, Michel

Hello CompKing, I totally agree with you. The main issue is that we have nothing to do with the error detection/correction (the PLM is doing all that) and, as such, we can only report back what the PLM sends back to us. Would you be kind enough to do one more test? Would you move your Access Point back to where it was originally, reboot your thermostat, and retry? With kind regards, Michel By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between)

Hi Joe, Was it something like: -2 15 15 If so, and if you have motion sensors, if this happens next time, please take the batteries out of your motion sensors and let me know if it helps. With kind regards, Michel

Oktane, I am afraid you are reaching the limits of our expertise with multiple PLMs on the same network. May I humbly ask why you need ELK-PLM? If you have M1XEP, then you can integrate with ISY seamlessly (bi-directional). As far as PowerHome, I know it's an excellent product but I am not certain how these two should work together. Do you have a specific use case in mind? ISY was designed in such a way that you do NOT have to know about links, group numbers, removing/adding links, etc. As such, it would be very difficult for ISY to act like a PowerHome where you can selectively decide what links should be there and what links should not: The linkages are captured and presented by nodes in the tree. I am so very sorry I cannot be of further assistance, With kind regards, Michel

Hello upstatemike, Something very curious and coincidental. I just had a customer with the same exact issue. I had him count the links in the PLM and it was 416; we added more scenes (and devices in the scenes) but the number of links did NOT change. The scary part is that this was PLM 63 which was supposed to have the extended memory but it did not (or it didn't know that it did). So, at the moment, your theory seems to be very plausible. With kind regards, Michel

Mr. Sullivan, Just wanted to let you know that this was indeed a bug and it has already been fixed. Thanks so very much for letting us know. With kind regards, Michel

Hi Rich, Unfortunately, all new capabilities were put on hold while we are getting INSTEON issues resolved. With kind regards, Michel

Zellarman, Thanks for the update. I just wished SH would not change the protocol on existing devices. I am hoping for a day day when we'll have a stable enough protocol and all we have to change would be adding support for new devices. With kind regards, Michel

Hi burakk, Do you have any motion sensors? The next time this happens, please do be kind enough to take the battery out of all your motion sensors and let me know if it helps. With kind regards, Michel

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