Michel Kohanim

Hi Paul, We have experienced many more problems especially with 1.5: Christmas effect: random/ghost like activation of devices linked to it Missing link effect: random corruption of the link database With kind regards, Michel

Hello Paul, One more question: are you using Start Linking method or Add a New INSTEON Device? In either case, would you try Add a New INSTEON Device and choose the device type (KPL) from the drop down? If this works, then we know the problem: they are not responding with IDReq (which was quite prevalent in 1.5 and 1.6 and thus the introduction of 1.65 in a matter of weeks!). With kind regards, Michel

Hi Joe, No, I never received your email. I am so glad that it's all working to your satisfaction and I want to thank you for providing us with an interim solution. With kind regards, Michel

Hello dougos2, ETA is Monday but we keep pushing it out for last minute enhancements (whatever we can put in) and YES the fix for blank current state is in there. With kind regards, Michel

Hi Brian, Apologies for the inconvenience and thanks so very much for bringing this to our attention: due to massive changes in both the GUI and the firmware, you will have to migrate from 2.6.4 to 2.6.5 and then to 2.6.7. With kind regards, Michel

Hello keribi, I don't think it's something that everyone experiences. Did you enable POP/SMTP on your Google Account? With kind regards, Michel

Hi keribi, It might have to do with the "from" field which we have added in 2.6.8 (to be out shortly). With kind regards, Michel

Doug, Thanks SO very much for this information as it makes our theory more credible. Thanks again and with kind regards, Michel

Hi huddadudda, Unfortunately, this is a known issue: LED do not know anything about status except for on or off. What you might want to do is to create another scene, with just that KPL button as responder, and checks the status of your lamplinc and then turn the new scene off when the status is off. With kind regards, Michel

Hi Walter, It all depends on what you used in your MX700; if they are the same NEC codes as the one for the Credit Card remote, then (at least some of them) should work. If not, then I doubt you will confuse any IRLinc as it's all about the NEC codes. With kind regards, Michel

Hi Walter, It all depends on what you used in your MX700; if they are the same NEC codes as the one for the Credit Card remote, then (at least some of them) should work. If not, then I doubt you will confuse any IRLinc as it's all about the NEC codes. With kind regards, Michel

Hi sloop, So far, we have not had any problems with IE/Java/Win64. With kind regards, Michel

Hi Eug, This is quite strange and it can be explained only in two ways: 1. A bug in ISY 2. A defective RL Do you have this problem even if you factory reset your RL? Do you use Link Management->Link a RemoteLinc? With kind regards, Michel It was emailed to me when I was having a firmware update problem. Autodiscover. Hi Michel, I'm not sure what you mean by "master links for the RL", but for what it's worth, when readding the RL and explicitly stating the device type, as suggested by Darrell, it worked fine. I should also point out that the existing links were created directly on the devices, with no software intervention.

upstatemike, Yes, I agree. Let us see what we can do ... With kind regards, Michel This would certainly be helpful. Even the ability to just be able to see the unkown links would go a long way towards helping with troubleshooting.

shandelman, Please make sure you do not have any firewall software running. If you do, please find yours in http://forum.universal-devices.com/viewforum.php?f=3 and please do be kind to take the corrective measure as outlined therein. With kind regards, Michel

Hi sloop, There are some problems with Java/Firefox/Win64 which we have not yet been able to resolve! With kind regards, Michel

Hi Rob, I must confess that we have not really tested this scenario thoroughly enough to be able to definitively answer your question. This said, however, I can tell you the following: 1. ISY should withstand power failures and spikes on the power (from PLM) to up to 30 volts (normally, the PLM power supply is at 12 volts). Anything above that may damange ISY 2. ISY should be able to handle PLM connect/disconnects as long as it is itself connected to the power So, the only thing to be tested (and mostly in real life scenarios) is to see how the PLM really reacts after a power surge. I would sincerely appreciate any input you can give us. With kind regards, Michel Michel, what size/type power supply do you recommend? I would like to do this as well.

Hello Michael, Do you have Dynamic DNS? Have you considered assigning your ISY a static IP address (http://www.universal-devices.com/mwiki/ ... IP_Address)? With kind regards, Michel

Hi raypanic, ISY shows what the device returns for its version#. In most cases, this version number is NOT equal to the label put on the devices by SH. With kind regards, Michel

Hello Eug, The reason for seeing your RL buttons as responders is that, in all likelihood, the previous application did not create master links for the RL, in the other devices. Did this ever work? With kind regards, Michel It was emailed to me when I was having a firmware update problem. Autodiscover.

Hello RAldridge, The problem with the program not firing is indeed quite troubling and has to be investigated more. Can you provide us with more information? Now, null means that there was an error. In this case, the error is -10107. You can find the description of error codes at http://www.universal-devices.com/mwiki/ ... tem_Errors In short, it seems that someone was trying to access your system without providing the Userid and Password. With kind regards, Michel

jhimmel, To be 100% honest, we have that feature already there (90%) but we stopped mostly because any unsupervised (not system based) changes to the links means 100x the support calls and problem resolution scenarios. Unlike you and Eug, most ISYers are NOT experts in INSTEON links and what they mean and thus it's very difficult for us to include this feature. Perhaps we implement another solution which shows you "unknown links" and asks you what you want to do with them: keep/remove? This way, ISY can still be privy of what you are intending to do and keep track of the changes. With kind regards, Michel

Hi Rand, Yes, you are 100% correct. The only problem is that some of those new KPLs are i2 and some are 1/2 i2 neither of which we can currently support since except by firmware version, we have no way of knowing which one supports full i2 and which one 1/2 i2. Furthermore, after extensive i2 testing with Motion Sensor, RL, TimerLinc, we have come to the conclusion that it will take us (including SH) a lot longer before i2 commands can be used reliably. With kind regards, Michel

Hi Ray, Since we are very close to having an official release - and as Gary suggested - please hold off for now. With kind regards, Michel

Hi Bob, Are you specifically referring to local on level/ramp rate or those for a scene? If local, then the easiest way is to manually set them (we have an intermittent bug which we have not found yet). If you are talking about the scene on level/ramp rates, then there's surely something very wrong. You do not have to do factory reset on new devices. You do factory reset if and only if you think your device is not behaving as it should based on your scenes. Of course, we've had situations where brand new devices have had X10 addresses stored in them but the likelihood is low. With kind regards, Michel