Michel Kohanim

Illusion, This reminds of my early days of testing KPLs versions 2A and 2D both of which intermittently caused other devices to turn on. Do yo have any of those in your system? With kind regards, Michel

Hello fkoplik, The problem is communications. Please do the following: 1. Factory reset your switch 2. Go to Link Management | Start Linking 3. Press and hold the set button on your switch With kind regards, Michel

Hi Joe, Please upgrade to 2.8.10 ... I think there may have been an IP conflict: http://forum.universal-devices.com/viewtopic.php?t=5613 This should fix the certificate error. As far as not having My Lighting on your computer, I think the problem may be related to your firewall software. Please make sure ISY is in the trusted zone/white list. You can get your ISY's IP address by going to Help | About. With kind regards, Michel

jtara92101, What happens if you query the thermostat from ISY. Will it then compute? The fundamental problem is this: there's only one interface to get the cool/heat setpoints from the thermostat. This is irrespective of the mode and therefore we are 100% reliant on what the thermostat sends back when queried. If the query fixes the problem, then we can add a query to the code after you change the mode from program auto to something else. If it does not, then we are basically out of luck. With kind regards, Michel

Hello mmknox, That's to be expected since ControLinc is a controller only and does not respond to group commands. With kind regards, Michel

Hello apostolakisl, The problem with that was that if you had too many devices, then some would be chopped (not fitting in the screen). With kind regards, Michel

Moshe, Scene Test in previous versions did not turn on the scene before doing the test. This could explain the scene test issue but this does not explain why your programs do not run. mlennox, Please post your program here. With kind regards, Michel

Hello Joe, ISY has a hard time communicating with your router. If the cables are OK, then the problem could be any of the following: 1. ISY cannot get a DHCP address from the router 2. There are other devices with the same IP address on the network Does rebooting ISY fixes the problem? If so, what version of firmware is ISY running? With kind regards, Michel

Hello Mike R., We have tried numerous techniques to make this faster but, unfortunately, Java is not cooperating! With kind regards, Michel

Hello jp5150, This error occurs when ISY cannot communicate with the device. I recommend removing the KPL from ISY, doing a factory reset on it, and then add it back. If that does not help the situation then the problem is either a defective switch or signal related. With kind regards, Michel

Hello bocaray, Where do you see C instead of F? ficklma1, If the REST interface becomes slow or stops working that's a known issue. If you have communications errors with one or more of your devices, first we have to figure out whether or not the problem is scene related or device related. i.e. do you have the same problem when you query the devices. If you do not have status present in the Admin Console, this points to firewall issues. Would you be kind enough to make sure that ISY is in the trusted/white zone of your firewall. Please note that disabling firewall does NOT help this situation. With kind regards, Michel

Hello Moshe, I have to be clear here since there's absolutely no correlation between 2.8.10 and "some" devices in "some" scenes not responding. ISY does not at all distinguish between sending a command to scene A or scene B. What you might want to try is to disable all your programs and see if this helps the issue. If it does, then you have a program that is causing a conflict. With kind regards, Michel

Hi Tim, Please see my comments below. With kind regards, Michel Thanks! Depends on the type of the socket. For instance, HTTP/HTTPS sockets have a timeout which is configurable in the shell (CWT). Subscription sockets are closed if the subscriber cannot be reached. This said, if the client continues sending HTTP requests, then after a while, all HTTP tasks will be consumed and it might take a while for them to release (backlog of 20) the sockets. I suspect that AtHome, although asleep, is still communicating with ISY and is exhausting the HTTP tasks. No, ISY only closes the socket if there's either timeout or subscriber is not responding. What I think is that AtHome has multiple requests queued up and thus exhausting the HTTP tasks. All sockets are closed and discarded when the system is rebooted.

Hi Tim, Thanks so very much for the update. We really need to know what is AtHome doing when in sleep mode or when it wakes up. From your logs, it seems that multiple threads start communicating with ISY (which is normal) but they never close the socket when AtHome goes to sleep. Do you have access to AtHome developers? If so, please do be kind enough to have them contact us at support@universal-devices.com and we'll figure it out. With kind regards, Michel

Hi Joe, Thank you. This means that ISY is no longer connected to your router/network or the cable from Network to the router is not plugged in correctly. Would you please make sure that the connection from the router to your ISY is secure? With kind regards, Michel

Zellarman, I am not sure what you did in the telnet session (actually nothing is required if you use File | Enable Internet Access). We'd be delighted to help you setup port forwarding in your router. Please do be kind enough to call our tech support and schedule a tech session. With kind regards, Michel

Hi Tim, I need a huge favor from you: please make sure your AtHome and iPod/Pad are completely off (not connected to ISY) and then disconnect DSCLinc and let me know if you still have the same issue. I do appreciate it very much. The synposis is that something is opening a socket and never closes it. ISY keeps waiting for the socket to get closed but it does not. These are HTTP sockets so it would really help if we figure out if any of the external applications are causing this. Once that has been established, we can figure out what steps to take next. With kind regards, Michel

Hello Orest, The problem might be that your KPL is responding with a NACK. If you can query the device properly, then the only thing I can suggest is this: 1. Factory reset your KPL and then try the query again. If it gives you the same error while still working, then I suspect a defective KPL 2. If it works properly and without errors, then please right mouse click on the KPL and then choose Restore Device Is it possible that you have some programs that might be trying to communicate with this KPL simultaneously? With kind regards, Michel

Hello dnl, Unfortunately ISY does not currently support SSL. It supports TLS ... we do have plans for supporting SSL in our requirements but it does not have a high priority. With kind regards, Michel

Hi Tim, What else is communicating with your ISY except for the Admin Console? Do you have any mobile applications such as MobiLinc or Conductor? Do you have ELK? With kind regards, Michel

Hello Zellarman, Did you by any chance upgrade the router's firmware? In some cases (and although I hate hearing it) routers need to be rebooted regularly (weekly) ... I have never had to reboot mine but would you please try rebooting the router and then try File | Enable Internet Access again. Please note that in all cases, it's always best to do port forwarding manually. With kind regards, Michel

Hello Joe, Would you please take a look at the LEDs on the front of the unit and make sure that non are lit except the Power LED? With kind regards, Michel

Zellarman, One has nothing to do with the other and I think you do not have the sequence of events correct: based on our records, you had to have someone local to your ISY install the modules since you could NOT access your ISY remotely. We can certainly disable the modules if you feel that has anything to do with the remote access issue but I just don't want you to waste time on things that I can say with 99.999% confidence have nothing to do with one another. With kind regards, Michel

jwagner010, Thank YOU. We reproduced and fixed the problem! It should be available in the next release shortly. With kind regards, Michel

Hello jwagner010, Thanks so very much ... this gives us something to test with. May I ask how many resources you have? Hi Moshe, please do so. It's extremely extremely unlikely that a new firmware would have a negative impact on scene operations (ISY is not even in the loop). With kind regards, Michel