Michel Kohanim

Hi keribi, Release 2.6.8 should be out shortly ( although it's been quite a long time). In the meantime, would you be kind enough to check your logs and let me know if you see any errors. And, if so, could you provide me with the error numbers? With kind regards, Michel

Hello eddyk, Please go to Help->About and make sure you have release 2.6.7. Then, please clear your Java cache. Please note that all your browser windows must be closed for Java cache to be cleared: 1. Control Panel->Java 2. Settings Button 3. Delete Files With kind regards, Michel

Hi Gary, Thanks so very much for your vote of confidence! Hardware enhancements are currently isolated to IR out/expander which we are currently testing as well as a serial expander which allows you to communicate with more serial devices. For the meter, you need their network enabled devices. That's about it. With kind regards, Michel

Hi Dave, It would be very difficult to diagnose the problem this way. Would it be possible to login to your system remotely? Also, please note that non-toggle either sends on or off all the time. Furthermore, mutual exclusive buttons do not work if you have them controlled by other switches. With kind regards, Michel

Hi AnthemAVM, The protocol supports temperature readings for different zones but we've yet to see values for any zones except zone 1. With kind regards, Michel

Hi Paul, We are trying to support the same features in 99i and thus you won't need 99i PRO. Here are the features that will be supported shortly (there will be a flat fee for each feature): 1. Integration of programs with Weather Information (temp, humidity, gust, wind direction, rain today, etc.) 2. Integration with Brultech energy meters 3. Integration with Open DR (where available) to sense and respond to load level on the grid 4. Calling a URL from the programs 5. Customizable home pages ... and many more With kind regards, I'm trying to decide if I really need the 99 PRO, or if the 99i/26 would be good enough. Could you by any chance give me an idea of what these major improvements are going to be? I'm really looking forward to getting an ISY, but don't want to pay the big bucks for the PRO if I don't need to. Thanks!

Hi Joe, Long time no see! A simpler solution would be to use click for Program On and Double click for Program Off. This way, you would be using the same switch and you would never have to guess whether or not the program is running. With kind regards, Michel

Hi All, These are excellent requirements which shall (must) be implemented. The only issue we keep fighting with is enhancements (things we can do without for now) vs. bug fixes (such as new INSTEON devices/i2/SHN products/...). I do sincerely appreciate your patience. With kind regards, Michel

Hello jwagner010, You raise a good point and one which we have pondered a lot: should ISY act as a dynamic dns (be cognizant of ISP IP changes) or should it let the router take care of this. We arrived at the conclusion that ISY is simply a client to your router and having a free dynamic DNS account will surely be the best way of handling this. Now, on the ISY side, when ISY gets a different IP address, it actually does try to reconfigure the router. If ISY is not successful, then you will not have remote access. Perhaps we can have ISY keep trying it but, in most cases, UPnP traffic causes some of the routers to start behaving erratically (especially Verizon/Actiontec). With kind regards, Michel

Hi Rob, In most cases, DNS resolution is simply forwarded by the router. In some cases - and especially if you have static IP address assigned to your ISY - your router may refuse relaying DNS requests. Please look for a DNS Relay settings in your router. With kind regards, Michel

Hello jamesx0, The reason is that ISY tries failing requests three times. So, you got -2 the first time and the second time actually we got a garbled message. With kind regards, Michel Is there a reason that the setpoint defaults to 23 when there is an error?

Hello jamesx0, I think the first line is the clue: -2 means device communications error. Therefore, ISY is having difficulties querying the thermostat. If this happens a lot, then I would suspect that your AccessPoint is not close enough to your thermostat. With kind regards, Michel

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.