Michel Kohanim

Hi binaryman, In what version of ISY were you able to see the status of MorningLinc in programs? With kind regards, Michel

Hi Joe, my pleasure and with pleasure! With kind regards, Michel

Hi johnnyt, The best thing to do would be to use our debug version (pretty stable). With kind regards, Michel

Hi Taner and Greg, I can definitively tell you that the problem is that INSTEON messages are corrupted in transit and then translated as On by any devices that's on the path (from PLM). What you need to do is: If you have any programs that change the status of a backlight button on KPL, make sure they are no loops or make sure there are delays between each activation. If those buttons are activated because of a previous event form another device, such as a motion sensor, make sure there's a delay between the program becoming true and the KPL backlight scene being activated The above two will dramatically reduce the number of occurrences (reducing collision between traffic going on and traffic coming into the PLM). With kind regards, Michel

Hi Xathros, It's quite possible since we removed UPnP subscription from ISY in 3.3.10. Everyone on the Developer's list was notified but apparently not AtHome. I think that's the crux of the problem. With kind regards, Michel

Hi Joe, If you are planning to also have some Z-Wave devices, then you will have to choose between energy monitoring and Z-Wave i.e. you can either have Zigbee OR Z-Wave. If Z-Wave integration is more important, then you should just get the regular 994. If Energy Monitoring is more important, then 994i Z series would be the right choice. Integration with Davis Weather Station and others can be done on both once we have the functionality. With kind regards, Michel

Hi Taner, There has been other report of this issue and thus far the problem seems to be related to INSTEON traffic being misconstrued as group 255 (all). Question Do you happen to have a program that checks the condition of a Motion Sensor and then changes the status of a KPL button (through a scene)? If so, please try putting a delay between the change in status and then the activation of the button. With kind regards, Michel

Hi jtara92101, Usually, this works: 1. Remove Java 1.7 completely 2. Go to software update and make sure your existing Java 1.6 is up to date 3. Reinstall Java 1.7 With kind regards, Michel

Hi johnnyt, Xathros has a valid point. And, since there are two other reported issues with clock on 4.0.5 (even though unrelated), it would be great if you could contact us so that we can have a debug version installed and monitor what's going on. With kind regards, Michel

jtara92101, Dashboard URL is: http://isy.universal-devices.com/99i/dashboard.jnlp . With kind regards, Michel

jtara92101, Dashboard URL is: http://isy.universal-devices.com/99i/dashboard.jnlp . With kind regards, Michel

Hi johnnyt, In addition to suggestions by apostolakisl, please check your logs for any anomalies related to the reported time. With kind regards, Michel

Hello jtara92101, OpenADR is a standard that will be used by utilities (especially those in California) to convey real-time load/price signals to customers. You cannot really do much with it now but I am certain next year most (including SDGE&) will offer incentives and rebates for participating. With kind regards, Michel

Hi jtara92101, Are you still having the localhost issue? If so, it points to a faulty Java installation on MAC. With kind regards, Michel

Hi Xathros, Thank you for the explanation. You only need to restore your 3.3.10 backup if you downgrade and thus the reverse is not true: you should be able to restore your 3.3.10 backup on a 4.0.5 and everything should be migrated properly after reboot. With kind regards, Michel

Hi Steigs, We are working on it as we speak. With kind regards, Michel

Hi Talbot, Please send an email to sales@universal-devices.com, with your current model number and date of purchase and we'll do our best to accommodate. With kind regards, Michel

Hi johnnyt, Debug statements to check the health of INSTEON databases in the presence of X10 devices. You can safely ignore them for now. With kind regards, Michel

Hi Tom, You cannot use the 99 certificate. If it was self signed, then please recreate one for your 994. With kind regards, Michel

Hi Tom, What type of certificate do you have? If you want to import an existing certificate, it has to be in PKCS12 format (.pfx). Otherwise, you will have to go through the whole process of sending a request to CA, and then receiving the certificate. With kind regards, Michel

Hi Michael, First, we have to figure out why your support requests are delayed. Would you please try submitting a ticket instead (links below)? No, please close the Admin Console. So, we need to figure out where the traffic is coming from. With kind regards, Michel

Hi Drew, I do not know what's a KPL bug and, unless you think this is related, I do not wish to mix them up. Need more information about your programs: 1. Contents of one that does not work 2. Whether or not it's inside a folder with condition 3. Do you see status changes for your devices in the Admin Console whey you physically activate them? If you wish, you can respond to support@universal-devices.com as it'll be much quicker. With kind regards, Michel

Hi Tom, On 994, the link should take you to: http://www.universal-devices.com/docs/I ... 0Guide.pdf Basically, what you need to do: 1. Read and familiarize yourself with the concepts 2. Follow the instructions on page 9 section d to create a self signed certificate With kind regards, Michel

Hi Drew, It seems that your backup is not the reflection of reality. At this point, it's best to: 1. Backup your 994 2. Copy the contents of your 99/CONF (including all sub directories) SD Card 3. Remove the contents of your 994/CONF SD Card 4. Paste the contents of #2 into 994/CONF directory Although not advised, I really do not see a better option at the moment. With kind regards, Michel

Hello Mike Roach, Apologies for tardy reply and I wished you had contacted our tech support team and I strongly recommend that you do anyway. The first thing I recommend is: remove ISY from the PLM and let me know if the PLM is still blinking. If so, you have a device (most probably X10) that's inundating the network with noise/traffic. If not, ISY is probably trying to write updates to devices and it's just busy. With kind regards, Michel