Michel Kohanim

Hello hackshaven, I am so very sorry to hear that WB does not want additional members. We tried Weather Underground before going with WB but the amount of licensing fees they wanted far exceeded anything that a normal user would want to pay (monthly fees of close to $20.00/month based on our current number of users). Unfortunately, I do not think we can support Weather Underground. With kind regards, Michel

Hi Mitch, The program you have will run every time the Armed Away becomes False and on between 7:30 PM Fridays till 7:00 AM the next Monday. So, if during these hours, the program changes state from true to false/and vice versa, this program is evaluated and run accordingly. With kind regards, Michel

Hello GPG, Thanks so very much for providing us with this feedback which I am sure others will find extremely useful. Do you mind if we included your post in our Wiki? With kind regards, Michel

Hello joefly, Sincere apologies for the inconvenience. The problem you are reporting has to do with File System. If you have moved your ISY, in all likelihood, the SD Card (on the left side of the unit) has become loose. If you have an ISY with an SD Card slot on the left, all you have to do is to push the SD Card in so that it pops out and then reinsert it back in ensuring that you hear a click. If your enclosure does not have an SD Card slot, then, unfortunately so, you will have to take out the board and reseat the SD Card. With kind regards, Michel

Hello aaronb, Please go to Tools | Diagnostics | Event Viewer on Level 3. Turn on/off the questionable button and let's see if you get any events in the event viewer (INST-SRX). If not, there could be three explanations: 1. The signal is not getting from the KPL to the PLM 2. The PLM has reached its link capacity and thus you are not hearing status updates If other buttons on the same KPL work, then may I humbly recommend: 1. Removing KPL from ISY 2. Doing a factory reset on it 3. Adding it back With kind regards, Michel

Hi Tclark, This is usually indicative of port forwarding issues (i.e. you have some other devices port forwarded to the same IP as ISY). Please check port forwarding rules in your router and let us know. With kind regards, Michel

Hi Mitch, This will only run once. You might want to add a repeat for each 24 hours. With kind regards, Michel

Hello bktong, Thanks so very much. LeeG also had an idea that we are investigating: Do you know what's the actual humidity reported by your thermostat? How far off is it from what ISY reports (obviously not anything above 100%)? And, is there any way you could verify this value against say WeatherBug for your area? Thanks and with kind regards, Michel

Hi Billy, It seems that there's something wrong with thermostat/dongle as it's reporting 9E (158) for humidity. With kind regards, Michel

Hello Billy, Excellent. What I need is the message right prior to the first message. You see, when you got 44%, the last byte of the message received was 2C (=44 Decimal). But, you didn't send the same message for 154. In case you try and you get: Fri 09/10/2010 08:15:05 PM : [iNST-SRX ] 02 50 14.07.FB 12.9C.D8 07 6F 9A (9A) Then we know that the thermostat is returning the wrong humidity (9A = 154 in Decimal). In short, what you need to do is to check the last byte of the returned message (INST-SRX) which is Hex. Use your computer's calculator to covert the last byte from Hex to Decimal. If the calculated value is equal to what ISY reports, then the problem is either the dongle or the thermostat itself. With kind regards, Michel

Hi Tim, DON is only active till the next reboot. Regardless, do you still see 100xx errors? As I mentioned before, the duration within which ISY locks you out (during DOS) depends on: 1. How frequently you are getting the attack 2. Have you been able to login in the meantime I still need to know if you have Pure Network's Network Magic running anywhere. Most Cisco/Linksys routers have this feature and you might have had it enabled. Can you think of any changes you made to your network, router, firewall? With kind regards, Michel

Hi Tim, The fact that you can still telnet to ISY even though your programs are not running and even though you cannot access the Admin Console means that a) ISY is NOT locked up and b)rebooting may only solve the symptoms but not the cause. If you want to be able to remotely telnet to ISY, all you have to do is to forward port 23. With kind regards, Michel

Hello mdyod, I am not sure what news you were awaiting but, based on the specs, we are sending the correct command. With kind regards, Michel

Hi Andy, The first question is whether or not this is ISY26 or 99 we are talking about. If they are at 2.7.0 or above, all you have to do is to go to Help | Automatically Upgrade My Lighting. This will install 2.7.15. If they are on an older firmware, and if this is an ISY26, the best method would be to contact our tech support to walk you through it. With kind regards, Michel

Hello osullys, I let Burak talk about TouchSwitch. But, here are my comments: 1. Since you already have Network Module, then all you have to do is to create rules in the network module to communicate with GC (I do not think you need Bobby) 2. In TouchSwitch, under settings, add buttons that call the Network Resources. This way, you can use your iPod to control all rules pointing to GC With kind regards, Michel

Hello ceaves, There are two explanations for this: 1. Java cache was not cleared properly 2. Firewall issues ... please do ensure that ISY's IP address is in the Trusted/White list on your firewall With kind regards, Michel

Hi Tim, Thanks so very much. This explains the reason why you could not connect to the Admin Console: Something (or someone) is trying to login to your ISY with bad (or no) credentials every few seconds. ISY considers this an attack and disables HTTP tasks for a while. It may keep the tasks down till such time that the attack is no longer there OR that you have logged in successfully. Now, this could happen in two cases: 1. Network Magic is a major cause for this issue. If you have Network Magic, please disable the scan since that's what's causing all the login attempts 2. Someone is actually trying to hack in to your system If you have 2.8.1 or above, you login to the shell, issue DON; this will cause ALL traffic to be logged in the error log (including the IP address of the caller). With kind regards, Michel

Hello Tim, 503 is an HTTP error for "Service Not Available": http://www.checkupdown.com/status/E503.html How many 10103s do you get? And, in both cases, do you get 140008 before it stops? With kind regards, Michel

Hi Tim, Apologies for a tardy reply. Weatherbug values are integers with 4 decimal places. i.e. 74.235, 101.824, etc. ISY does NOT round off the values in program execution but it does so for display purposes. So, basically: 74.235 > 74.000 74.900 So, if you really want to handle "in between values" you would have to use the And/is not operators. With kind regards, Michel

Hello raaka, Excellent! I assume you can now log in to the Admin Console, correct? Just by the virtue of having such an old firmware (more than 2 years old), I suspect your PLM is probably as old. I must warn you that older PLMs (firmware 72 and below) had many bugs that have now been fixed. If you have an older PLM, I strongly recommend getting it replaced with 2413S. With kind regards, Michel

Hello lawr1000, You should only see one. A load controller is no different than a SwitchLinc Relay ... With kind regards, Michel

Hello raaka, You might have an older firmware where the telnet port was 126 instead of the default. As such, please try: telnet 192.168.0.103 126 If this works, then we know the reason why you cannot get to it from the browser: the old firmware used to have a different port for each ISY. So, if telnet is successful, at the shell you will see the exact URL for your ISY. Once you got that, then you will HAVE to upgrade the firmware. Also, you can figure out the URL for your ISY by: 1. Going to your Network dialog (on Windows) ... if you have UPnP enabled, it shows up as My Lighting 2. Go to http://www.universal-devices.com/99i With kind regards, Michel

Hi Billy, I do think there's a problem with either the humidity sensor or the dongle especially if it happens more than 50% of the time. With kind regards, Michel

Hello LeeG, We shall take a look but a cursory look at the specs and the output show that we are indeed sending the correct command. With kind regards, Michel

Hello all, Thanks so very much for the feedback. That was indeed a bug with 2.8.1 and should be fixed in 2.8.2. With kind regards, Michel