Michel Kohanim

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

jellis, Please do NOT factory reset ISY as it will not help with anything. There's a known bug with 3.1.5 and 3.1.6 with respect to email notifications. Can you tell me what is your firmware version? With kind regards, Michel

Hello jkraus, No, it does not. It's on our plate of things to do right after ELK. With kind regards, Michel

Hello Pazium, I am not sure I understand the issue. Your corporate firewall does not let you get to ISY? If so, I do not think the choice of dyanmic dns provider is going to be much help. With kind regards, Michel

Hi Tim, thank you. The problem is that you are not the only one with this specific problem. We are working with SmartHome to figure out the root cause ... hopefully soon! In the meantime, please do keep us posted and we'll let you know as soon as we find out the root cause. With kind regards, Michel

Hi Tim, Thank you. Unfortunately I think you have a defective Motion Sensor. Before requesting for a new one, we should do one more test: 1. Put your motion sensor in programming mode 2. Right mouse click on the node representing your motion sensor and then choose Restore Device Please do keep us posted. With kind regards, Michel

Hello gakran, As LeeG indicated, we do not recommend factory reset as it may hide the underlying issue and it usually does not fix anything. Program export only exports programs and not all your configuration. You need to have regular backup of your system to ensure that the system as a whole can be reprogrammed. As far as X10 I/6, these are X10 messages being sent or received. If you still have your X10 controller, you might want to remove it and see if you still get those messages. There's no way to disable X10 messages that are received. With kind regards, Michel

Hello Benoit, Sincere apologies. The problem was 2.8.16 and ELK and then 3.1.6 and network connections. Please do be kind enough to send your Error Log to support@universal-devices.com . With kind regards, Michel

Hi ergodic and LeeG, This error has two causes: 1. Device not responding even after 3 retries 2. The device sends a NACK As far as I know - and as LeeG mentioned - ISY does not sending anything to motion sensors at all unless you are programming it. With kind regards, Michel

Hi Chad, I do not see your entry in the Wiki ... has it been already added? As far as the Zip file, I was referring to the Wiki. Thanks again and with kind regards, Michel

Hello elvisimprsntr, Thanks so very much. It shall be taken care of. Hi Scott, thank you; your logs were instrumental in finding the bug. Hi Matt, 3.1.6 does indeed have an issue with ECM1240: it does not poll! We should have 3.1.7 out shortly hopefully by the end of the week at the latest. With kind regards, Michel

Hello captfisk, The first thing we need to do is to make sure you are actually talking to ISY. Can you please login to your laptop and then go to http://your.isy.ip.address/desc ? If you do not get anything and/or if the result is not XML, then - and in all likelihood - the IP address for ISY was changed and you are connecting to something else. If your laptop is Windows based - and if you have 2.8.16 installed - you can get to ISY by typing http://isy OR you can go to http://www.universal-devices.com/99i provided that you are local to ISY. With kind regards, Michel