klundy Posted July 24, 2011 Posted July 24, 2011 Changing the timeout to 500 improved my results, but still not 100%. I just did 10 test mails from the configuration screen. 1 every 10 seconds or so. 7 were successful (with the body timeout error), but 3 gave me a password error. Note that I wasn't changing the password during this test Also, any thoughts on the IR messages I am receiving? Thanks!!! Kevin Hello Candide/dennisric/RatRanch, Apologies for the inconvenience. Upon further testing it seems that our performance improvements to the SSL library has caused ISY to be faster than before so timeouts greater than 1000 ms causes ISY to wait for a response from the server after it has posted the Body but the server closes the connection before the timeout. In short, now, the longer the timeout, the more errors you are going to get. So, please try 500, 750, 1000, and 1500. The most important test is to not get Server not responding (that's what the timeout should be used for). Once you have the timeout set, you can ignore Body timeout errors since the email has already been sent. You will be pleasantly surprised by the improved performance with shorter timeouts. The extra errors are going to be fixed in the next release. Please note that this issue only affects TLS (which depends on SSL). With kind regards, Michel Quote
robandcathy1 Posted July 24, 2011 Posted July 24, 2011 Thank You Lee again, I tried this also before but it would not work until I added a few seconds on the clock, which brings me to the question why do I have to add time to the sunset/sunrise program. The ISY does have a internal clock that adjusts daily to both sunset/sunrise, can it not start running at that exact moment? Not that it matters 15 seconds but just trying to understand the ISY better, also thought that would be a simpler way of doing it. Thank You again! Quote
ryarber Posted July 24, 2011 Posted July 24, 2011 I have come home to a frozen ISY the last two days. How can I troubleshoot this? Quote
Michel Kohanim Posted July 24, 2011 Author Posted July 24, 2011 klundy, Thank you. Please try 750 ... you can ignore body errors (server, password, user timeouts should be fixed by increasing the timeout). ryarber, Sincere apologies. Would you please let me know: 1. Do you have ELK integrated with your ISY? 2. Are you now using 2048 SSL certificates? 3. Has anything at all changed in your LAN? With kind regards, Michel Quote
Brian H Posted July 24, 2011 Posted July 24, 2011 I am seeing lots of network errors again with 3.1.5. Sat 2011/07/23 07:11:21 PM System -5 Start Sat 2011/07/23 07:11:31 PM System -60001 pool.ntp.org Sun 2011/07/24 07:11:42 AM System -60001 pool.ntp.org Sun 2011/07/24 07:11:57 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:13 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:30 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:48 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:06 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:24 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:42 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:00 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:18 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:48 AM System -100 [DHCP] state=FAILED Sun 2011/07/24 07:18:48 AM System -100 [DHCP] Timed out; Restarting Sun 2011/07/24 07:23:27 AM System -100 No network connection Sun 2011/07/24 07:24:51 AM System -100 No network connection Sun 2011/07/24 07:26:16 AM System -100 No network connection Sun 2011/07/24 07:47:31 AM System -100 No network connection Sun 2011/07/24 08:02:56 AM System -100 No network connection Sun 2011/07/24 08:34:11 AM System -100 No network connection Sun 2011/07/24 08:57:25 AM System -100 No network connection Sun 2011/07/24 08:58:10 AM System -100 No network connection Sun 2011/07/24 09:15:26 AM System -100 No network connection Sun 2011/07/24 09:17:01 AM System -100 No network connection Sun 2011/07/24 09:21:06 AM System -100 No network connection Sun 2011/07/24 09:24:41 AM System -100 No network connection Quote
bcall Posted July 24, 2011 Posted July 24, 2011 Sincere apologies. Would you please let me know:1. Do you have ELK integrated with your ISY? 2. Are you now using 2048 SSL certificates? 3. Has anything at all changed in your LAN? With kind regards, Michel Hi Michel, My ISY has also been freezing sporadically over the last few weeks. It's been driving me nuts. It wouldn't be that big a deal but I use it to control my EZRain and I live in Las Vegas, so the plants don't get watered and when it's over 100 degrees that can be really bad. I have two ISYs, one at my house and one at my parents'. The one at my house never crashes. It's the one at my parents' house that's been problematic. That one is connected to an Elk security system. I noticed you mentioned that in your diagnostic questions. Thanks for any help you can give. Brad Quote
junkycosmos Posted July 24, 2011 Posted July 24, 2011 Question on support of load status for the 2477SA2 220v normally closed load controller. I searched and found a few discussions on here regarding support for load sense but never saw full conclusion. There are a few entries in the beta 2.17 and 2.18 asking how the ISY displays what might be considered "node2" or load sense for this device. I have verified that the recent version unit received from SH (r1.0 2910 received 2wks ago) had load led that follows load status pretty well when 2477SA2 main relay is off. Closing and opening the load circuit while the main 2477sa2 is off had the load led follow correctly. Toggling 2477sa2 relay on/off quickly can cause the load led to getbstuck on however doing a status querry by isy of 2477sa2 always resets the load led. Having 2477SA2 main relay powered on results in load led staying on regardless of load circuit state being open or closed. So we might say load status led works half of the time: when the 2477SA2 main relay is powered off. Would still be of value to have the load status node reported in ISY even though it only works during power off. There are a few scenarios where it becomes useful to know the controlled load is calling for power when the 2477SA2 is off. This would be especially useful since relay of 247sa2 does not automatically follow load sense led: I.e. Isy could be used to decision when load calls for power run a program to turn on 2477SA2 relay or send notification etc. I see from this forum thread that others have been able to manually link insteon devices to 2477SA2s load sense viewtopic.php?f=27&t=5449 Is there a way to have the load sense report in the ISY ? Thanks much J Quote
klundy Posted July 24, 2011 Posted July 24, 2011 With 750, 7 out of ten went through. With 875, 6 out of ten. With 1000 it was 6 out of ten. I still see 1 server error and the rest were password errors. With "use default" it was 10 out of ten. I also think I identified a GUI bug. When just changing the timeout, the save button doesn't seem active. I had to click on another field in order to get the save button to save. I found another thread similar to my IR messages and you indicated to that user it sounded like a bad IR module. Should I contact support for a replacement (I purchased directly from the UD store). Last I checked, today is Sunday, shouldn't you be off today? klundy, Thank you. Please try 750 ... you can ignore body errors (server, password, user timeouts should be fixed by increasing the timeout). Michel Quote
Candide Posted July 24, 2011 Posted July 24, 2011 klundy, Thank you. Please try 750 ... you can ignore body errors (server, password, user timeouts should be fixed by increasing the timeout). ryarber, Sincere apologies. Would you please let me know: 1. Do you have ELK integrated with your ISY? 2. Are you now using 2048 SSL certificates? 3. Has anything at all changed in your LAN? With kind regards, Michel Thanks for the update and steps. I updated to 3.1.5 again and tried timeouts of 900 and 750, both were the same, I got a "body" error but the message was sent. The Weather module does respond, at least with the airport station, I will have to wait to see if there continual errors, I will update here. Thank you, Quote
Candide Posted July 24, 2011 Posted July 24, 2011 I am still getting weather-bug errors on some stations, current in the list. Sun 2011/07/24 04:35:52 PM System -140005 CLI-WBug Quote
Michel Kohanim Posted July 24, 2011 Author Posted July 24, 2011 Hello Brian, Apologies for the inconvenience. This is how ISY works: 1. If there's an error resolving a name to an IP (DNS erorr) then ISY increases the timeout for DNS resolution. If after 10 retries ISY can still not resolve a name (that used to work), then it concludes that DNS servers might have changed and therefore it tries to renew its DHCP lease (if it does not have a static IP address). From the errors below, it seems that ISY is trying to renew its lease but your router is refusing to renew ISY's lease. It would be a great help if you can look at router's logs and for the time period below cut/paste the entries. In 99.999% of the cases, the router must honor a lease renew request. With kind regards, Michel I am seeing lots of network errors again with 3.1.5.Sat 2011/07/23 07:11:21 PM System -5 Start Sat 2011/07/23 07:11:31 PM System -60001 pool.ntp.org Sun 2011/07/24 07:11:42 AM System -60001 pool.ntp.org Sun 2011/07/24 07:11:57 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:13 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:30 AM System -60001 pool.ntp.org Sun 2011/07/24 07:12:48 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:06 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:24 AM System -60001 pool.ntp.org Sun 2011/07/24 07:13:42 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:00 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:18 AM System -60001 pool.ntp.org Sun 2011/07/24 07:14:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:14:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:15:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:16:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:48 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:17:58 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:08 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:18 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:28 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:38 AM System -100 [DHCP] state=RENEW Sun 2011/07/24 07:18:48 AM System -100 [DHCP] state=FAILED Sun 2011/07/24 07:18:48 AM System -100 [DHCP] Timed out; Restarting Sun 2011/07/24 07:23:27 AM System -100 No network connection Sun 2011/07/24 07:24:51 AM System -100 No network connection Sun 2011/07/24 07:26:16 AM System -100 No network connection Sun 2011/07/24 07:47:31 AM System -100 No network connection Sun 2011/07/24 08:02:56 AM System -100 No network connection Sun 2011/07/24 08:34:11 AM System -100 No network connection Sun 2011/07/24 08:57:25 AM System -100 No network connection Sun 2011/07/24 08:58:10 AM System -100 No network connection Sun 2011/07/24 09:15:26 AM System -100 No network connection Sun 2011/07/24 09:17:01 AM System -100 No network connection Sun 2011/07/24 09:21:06 AM System -100 No network connection Sun 2011/07/24 09:24:41 AM System -100 No network connection Quote
Michel Kohanim Posted July 24, 2011 Author Posted July 24, 2011 Hello Brad, Sincere apologies for the inconvenience. This is a known issue with ELK and the only time we have been able to reproduce it is when ELK is in programming mode (through ELK RP or other methods). We should have the ELK module out shortly which should address this issue. In the meantime, if possible, remove ELK configuration from ISY and let me know if you still experience system hang. With kind regards, Michel Sincere apologies. Would you please let me know:1. Do you have ELK integrated with your ISY? 2. Are you now using 2048 SSL certificates? 3. Has anything at all changed in your LAN? With kind regards, Michel Hi Michel, My ISY has also been freezing sporadically over the last few weeks. It's been driving me nuts. It wouldn't be that big a deal but I use it to control my EZRain and I live in Las Vegas, so the plants don't get watered and when it's over 100 degrees that can be really bad. I have two ISYs, one at my house and one at my parents'. The one at my house never crashes. It's the one at my parents' house that's been problematic. That one is connected to an Elk security system. I noticed you mentioned that in your diagnostic questions. Thanks for any help you can give. Brad Quote
Michel Kohanim Posted July 24, 2011 Author Posted July 24, 2011 Hello junkycosmos, As far as I remember, load sense simply sends an off when no load is connected. I am not aware of any multicast signals that would help ISY identify whether or not a load has been disconnected. With kind regards, Michel Question on support of load status for the 2477SA2 220v normally closed load controller. I searched and found a few discussions on here regarding support for load sense but never saw full conclusion. There are a few entries in the beta 2.17 and 2.18 asking how the ISY displays what might be considered "node2" or load sense for this device. I have verified that the recent version unit received from SH (r1.0 2910 received 2wks ago) had load led that follows load status pretty well when 2477SA2 main relay is off. Closing and opening the load circuit while the main 2477sa2 is off had the load led follow correctly. Toggling 2477sa2 relay on/off quickly can cause the load led to getbstuck on however doing a status querry by isy of 2477sa2 always resets the load led. Having 2477SA2 main relay powered on results in load led staying on regardless of load circuit state being open or closed. So we might say load status led works half of the time: when the 2477SA2 main relay is powered off. Would still be of value to have the load status node reported in ISY even though it only works during power off. There are a few scenarios where it becomes useful to know the controlled load is calling for power when the 2477SA2 is off. This would be especially useful since relay of 247sa2 does not automatically follow load sense led: I.e. Isy could be used to decision when load calls for power run a program to turn on 2477SA2 relay or send notification etc. I see from this forum thread that others have been able to manually link insteon devices to 2477SA2s load sense viewtopic.php?f=27&t=5449 Is there a way to have the load sense report in the ISY ? Thanks much J Quote
Michel Kohanim Posted July 24, 2011 Author Posted July 24, 2011 klundy/Candide, Thanks so very much for the update. Perhaps it would be best to have an intermediate release of 3.1.6 with spurious errors removed so that we can figure out what's causing the problem. I'll wait till tomorrow and then will decide (based on whatever else we can fix by then) whether or not we should have an intermediate release. With kind regards, Michel Quote
Brian H Posted July 25, 2011 Posted July 25, 2011 I will have to keep an eye on it as the Log was turned off. The lease time was set to 60 minutes. I now see the default is one day. Quote
bcall Posted July 25, 2011 Posted July 25, 2011 Hello Brad, Sincere apologies for the inconvenience. This is a known issue with ELK and the only time we have been able to reproduce it is when ELK is in programming mode (through ELK RP or other methods). We should have the ELK module out shortly which should address this issue. In the meantime, if possible, remove ELK configuration from ISY and let me know if you still experience system hang. With kind regards, Michel Hi Michel, Lol. The only reason I bought and installed the Elk at my parents was so that it could integrate with the ISY I installed there. The Elk is way overkill for their needs, but I wanted to be able to automate some things for them based on the status of alarm zones. I'll severe the connection and let you know what happens. The ISY only crashes about once every week or two, so it may be some time before I have some feedback. Also, I haven't entered programming mode on the Elk in about five months. So, if the Elk's programming mode is the only thing that hangs the ISY, maybe the Elk isn't the problem? I do communicate with the ISY using Mobilinc and also directly using HTTP commands from an app called iRule (which allows me to send HTTP commands from my iPad). But I communicate with the ISY at my house through the same two means and it doesn't ever crash. The only difference between the set up at my house and my parents is the Elk. BTW - I would have installed the ISY at their house regardless of whether it talked to the Elk (I can't imagine them living without an ISY, it just wouldn't be civilized!). Any idea when the Elk module might be ready? If this turns out to be the cause of the crashing, are there any openings in the Elk module beta program? Thanks for your help, Brad Quote
ryarber Posted July 25, 2011 Posted July 25, 2011 klundy, Thank you. Please try 750 ... you can ignore body errors (server, password, user timeouts should be fixed by increasing the timeout). ryarber, Sincere apologies. Would you please let me know: 1. Do you have ELK integrated with your ISY? 2. Are you now using 2048 SSL certificates? 3. Has anything at all changed in your LAN? With kind regards, Michel 1. Yes, I have an ELK integrated with my ISY 2. I have no idea if I'm using a 2048 SSL certificate? How can I tell? 3. I have been having router issues so I recently went in and assigned static IP's to all my devices in the house and added a wireless access point to an area that I was having poor signal. Assigning static IP's seems to have helped my router a great deal. I downloaded Mac OS X Lion and Lion server to a computer in my house and have been working on configuring it. The logs said nothing other than just lack of activity from when the ISY hung until I reset it, when there is normally a lot of chatter. Quote
elvisimprsntr Posted July 25, 2011 Posted July 25, 2011 Hello Brad, Sincere apologies for the inconvenience. This is a known issue with ELK and the only time we have been able to reproduce it is when ELK is in programming mode (through ELK RP or other methods). We should have the ELK module out shortly which should address this issue. In the meantime, if possible, remove ELK configuration from ISY and let me know if you still experience system hang. With kind regards, Michel Hi Michel, Lol. The only reason I bought and installed the Elk at my parents was so that it could integrate with the ISY I installed there. The Elk is way overkill for their needs, but I wanted to be able to automate some things for them based on the status of alarm zones. I'll severe the connection and let you know what happens. The ISY only crashes about once every week or two, so it may be some time before I have some feedback. Also, I haven't entered programming mode on the Elk in about five months. So, if the Elk's programming mode is the only thing that hangs the ISY, maybe the Elk isn't the problem? I do communicate with the ISY using Mobilinc and also directly using HTTP commands from an app called iRule (which allows me to send HTTP commands from my iPad). But I communicate with the ISY at my house through the same two means and it doesn't ever crash. The only difference between the set up at my house and my parents is the Elk. BTW - I would have installed the ISY at their house regardless of whether it talked to the Elk (I can't imagine them living without an ISY, it just wouldn't be civilized!). Any idea when the Elk module might be ready? If this turns out to be the cause of the crashing, are there any openings in the Elk module beta program? Thanks for your help, Brad Brad, I have been experincing similar ISY lockup problems going back to 2.x.x firmware. As Michel indicated, the problem can occur when using the ElkRP software to reprogram the XEP interface which requires a reboot. I can also induce the problem by simply rebooting my router or it will occur when I loose power to my home since my ISY nor my router is on a UPS. My plan is to put both my ISY on a separate power brick to not reply on the PLM to provide power and place both the ISY and router on a UPS to prevent power quality or brown outs from affecting the ISY while waiting on UDI to fix the ISY lockup issue with the Elk. I am even considering putting the ISY on a UPS with controllable outlets or network controllable power strip so I can cut power to the ISY to force a reboot when I am 1500 miles away from my home. The poor reliability of the ISY and the lack of a watch dog timer to force a restart in such instances is precisely why I do not use the ISY for any personal safety, property protection, or irrigation. I am sure UDI and it's lawyers will probably remind us once again of their disclaimers and terms of use. Elvis Quote
dennisric Posted July 26, 2011 Posted July 26, 2011 I reloaded my ISY back to version 3.1.4 and it fixed my notifications. No matter what I did in ver 3.1.5 I could not get the notifications to work. I have learned something here and will not do new firmware updates with a Beta release. Quote
Michel Kohanim Posted July 26, 2011 Author Posted July 26, 2011 Hi Brad, thanks so very much for the update and your vote of confidence. I really do appreciate it. ELK module should be out soon but, in any case, we are going to have a fix for this crash much sooner. It was completely and oversight on our part not knowing the extent to which this problem affects our customers. Again, sincere apologies. With kind regards, Michel Hello Brad, Lol. The only reason I bought and installed the Elk at my parents was so that it could integrate with the ISY I installed there. The Elk is way overkill for their needs, but I wanted to be able to automate some things for them based on the status of alarm zones. I'll severe the connection and let you know what happens. The ISY only crashes about once every week or two, so it may be some time before I have some feedback. Also, I haven't entered programming mode on the Elk in about five months. So, if the Elk's programming mode is the only thing that hangs the ISY, maybe the Elk isn't the problem? I do communicate with the ISY using Mobilinc and also directly using HTTP commands from an app called iRule (which allows me to send HTTP commands from my iPad). But I communicate with the ISY at my house through the same two means and it doesn't ever crash. The only difference between the set up at my house and my parents is the Elk. BTW - I would have installed the ISY at their house regardless of whether it talked to the Elk (I can't imagine them living without an ISY, it just wouldn't be civilized!). Any idea when the Elk module might be ready? If this turns out to be the cause of the crashing, are there any openings in the Elk module beta program? Thanks for your help, Brad Quote
Michel Kohanim Posted July 26, 2011 Author Posted July 26, 2011 Hello ryarber, Thank you. Please remove the ELK configuration from ISY temporarily. I think the combination of changing routers and ELK is the root cause of the crash. We should have a fix shortly. With kind regards, Michel 1. Yes, I have an ELK integrated with my ISY 2. I have no idea if I'm using a 2048 SSL certificate? How can I tell? 3. I have been having router issues so I recently went in and assigned static IP's to all my devices in the house and added a wireless access point to an area that I was having poor signal. Assigning static IP's seems to have helped my router a great deal. I downloaded Mac OS X Lion and Lion server to a computer in my house and have been working on configuring it. The logs said nothing other than just lack of activity from when the ISY hung until I reset it, when there is normally a lot of chatter. Quote
Michel Kohanim Posted July 26, 2011 Author Posted July 26, 2011 Elvis, I had a hard time deciding whether or not to respond to your post. You have all the right in the world to be upset and I have already stated that not resolving the ELK issue was a complete oversight on our part. It shall be fixed in the next beta release. This said, your post gives the impression that we had designed and promoted ISY for personal safety/property protection and now we are hiding behind our lawyers and disclaimers. It does not require lawyers and disclaimers to clearly and unequivocally state that ISY IS NOT and WAS NOT designed with those applications in mind. Period. As far as reliability, your post gives the impression that you have other reliability issues above and beyond ELK. If so, please post them so that we would have the opportunity to investigate and fix them. If not, I'd appreciate it if you would not make general statements. As far as watchdog timers, I do not wish to get into a philosophical discussion. In our world, watchdog timers are good for hiding bugs (if something fails, reboot). Ideally, we would like to fix bugs and again I apologize for missing the ELK bug. With kind regards, Michel The poor reliability of the ISY and the lack of a watch dog timer to force a restart in such instances is precisely why I do not use the ISY for any personal safety, property protection, or irrigation. I am sure UDI and it's lawyers will probably remind us once again of their disclaimers and terms of use. Elvis Quote
elvisimprsntr Posted July 26, 2011 Posted July 26, 2011 Michel, I am not upset, just disappointed. In fact I think the ISY is an excellent device, when not locked up. I have my whole house automated to the point where I almost never need to use the light switch or even pick up a TV remote to change a TV channel. And when I do, I pick up my iOS device running eKeypad Pro or Mobilic HD or Redeye apps. Unfortunately, the ISY seems to lock up at least once a week, or as I have indicated, reboot my router, Elk, or power goes out at my house. When it does lock up, I am usually 1500 to 2500 miles away from home and unable to remove power to reboot the device. Becasue Brad expressed a concern since he uses his ISY for irrigation, I merely wanted to let him know he is not the only one experiencing similar behavior and what he might be able to do to reduce the occurrence. Hopefully, the next beta will address the lock up issues. If not, perhaps you can advise what information I can extract from the ISY to help diagnose the problem. Since I have to reboot to regain access to the device, I assume that most of the diagnostic information is lost. Perhaps there is a JTAG or serial interface, or something else that can be used to collect information. I'm out! Elvis PS. I am sure there is a functional equivalent for whatever CPU/hardware the ISY uses, but the ISY seems to fit the definition of when to use one. http://download.microsoft.com/download/ ... dtspec.doc Elvis, I had a hard time deciding whether or not to respond to your post. You have all the right in the world to be upset and I have already stated that not resolving the ELK issue was a complete oversight on our part. It shall be fixed in the next beta release. This said, your post gives the impression that we had designed and promoted ISY for personal safety/property protection and now we are hiding behind our lawyers and disclaimers. It does not require lawyers and disclaimers to clearly and unequivocally state that ISY IS NOT and WAS NOT designed with those applications in mind. Period. As far as reliability, your post gives the impression that you have other reliability issues above and beyond ELK. If so, please post them so that we would have the opportunity to investigate and fix them. If not, I'd appreciate it if you would not make general statements. As far as watchdog timers, I do not wish to get into a philosophical discussion. In our world, watchdog timers are good for hiding bugs (if something fails, reboot). Ideally, we would like to fix bugs and again I apologize for missing the ELK bug. With kind regards, Michel The poor reliability of the ISY and the lack of a watch dog timer to force a restart in such instances is precisely why I do not use the ISY for any personal safety, property protection, or irrigation. I am sure UDI and it's lawyers will probably remind us once again of their disclaimers and terms of use. Elvis Quote
Michel Kohanim Posted July 27, 2011 Author Posted July 27, 2011 Hello Elvis, As I mentioned before, you have all the right in the world to be disappointed. As a matter of fact, I am quite disappointed at ourselves for letting this bug live without addressing it sooner. There are no excuses for this and it shall be fixed in the next release. We do not need any debugging information as we know precisely what's causing the system hang. Please do bear with us for a few more days and we'll have it fixed. With kind regards, Michel Quote
backinthelab Posted July 27, 2011 Posted July 27, 2011 Just wanted to add myself to the list of -140005 CLI-WBug errors. They began on 7/20, which I think is when I updated but not sure. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.