Michel Kohanim

Hi Tim, Thanks so very much for the update. When you link the motion sensor directly to your device, does it control the device. I am having some intermittent problems with a new motion sensor as well. We do need to get to the bottom of this since it seems to be more prevalent that I had expected. With kind regards, Michel

Hello Elvis, We were going to have 3.1.7 this morning but found a little bug which seems to be eating up buffers especially when you use Chrome. As such, I do not think we are going to have 3.1.7 released this weekend. Sincere apologies. With kind regards, Michel

Hello Steigs, The best method for factory resetting ISY is [ulr=http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON]outlined here[/url]. You will also have to factory reset your PLM at the minimum and all your devices if necessary. With kind regards, Michel

Hello rmlinnovator, Unfortunately we do not have any plans. This said, SmartHome has regular training sessions all of which include training on ISY as well. With kind regards, Michel

Hello Karl, I do apologize for the inconvenience. There seems to be some network issues here which would be best solved over the phone. Please do be kind enough to contact our tech support team. With kind regards, Michel

mitch236, Let me chime in. As LeeG suggested, you cannot communicate with MorningLinc UNLESS there's a link in the database you won't be able to communicate with MorningLinc from ISY. As such, please do be kind enough to follow the instruction as provided by LeeG and retry. With kind regards, Michel

Hello remedy1234, I still have not heard back from SmartHome ... the thing is that I am not even sure a new Motion Sensor will fix this issue. I finally got the new Motion Sensor and I cannot reproduce any of these problems so it's quite hard to decide what the issue is. Can you tell me the exact procedure you followed to add the Motion Sensor? Did you use the drop down and made sure your Motion Sensor is in programming mode? With kind regards, Michel

Hello buzzhazzard, Thanks for the update. Yes, you can still control your devices and your programs should work. And, yes, when you get a new PLM, all you have to do is to do a File | Restore Modem (PLM) and you should be done. One more question: have you ever done File | Remove Modem? If so, that explains all the issues because this function removes all the links from your PLM and restore will basically restore nothing. With kind regards, Michel

Hi Joe, Thanks so very much for the steps to reproduce the issue ... it did help: the problem is in the UI and not 3.1.6 firmware. This should be fixed in 3.1.7 wherein we basically had to massively change our networking framework. With kind regards, Michel

Hello kevinohara80, This is excellent! Thanks so very much for sharing ... now if we could only get a less expensive quote from Salesforce.com! With kind regards, Michel

Hello buzzhazzard, I am so very sorry but I think the PLM might have lost all its links (this does happen occasionally). What you want to do is to go to Tools | Diagnostics | Show PLM Link table, click on start, and when completed please click on the count button. If the number is 0 or low, then the PLM has lost all its links and I do recommend replacing it. In the meantime, you could try File | Restore Modem. With kind regards, Michel

Thanks junkycosmos. Looking forward to the update. With kind regards, Michel

Hello buzzhazard, Thank you. Do you know what firewall software you have on your computers? With kind regards, Michel

Hi junkycosmos, Thank you. Yes, you do need to choose the device type from the list. The major problem with those -2s is that, I am assuming, they are being initiated by the Motion Sensor and they should NOT since Motion Sensors should be passive. I think this might be contributing to battery life because it seems that the motion sensor is not going to sleep. With kind regards, Michel

Hello buzzhazzard, May I assume that the programs in ISY DO know the correct/current status of the devices? If so, the problem is firewall related or interactions between the computer and ISY. With kind regards, Michel

Hello junkycosmos, ISY does not persist the state of devices. So, it's normal for you not to see the low bat state since Motion Sensor only sends when low bat is sensed (to save whatever remains of the battery). The -2s are troublesome for Motion Sensors since they should not be responders. Would it be possible to remove one from ISY and then add it back in and see if you still get the persistent -2s? With kind regards, Michel

Hi C Martin, 0 decimal points. All numbers are wholes. With kind regards, Michel

Hello kaisersoze, Unfortunately not. With kind regards, Michel

Hello jsp, What type of firewall do you have and do you have Flash installed. There seem to have been a conflict between Flash and Java at some point but it has not been verified. With kind regards, Michel

Hello junkycosmos, Thanks so very much for the update. The status of low bat gets cleared in two cases: 1. Querying that node 2. Power cycling ISY May I assume that neither of the above is the case in your situation? With kind regards, Michel

CJVann, Please upgrade to our official release (2.8.16). It's very difficult to troubleshoot a very old beta. With kind regards, Michel

Hello gakran, Thanks so very much for the update. We will look into this issue before sending 3.1.7 out. With kind regards, Michel

Hello all, I am quite wary of giving ETAs simply because we have not been able to meet our own expectations vis-a-vis ELK. On top of that, we have to make sure that we have a stable system again. I am hoping 3.1.7 to be out this week, then ELK, and then support for additional INSTEON devices. With kind regards, Michel

Thanks LeeG ! With kind regards, Michel

Hi Wayne, I have seen this many times with bad or going bad PLMs. With kind regards, Michel