Michel Kohanim

Hi Mike, Not at all: 994/99 UIs are identical. With kind regards, Michel

Hello to_lighter, Long time no see! 1. Try accessing ISY's HTTPS port locally using https:// ... if that does not work, then the issue is https related 2. Are you certain port 443 is not being forwarded to anything else? With kind regards, Michel

Hi starmanj, All status changes from the thermostat should immediately appear in the Admin Console. I suspect that your thermostat is not sending any change of state events back to the PLM. This could be attributed to 3 things: 1. You have too many links in the PLM. To verify, go to Tools | Diagnostics | Show PLM Links Table ... Start, wait for it to complete, and then click the Count button 2. Your thermostat is not registered in ISY properly. To validate, remove the thermostat, makes sure it's in the off position and then add it back using Start Linking method 3. The thermostat is defective. If neither of the above - and barring communication issues - you should get the thermostat replaced With kind regards, Michel

Hi Gary, No plans yet! Need more demand. With kind regards, Michel

Hi Ed, In addition to Brian's questions above, please note that rebooting ISY has no bearing on communications between devices. My recommendation is to NOT reboot ISY before contacting our tech support. It would be best to login to your computer and see what's going on. With kind regards, Michel

Hi oberkc, Thanks so very much. So, basically, some variation of upgrade/restore is restoring the wrong mode in the KPL. We have to figure out where the problem is. With kind regards, Michel

Hi jmed999, Rain information for some CA stations are non-existent. Light rates are not reported by all stations. So, in most cases, the customers do not really know if light information exists. With kind regards, Michel

Hi ejh3, Without details, it would be quite difficult figuring out what problems you are having and why you need to reboot ISY. Why do you have to reboot ISY? With kind regards, Michel

Hi munchee, Then, and unfortunately so, the unit is defective. I am so very sorry. With kind regards, Michel

Hi jmed999, That's excellent news! The most important thing is rain and light data ... we have communicated with them in the past but nothing came out of it. With kind regards, Michel

Hi ejh3, Which device did you have to reboot 3 times and what's your ISY's firmware version? And, what you are trying to accomplish? Putting the load as a responder means that when you turn on/off the load, the sub button is not going to reflect the correct status. With kind regards, Michel

Hello munchee, Are you certain Error or Error/Mem lights on the front of the unit are not blinking continuously? With kind regards, Michel

Hi nexus, Also, please go to Tools | Diagnostics | PLM Status/Info and make sure you are NOT in safe mode (it must show the PLM firmware version + "connected"). With kind regards, Michel

Hi Jim, These are from your X10 devices and are completely benign. With kind regards, Michel

Hi Guys, When we initially started, WU wanted an exorbitant amount of up front money for licensing and usage + service fees for each instance. Based on our calculations, we would have had to charge at least $100.00 per module per year just to break even. With kind regards, Michel

Thanks oberkc! I just tried a restore on a KPL v.40 with non-toggle buttons and everything got restored properly. It could be related to the database upgrade from 3.2.6 to 3.3.x. With kind regards, Michel

I am sorry but I have no clue what "native object" means when it comes to timers. ISY does have timers and pretty sophisticated ones. So, please do be kind enough to elaborate. With kind regards, Michel

Hello Oskar, Thanks for the update on the UI/ELK issue. The entries in the error log are 100% benign. They are just showing detailed access information. If you see socket inactive error, it means that the socket was improperly closed ... in short, you are OK. With kind regards, Michel

Hi LeeG, Thanks so very much for the experiment. So, in short, a device restore in 3.3.6 causes button toggle LEDs not to operate properly even though the button itself is indeed operating as non-toggle off? With kind regards, Michel

Hi jjwinston, It's a little difficult visualizing what you are trying to accomplish. May I humbly suggest two things: 1. Please review our tutorials (including videos) at http://wiki.universal-devices.com 2. If you are still having problems, please do not hesitate to contact us (links below) and we'll schedule a call to discuss any/all questions you might have With kind regards, Michel

Thanks Jason ... I do not think v95 supports setting time. Unfortunately I do not know the firmware version that does. With kind regards, Michel

Hi oskarw, Thanks so very much for the feedback. Would you be kind enough to let me know the UI version for the Admin Console? Also, if possible, can you try http://www.universal-devices.com/99i/3.3.5 instead and let me know if you still have the same problem? With kind regards, Michel

Jacob, As LeeG suggested, it's VERY important not to go back and forth between backup/firmware releases. when upgrading to 3.3.6, all database files are upgraded. We might have an issue with the upgrade process. This said, going back to firmware 3.2.6 will only exacerbate issues. Again, as LeeG suggested, please: 1. Restore a backup from 3.2.6 2. Remove the KPL in question 3. Add it back in Let me know if you have the same issues with other KPLs as you have with the one in question. Hi tunaman, What operating system and Java version? With kind regards, Michel

Hi Jason, You mentioned that they don't seem to be working. So, is the only problem you have is adjusting time/schedule? If so, you need their latest firmware. If not, can you tell me what's not working? With kind regards, Michel

Hi Mark, when you get a chance, can you tell me what you did to recover that took 8 hours? Just trying to figure out how we can optimize recovery. With kind regards, Michel