Michel Kohanim

Hi Robert, Motion Sensors and thermostats do NOT work in i1 mode. Based on information from SH, we are going to make the default i1 except for motion sensors and thermostats. As such, please do be kind enough to wait for our next drop (in a few days). With kind regards, Michel

Hi David, Apologies for the inconvenience. This is indeed possible (IRLinc button and KPL button in the same scene both as controllers). Please go to Tools->Diagnostics->Event Viewer, choose level 2, and the retry. In the event viewer, you will see WHY the request failed (i.e. which device is the culprit). Please keep me posted. With kind regards, Michel

Hello Jim, Is your SmartHome going through the Internet (i.e. https://your.external.ip.address)? If so, can you access your ISY using the remote URL via a browser on your computer? If not, is your SmartHome using your WiFi? With kind regards, Michel

Hello upstatemike, SH has been quite responsive to the issues as we have reported them. As such, they have an updated PLM that, if you don't mind, I would like you to test. If so, please forward me your address to tech@universal-devices.com. With kind regards, Michel

aaronb, This usually happens if your 10 lights have residue slave links to the other light OR if you have ELK. If you do NOT have ELK, please try File->Restore Devices. If you do have ELK, please make sure the Future bits are set. With kind regards, Michel With kind regards, Michel Not sure it is the upgrade, but my 10 lights turn off whenever someone turns on or off another light. Anyone else seeing funky behavior?

Hi Jim, I am not sure what's causing this issue as we cannot reproduce it but would love to know more so that, perhaps, there's a bug that we have to fix. To change the HTTP/S timeout, telnet to your ISY, login, and issue CWT. With kind regards, Michel quote="Stowaway"]Michel - Thanks for the quick response... Where would I make this change, and why could I connenct OK once and then nothing but timeouts...?

HI AD8BC, Please do not install 2.6.13 as we are going to have (hopefully the final) 2.6.14 where everything reverts to i1 except motion sensors and thermostats. With kind regards, Michel

Hi Jim, Have you tried increasing the timeout on your ISY? With kind regards, Michel

upstatemike, Thanks so very much for the update. This is very good! As far as your 3rd assumption, and in the original setup, were you getting [uNKNOWN] m n where m and n are numbers? If so, then you are 100% correct. If not, then I would think it's #2. I am going to forward this thread to SH. Thanks again so very much, With kind regards, Michel

Hi Steve, These are not unknown devices. They are unknown messages. It seems as if either the PLM or the device itself is responding with NACK and chopped off messages. This is all related to i2 messages (see the previous and following commands). I spoke with Mr. Steve Lee at SH yesterday. He is going to confirm whether or not we can move everything back to i1 (except the motion sensor) as these problems are simply not going away! With kind regards, Michel

Hello AD8BC, Thanks so very much. I do think your PLM does have something to do with what you are experiencing since i2 was not actively supported in PLMs before 68. One of the major problems with 52 PLMs is that they lockup given a lot of traffic. So, you had the same exact problems with i1 only mode? With kind regards, Michel

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