Michel Kohanim

Hi Illusion, Ah ... in Java preferences, can you please make sure you click the option such that the application/applet runs in the browser's process and not its own process. This might explain the discrepancy between firefox and safari. ryarber, we are hoping to have an official release the next time around in which case the url becomes /99i (without any release versions). As such, I do note your request but must postpone it till after our official release. burakk, on MAC drag and drop does not work that's why you should use the Copy menu item. With kind regards, Michel

Hello dkaleita, First of all I do not think you are doing anything wrong. The bottom line is that ISY cannot contact your DNS server to resolve names to IPs. This could be ISY related (hardware) or network related. The first thing I would do is to use an IP address instead of pool.ntp.org (i.e. go to the command prompt, and type nslookup pool.ntp.org ). If this works it means that ISY can access the Internet but not the DNS server. Also, it would help a lot if you could look at your router's log and see if there is any traffic for your ISY, whether or not they are being blocked, and the reason code. With kind regards, Michel

Hi Paul, Quite interesting but, at the same time, the epitome of problems with all SWL 35s: randomly going bad and causing comm errors. If it were my installation, I would replace them all especially if you bought all of them at the same time and thus the likelihood of all of them being from the same manufacturing batch. With kind regards, Michel

Hi all, All devices with sense can report status changes. The main issue is that we get the same signal whether or not the device is turned OFF (locally) or the load has gone bad. For INSTEON there's no distinction between the two (unfortunately). With kind regards, Michel

Hi AnthemAVM, Unless the MEM/Error blinking lights are persistent (i.e. they do NOT go away) I would not worry about them. Now, did you move port 80 to 1501 or port 443 to 1501? With kind regards, Michel

Hi drw, I am so very sorry for the inconvenience. This should not have happened ... just to be in synch, would you be kind enough to upgrade to 2.7.13 which seems to be much more stable than 2.7.6? With kind regards, Michel

Hi sceaton, Would you be kind enough to check the following and let us know: 1. Ensure that your program is Enabled AND that you have V2 thermostats (V1 will not work) 2. Go to Program Summary so that you can see the status of programs. Then, please go to Tools | Diagnostics | Event Viewer and choose Level 3. 3. Cause your thermostat to call for Heat then: 1. Check out the traffic in the Event Viewer 2. If you see the events that change the mode to Call for Heat, then look at the program summary page and check the last runtime In short, we want to make sure that your ISY indeed receives that event. If it does not, then we have to figure out where the signal is lost. With kind regards, Michel

Hi Justin, I think the problem is that ISY does not know the version number (.00) of your KPLs and thus does not let you have a sub button control the load. Unfortunately, at this point, I must recommend the following: 1. Remove your KPL from ISY 2. Add it back using either of the following methods: -- Link Management | Start Linking ... then push and hold the set button on your KPL OR -- Link Management | Add New INSTEON Device and ensure that you are using Auto Discover (do not pick a device from the list) With kind regards, Michel

Hi illusion, First of all, there was indeed a problem with v1 thermostats providing the wrong setpoint. Second of all, it's always best to use either Heat or Cool setpoint (not just setpoint). And, finally, when the thermostat mode is Off, the setpoints change to 0 which causes your condition to be true. With kind regards, Michel

Hi bbconvert, Unfortunately not. Have you considered our REST interface? With kind regards, Michel

Hi bbconvert, Unfortunately not. You may want to consider third party interfaces such as InterfaceGo, TouchSwitch, ISY AJAX, ... With kind regards, Michel

Hello again, Thanks so very much for the detailed report. So, would you say that most of the issues are with controlling the load on the Dining Room KPL? If so, would you be kind enough to give me the firmware version as reported by ISY for this device? Also, have you tried to compare the links to this KPL vs. those in ISY? With kind regards, Michel

Hi stevehoyt, We are working on this issue. There was indeed a related bug but I am not convinced it would address all the issues. Still investigating. With kind regards, Michel

