Michel Kohanim

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

Hello Exten, There's a Digi gateway that does what you wish. This said, even that requires you to setup a PAN (just like you connect to WiFi). I am not sure how that would help us! With kind regards, Michel

Hi ski2020, Unfortunately (or fortunately) the this one is not related to the bug we fixed. If you look below ****** Fri 09/21/2012 12:06:03 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 27 6C 48 (48) Fri 09/21/2012 12:06:03 PM : [standard-Direct Ack][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Fri 09/21/2012 12:06:03 PM : [ 11 B5 F0 1] CLISPC 72 ****** Your thermostat is returning 48 Hex = 72 Decimal = 36 degrees (72/2). At this point, I think it's the thermostat itself unless something else changed the set point. With kind regards, Michel

Hello GuitarBuilder, We have been for a while now (since June of this year): ISY994i ZS Series: http://sales.universal-devices.com/util ... zs-series/ Our news: http://sales.universal-devices.com/news/ With kind regards, Michel

Hi Exten, ISY acts as a coordinator for the specific PAN (personal area network) that it has been configured for. And, as such, it cannot act as a router for any other type of traffic. ISY currently supports only ECM1240, UDI-EM3, and RCS thermostats. GreenEye is planned by no ETA yet. We do have plans for supporting more Zigbee devices but, unfortunately, we have not found any interest and most have proprietary protocols not publicly available. No, ISY is very much strong-typed; this means that it will only publish events for "known" devices (registered in ISY) and "known" events for those devices as described in our WSDK. ISY is very specialized and not generic. If you can tell me what other Zigbee devices you have on your network, then we'll figure out what's needed

Hi brookbphx, This same issue has been reported by others and the problem is that the device itself is i2cs but subsequent queries by ISY for engine version fail. As such - and as LeeG suggested - it's very important for us to see the contents of the event viewer. Furthermore, please try right mouse click | Diagnostics | Query Insteon Engine ... if this works, then the problem is as those reported by others. With kind regards, Michel

Hello tflores, ZS series is for SmartGrid communications; i.e. it can communicate with your SmartGrid meter. Ecobee and NEST both have proprietary protocols that are not public and thus cannot be supported. ZWave is coming along pretty well ... this said, if you want to use ZWave, you would have to replace the SmartGrid/Zigbee radio with a ZWave radio. You cannot have both. With kind regards, Michel

Hello homejones, Although there are not very many differences between 99i and 994i at the moment, but the additional memory in 994i provides for extended functionality and support. Whereas, with 99i, we will reach a time when we cannot add any more functionality (including INSTEON device support). The modules you wish to add are supported in 99i. So, if you are looking for a static installation whereby you are done after initial configuration, then 99i would be OK. If you have more grandeur plans, then may I humbly suggest 994? With kind regards, Michel

Hi Teken, Thank you. This should work with Admin Console as is. Also, I got your email and it worked properly from my Admin Console. I suspect something in the computer (perhaps firewall) is blocking https to ISY from Java. With kind regards, Michel

Hi , Just sent you an email. With kind regards, Michel

Hello apostolakisl, We will check into the clock issue. It might be that the clock updater in the UI is not working properly. Hello Teken, If you know how to get certificate information from Opera, then that's all I need. Again, the only reason Java would not work is if for some reason your system is using SSLv2. If you wish, you can send your remote URL to support@universal-devices.com and we can check remotely. ski2020, yes and unfortunately so. SSLv2 is not secure. With kind regards, Michel