Michel Kohanim

Hi ski2020, Good question. As I mentioned before, there's absolutely nothing in the logs/event viewer that says ISY was the culprit. At this point it's either the thermostat or something else that was linked to the thermostat before. With kind regards, Michel

Hi Rich, That's what I have been wondering too! Our contact at FYP is no longer there. I just sent an email to the only email available at the site. I had sent another email last week but never heard back. With kind regards, Michel

Teken, As you might recall, I personally connected remotely to your ISY via HTTPS and using my Admin Console on both Windows 7 and Windows Vista. I do not recall ever proving or disproving you were using SSLv3. How did we arrive at this conclusion? Would you please forward and/or paste any records arriving at this conclusion? My records show our last email correspondence, on Wed 9/19/2012 7:17 PM, ended with you stating: ***** Hello, I have no problem accessing the ISY via the provided link. ***** So, are you still having the same problem? Also, if you have gone back to 3.2.6, have you restored your backup? With kind regards, Michel

Teken, A few points of clarification: 1. ISY does not need Java for command and control. You can use the AJAX interface and a host of other mobile/PC applications 2. For configuration, ISY requires Java. Java was chosen precisely because of its cross-platform support. HTML/AJAX require constant polling to get status updates. For configuration purposes, HTML/AJAX is not a good solution 3. I am not sure in which environments Java is not supported 4. In 3.3.2 instructions, it's explicitly stated that we had to remove SSL v2 Support because of security concerns. We cannot sacrifice security for ease of access 5. Since this problem is isolated to HTTPS/Admin Console and if you do not care about security, you are welcome to forward to the HTTP port. Ultimately, it's your system's security and you are the boss in that respect I have to stress again that the problem is accessing ISY, through the Admin Console (or Dashboard) using HTTPS. The problem is NOT there for HTTP nor is it there for the regular HTML/AJAX interface. Thank you for your feedback. With kind regards, Michel

Teken, We would be delighted to refund you for your ISY so that you can continue enjoying your SmartLinc. With kind regards, Michel

Hi ski2020, Here's your own quote: With kind regards, Michel

Hello Bill, I am so very sorry to hear about the problems you have been having. We did find a problem with KPL v40 and sub buttons which we have put a workaround in our next release to be out by Friday. If you don't mind, please wait for that release, remove your KPL from ISY, add it back, test and let us know what you find. Again, sincere apologies. With kind regards, Michel

Hello bconen, Do you have 99 or 994? If 99: 1. Telnet to your ISY 2. Login 3. Type: RF /CONF/UD.DCF Hello RLIKWARTZ, Please right mouse click | Diagnostics | Query Insteon Engine. With kind regards, Michel

Hi ski2020, If you see System, then it's coming from the device itself. The only times ISY is doing something is when you see Program OR Web instead of System. With kind regards, Michel

Hello GregE: viewtopic.php?f=27&t=8886&start=30 With kind regards, Michel

Hello brookbphx, Yet another I2CS anomaly for which we had to put yet another workaround. Our next build should be available by Friday. With kind regards, Michel

Hello brookbphx, We added a workaround for now which should be available in our next build by Friday this week. With kind regards, Michel

Hi Teken, No, we cannot support this feature as it causes major synchronization problems and additional support issues. With kind regards, Michel

Hello all, The only way that we got this to work was: 1. Make sure you are on automatic mode 2. Factory reset the Load Controller 3. Add it to ISY ... it may fail 4. If you see a node for the controller, right mouse click and then choose Diagnostics | Query Insteon Engine With kind regards, Michel

Thank you all. Verified and it shall be fixed for our next beta to be out shortly. With kind regards, Michel

Hello brookbphx, Thanks so very much. It would be great if we can get the output of the Event Viewer. Unfortunately, we cannot reproduce the problem here and thus the need to see the traffic. With kind regards, Michel

Hello brookbphx, This must be quite frustrating. May I humbly request a simple test? If possible at all: 1. Remove the KPL from ISY 2. Do a factory reset on it 3. Make a scene with all the KPL buttons in that scene as follows - Load: responder - Others: controllers 4. For each controller, assign varying degrees of on level for the load (including off). i.e. start from button B all the way to H Please do let me know what you get. With kind regards, Michel

Hello GregE, Did you use Start Linking method? Also, what's your ISY's firmware version? With kind regards, Michel

Hello RLIKWARTZ, Apparently it's only supported on a firmware that has not yet been released to the public and, unfortunately, we do not really know when it would. With kind regards, Michel

Hi LeeG, [quote="LeeG" F. why the Load Controller NAKs otherwise correct commands some of the time is an unknown This is precisely the problem that had been reported before (not on the forum) and, at the moment, we think it's the firmware in load controller. Thanks and with kind regards, Michel

Hello klum, Unfortunately not. With kind regards, Michel

Hello Exten, From my experience, I can tell you that Zigbee is one of those protocols that is so fragmented with different profiles that it would be quite improbably for anyone to figure out what can or cannot be done. For instance, RCS has its own proprietary protocol over Zigbee as does Brultech. Then, there's Zigbee Home Automation Profile which is similar to INSTEON but you will have a very hard time finding interoperable devices. And, finally, there's SEP which is designed to communicate with Smart Grid meters. As such - and if I understand you correctly - our plans are modest in nature and, unfortunately, nothing generic is planned. With kind regards, Michel

Hello ski2020, It's quite unlikely that ISY would send a command to a device on its own. What do the logs show at the time that you experienced a phantom command? With kind regards, Michel

Hi ski2020, As far as I remember, the byte you are referring to is the flag (i.e. what type of command): 07 = Standard Direct (something is sending a signal to the PLM) 27 = Standard Direct Ack (PLM sent something to a device and now the device is Acking it) With kind regards, Michel

Hi Exten, I do want to understand what other Zigbee devices you have beyond Brultech (which we support). With kind regards, Michel