Michel Kohanim

Hello cartwrig, Yes, but the main issue was that between different releases of 2A and 2D some did actually support this feature and thus there was no easy way for us to determine which one didn't. With kind regards, Michel

Hello theedudenator, You do not have to post anything. Did you get any failures? if so, we have to figure out what's causing the failures. What I would do is repeat the same test with ALL devices OFF. If the test succeeds, then it means one of your devices is causing noise. With kind regards, Michel

Hello jcip, Heat/Cool are called if and only if the thermostat is calling for them. So, this is only OK if your thermostat is not doing anything. With kind regards, Michel

Hello jcip, Yes, they are. I assume you have four nodes for each. The next question is whether or not you are on 2.7.15 firmware. If not, please do so. If yes, then I recommend doing a factory reset on the thermostat, remove it from ISY, and then add it back in. If that still doesn't work, then I would have to think a problem with the thermostat. With kind regards, Michel

Hello theedudenator, Please use Tools | Diagnostics | Scene Test to test your scenes for communication problems. If some devices in some scenes fail, we have to figure out what's causing the issue. With kind regards, Michel

Hi Guys, -5011 means ISY could no longer communicate with the client (i.e. Admin Console, MobiLinc, IES Touchpanel, etc.). mitch236, you did have this problem before and you were going to figure out which one of your devices were causing it. With kind regards, Michel

Hello jcip, Is this a V2 thermostat? With kind regards, Michel

Hello bocaray, It's really not needed unless you have programs that depend on 100% accurate reporting of device status AND you do a lot of dim/bright commands. With kind regards, Michel

Hello someguy, Can you please go to Event Viewer on level 3, try adding another button, and then paste the events here. With kind regards, Michel

Hello jkraus, Java socket errors and the inability to restore backup all point to firewall software. Have you recently changed/updated your firewall software? Apologies for not getting back to you sooner: we are completely closed on Saturdays and email/forum only over the weekend. With kind regards, Michel

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