Michel Kohanim

Hello someguy, The problem is in the "brand new" ... unfortunately, you will have to ask SH to update your firmware to the previous release: there's a major problem reading the IR database with the new firmware. With kind regards, Michel

Hello bluebastion, Apologies for the inconvenience. Please do call our tech support team to schedule a call; we'll login to your computer and set it up for you. With kind regards, Michel

Hi Mark, There are two ways of doing this: 1. Use programs the conditions of which are the parameters for the first thermostat 2. If You are looking for Heat/Cool being called, you can use scenes. i.e. the first thermostat heat/cool calling as the controller and the other thermostat as a responder With kind regards, Michel

Hi Mark, Thanks so very much for the update. I have to suspect firewall software on your PC. With kind regards, Michel

Hi theedudenator, Sorry, I didn't pay close attention to the event. In short, it's only your scenes that do not work. Would you please try restoring one or two of the devices in the scene? If that works (i.e turning on/off the scene has the desired impact on those devices), then follow up with File | Restore Devices ... this might take a long while. With kind regards, Michel

Hi Mark, do you get invalid length error or "ISY refused program update"? You are always welcome to call our tech support team to help out. With kind regards, Michel

Hello theedudenator, It seems that ISY has a hard time communicating with that specific device (3 INST-ACK and no SRX). This means that ISY tried 3 times to communicate with the device and it couldn't. Can you control this device using the main screen in the Admin Console? Try doing a query on it (right mouse click and then Query). With kind regards, Michel

Hello Mark, Apologies for the inconvenience. Would you be kind enough to try https://your.isy.ip.address/admin instead? Please note httpS and not http. With kind regards, Michel

Hello nowandthen, I am not sure what you mean by LEDs not showing up in the tree. Are you talking about the sub buttons? It's basically impossible to have KPLs without sub buttons unless: 1. The device was not added as a KPL (what's the description of the device)? 2. Corrupt file system (extremely rare) 3. They are actually there ... try using the Topology tool to see if they are already there With kind regards, Michel

Hello Mike R. Long time no see! I am so very glad to hear that everything seems to be working. The last time we tried the upgrade, the problem was the new firewall that was installed on your computer. Do you still have the same firewall or have you changed to a new one? With kind regards, Michel

Hi kevinbgibson, v00 means that ISY was instructed to assume a device type and thus didn't request for the firmware version. To get the actual firmware version, you will have to remove that device from ISY and either use Start Linking or Add New INSTEON Device | Auto Discover. Firmware versions below 2D do not support backlight adjustments. With kind regards, Michel

Hello all, Here's an update: Installed the new thermostat with the humidity sensor and it has been running for a long while now. The fluctuation between readings has never been more than 10%. Please note that the thermostat sends the humidity changes on its own so, when you do a query, you are getting the latest value. Has anyone experiences fluctuations of more than 10%? With kind regards, Michel

Hi kevinbgibson, The reason backlight does not work on the other KPLs is because, apparently, those devices were added using a specific type (Add INSTOEN Device and NOT choosing Auto Discover). If this is really important, then the only way to see if those devices support backlight is to remove them from ISY and use either of the following methods: 1. Start Linking 2. Add INSTEON Device using Auto Discover Please note KPL versions below 2D do NOT support backlight. With kind regards, Michel

Hi Joe, Yes, you can test for the status of any device regardless of their membership in any scene. You have two choices: 1. Use the Status of the device in your programs. Status changes if and only if the status of a device has changed. i.e. from on to off or vice versa. Status does NOT change and your programs are not re-evaluated if you turn on an already on device or turn off and already off device 2. Use Control in your programs. Control is basically the event generated from physically activating your device. So, if you turn on an already on device, your programs are re-evaluated every time. If you want to test for the status changes of a controller in a scene, it's best to use Status (not Control) From ISY's perspective, using X10 capabilities of an INSTEON device is equal to using X10. As such, there are still no easy ways of migrating from X10 to INSTEON. With kind regards, Michel

Hi Joe, Please see my comments below. With kind regards, Michel No No. As of right now, ISY does not know what a scene status is. Yes. Simply have the program call the scene There's really not an easy way. But, here are some pointers 1. Add your INSTEON devices for the X10 devices one scene at a time (i.e. those that participate in scenes together) 2. Go to programs, do Find/Replace and remove all the programs that depend on old X10 devices 3. Go to the main panel and remove the X10 devices With kind regards, Michel Thanks Joe

Hi Guys, The problem is fixed based on the records but it seems that it has not gotten into 2.7.15. The problem is that ISY was using an INT which didn't have enough range to support larger capacities. If you do not mind alpha software, please do send an email to support@universal-devices.com and please try 2.8.0. With kind regards, Michel

Hello Mr. Giffen, As far as I can tell, the value is a number between 0 - 100 and it denotes the ambient light level. The light rate is the percentage of change in hour. With kind regards, Michel

Hello Billy, Just got the thermostat, installed it, and it's on the list of things to do shortly. Unless it's an API/Thermostat problem, I do not think this is going to take long. With kind regards, Michel

Hi Dennis, Would you be kind enough to: 1. Clear your java cache 2. Go to http://www.universal-devices.com/99i/da ... admin.jnlp Let me know if you still have the same issue. With kind regards, Michel

Hello jwf, If you get a request failed for backlight, it's because your KPL does not support it. As far as disable, ISY cannot really physically disable an INSTEON device. This feature is there to let you remove a device from an outlet without ISY complaining about not being able to communicate with it. With kind regards, Michel

Hello jwf, ISY with IR option allows you to trigger based on whatever you like but it's really up to you to program it as a toggle vs. non-toggle. i.e. the action part of the program decides what needs to be done. With kind regards, Michel

Hello wrdarnell, You can name it whatever you like! With kind regards, Michel

Hello Dennis, ISY supports up to 16GB. There was a bug in the UI reporting routine which is fixed. In any case, please: 1. Take a backup of your system 2. Telnet to ISY 3. Issue FS (formats the SD Card) ... although ISY works with both FAT 16/32, the FS function formats it specifically for use with ISY with some performance improvements Once FS is complete. you will have to go to http://www.universal-devices.com/99i and then reinstall 2.7.15 and then restore your backup. With kind regards, Michel

Hello paulbram, The issue with WB alerts is that it has to be sent ... as far as I know, there's no way for us to query the alert status yet. We do have plans for WB improvements such as forecasts and evatranspiration but currently on low priority. With kind regards, Michel

Hello gtrotter4, Sincere apologies for a tardy reply. The first question I have is whether or not you could connect remotely via a browser (not iPhone). This can help us isolate the problem. Unfortunately there's not much you can do to prevent the router/modem reboot. With kind regards, Michel