Michel Kohanim

Hi Robert, We are so close in releasing the ELK module that it would not make sense to spend time on providing this variable. This said, if we run into delays, then yes, absolutely. polexian, I do not think ELK module will be in 3.1.7 since 3.1.7 is mainly to fix other bugs introduced in 3.1.5/6. With kind regards, Michel

Hi Kev, Thanks so very much! Do you mind if we post a link to your post in our Wiki? With kind regards, Michel

Hi Jeff, Please try http://www.universal-devices.com/99i/3.1.6/ and let me know if you have the same problem. With kind regards, Michel

Hello all, I hope you do not mind but this will be a collective response! Mr. Allen, Would you be kind enough to send me the trace/traffic? Or, do you know which authentication method that server requires? I am hoping to have this fixed by 3.1.7. sanders2222 This is quite odd. Are you certain there are NO "Wait" statements in your programs? bcall We are hoping to have 3.1.7 out by this coming weekend. I do recommend holding off since backups using 3.1.6 will be corrupted and basically useless. 3.1.7 will basically be a maintenance release to address some of the bugs introduced in 3.1.5 and 3.1.6 ... plus support for additional devices. ELK module will come out as Beta! ryarber No, the backup bug has no impact whatsoever on upgrading firmware. With kind regards, Michel

Hello aaronburnlab, I already replied to your support ticket. The process is quite simple: backup your current ISY and restore it on the new one. With kind regards, Michel

Hello all, With sincere apologies: Backups using 3.1.6 are corrupted. Please do ensure you keep older backups and also that you do NOT restore 3.1.6 backups on your ISYs. 3.1.7 should be out shortly. With kind regards, Michel

Hello H2R, Thanks so very much for the feedback which helped us find the bug in 3.1.6 as indeed the backup did have binary conversion issues introduced when we added support for Chrome (and their out of band mechanisms to handle SSL). This has been fixed and it shall be included in 3.1.7. Thanks again and with kind regards, Michel

Hello wrj0, No problem at all. Yes, with new INSTEON firmware, there's an option to send humidity reports (instead of having to solder something). We added support for it and just waiting for verification from SmartHome on the correct bit to set (bit 2 or 2nd bit = bit 3). With kind regards, Michel

Hello C Martin, I noticed that your ticket was assigned. Was there a resolution? With kind regards, Michel

Hi C Martin, This is not good. Do you which firmware version backup you were restoring from? We do have your ticket so perhaps it would be best to have a phone support. With kind regards, Michel

Hi Brian, Unfortunately not at the moment. With kind regards, Michel

Hello wrj0, As far as I know humidity reporting is disabled by default. And, you cannot set this setting if you have a thermostat without a sensor. And, finally, there's a known issue with the current thermostat firmware to report humidity x 2. With kind regards, Michel

wrj0, Known issue with the current thermostat firmware version: humidity reporting has to be explicitly set. We are adding support for this command in the next release. With kind regards, Michel

Hi Greg, That's quite possible. I am going to forward this post to our reps at SmartHome. Thanks so very much! With kind regards, Michel

Hi Candide, Those errors are for X10 devices and a bug which shall be fixed shortly. nstein, From which version did you upgrade? With kind regards, Michel

Hello H2R, This should also be fixed once we start playing with the unit. With kind regards, Michel

Hello mohansen, Thanks so very much for the log. I noticed a lot of DNS error but I am not sure why that would cause a system hang. I do not think it's ELK related. I sent you an email with more questions. Again, sincere apologies for this problem. Hi polexian, Unfortunately not. With kind regards, Michel

Hi Greg, Thank you. Just got one of those thermostats and will try to duplicate and provide feedback . With kind regards, Michel

Hi Tim, Query is done after programs have been initialized As soon as the network is up but it depends on what DSCLink/WCLink is trying to do. The steps have not changed but some of the priorities have changed to improve SSL2048 bit performance. What behavior are you seeing? With kind regards,

Hi tome, This is a previous error ... it simply means that someone tried to login but failed. With kind regards, Michel

Hello mohansen, Sincere apologies for tardy reply ... was trying to reproduce alas failed. Can you please let me know whether or not other ISY programs were running? I assume you didn't have regular browser access to ISY either, is that correct? Would you be kind enough to send me your error log to support@universal-devices.com? With kind regards, Michel

Hi jsp, Yes, precisely so that you can see status on ELK Touchscreen and other clients. With kind regards, Michel

Hello robandcathy, Those are mostly OEM/Utilities and we do not have them for retail. In certain cases, if you would like to use Brultech Energy monitors using native Zigbee, you can send an email to sales@universal-devices.com and we'll see whether or not we can accommodate. With kind regards, Michel

Hi Clarence, This means that there are pending device updates that ISY has tried programming into the device but has failed. Please right mouse click on the green 0101 icon and then choose Write updates to device. If that fails, then you have communications issues with that device. With kind regards, Michel

Hello Clarence, All the features available in 2.8.16 are still available in 3.1.6 and thus you do not have to upgrade to use the newest Venstar dongles/thermostats. To answer your questions: Yes. No. Everything you can see on the Admin Console can be changed remotely With kind regards, Michel