Hi Paul, Is is possible that some of them are on while others are off? The reason I asked for replacement is because I have never seen such a behavior nor has it ever been reported. So, if we make sure that they do not have the same brightness (either all off or all on), then that surely indicates a problem. If the compare is identical, then please do a factory reset on your KPL and do another restore. With kind regards, Michel

Hi mitch236, From ISY perspective, there's absolutely no difference whatsoever. Outside of ISY, the only difference would be that MobiLinc is using the WiFi on your router and ISY is using the wired Ethernet. So, I suspect one of the following two scenarios: 1. The scenes do not work in any case ... i.e. you just get lucky that they work when you use the Admin Console. This is device communications issue which has to be investigated further 2. When you use your MobiLinc, your router induces noise on the powerline or RF Access Points (quite unlikely but possible). To verify this issue, try turning off the WiFi on your iPhone and use the Cellular channel. If this fixes the issue, then we might have to think about replacing your router With kind regards, Michel

Hello, You will find the instructions in this post: http://forum.universal-devices.com/viewtopic.php?t=3717 (scroll down to V2 Thermostats). With kind regards, Michel

Hello Genstr, Please see my comments below. With kind regards, This sounds like ISY is not able to send events to the Admin Client. Do you get status change events from your devices? What firewall software do you have? When you cleared the cache, were all your browser windows closed? I think you are referring to folders, correct? If so, this is a known issue and shall be fixed shortly. If you are referring to scenes, then we have not been able to reproduce it. This is why I am wondering that perhaps you do not have the latest Admin Console (your system is using the cached copy). For KPLs, you should see an on level and off level the total combination of which is 32. Of course, this would only work for later version of KPLs than 2D. Thanks so very much for pointing this out .. I do appreciate it. Yes, absolutely and thanks so very much for the feedback.

Hi Steve, Thanks so very much for the feedback. May I humbly ask "which" issue you are experiencing? Is it the System Busy issue or the exception when you close your Admin Console. If the former, are you certain you are using the correct URL? With kind regards, Michel

Hi Paul, I am with oberkc ... the best thing would be to do a compare. If you have different LED levels for different sets of buttons, I do strongly recommend getting your KPL replaced since it is NOT normal. Also, if you have spidered this KPL, there might be links in there that are causing problems. A factory reset of the KPL might also be an option. With kind regards, Michel

Hi Scott, The problem is as follows: 1. Mutual Exclusivity only works locally on the same device 2. As soon as activation of any scene for which these buttons are members of, the Mutex relationship is broken The best approach would be to use the Button Grouping button instead of a scene. Then you must have programs that sense any conflict and update the status. I know this is quite convoluted but - and unfortunately so - this is the only way around the problems stated above. With kind regards, Michel

Hi intellihome, Apologies for the confusion. These are bug FIXES and enhancements. We do not yet have any confirmed bugs in 2.7.13. I am going to update the post and making it more clear. Thanks for bringing this issue to our attention. With kind regards, Michel

Hi gfridland, Catchup schedules would only be the issue if the reboot is within the grace period of your actual timed event. Can you ensure that you do not have the Run at Startup checked (in Program Summary page). With kind regards, Michel

Hi Paul, This does not sound good. Please try this: 1. Open Tools | Diagnostics | Event Viewer ... change level to 3 2. Pick one of the devices for which you have 0101 icon 3. Right mouse click and choose Write Updates menu item Please review the Event Viewer ... if you see many INST-ACK without an immediate INST-SRX, then the problem is that PLM cannot communicate with that device. If you wish, you can post the output of the Event Viewer here. With kind regards, Michel

Hi Glenn, I think they are more accurate since they use the exact latitude and longitude for the weather station. Do you have your exact lat/long? If so, you can change your location to custom location and provide the lat/longs. With kind regards, Michel

Hi Paul, Thanks so very much for the update. A hung Admin Console does not ISY processing and 12 hours (+ more) is really too long .... please keep me posted. With kind regards, Michel