elvisimprsntr

I just requested my replacement. My guess is they update units as they come back and ship them out to different customers. The downside of non-field reprogrammable hardware.

I have a v2.0 adapter and don't seem to have the communication/lockup issues everyone is reporting. Just curious what the communication issues are and with what version.

Try using a different time server (us.pool.ntp.org) Also try a city not so close the time zoneline. Not sure if the ISY DST determination is look up table or is formula based, but I have seen formula based implementation get it completely wrong, or change a week prior or late. If the time is correct after this Sunday, we will know it is formula based or the offset is wrong for your city.

I don't have flex power enabled.

why does the ISY keep making requests to Above Net Communications (64.124.109.237) servers? is this for weather bug?

confirmed the beta 10 still locks up when rebooting the Elk XEP.

sorry to report that rebooting the Elk XEP once again causes the ISY to lock up

according to Wes "UDI broke UPnP auto discovery in the .8 and .9 firmware releases that can lead to his issue." I believe this will be fixed in .10

for what its worth, I use us.pool.ntp.org with a static IP address and router with DNSMasq enabled.

Another data point.... I upgraded to 3.1.9 RDPed into my Windows box over a 3G connection from my iPhone without any problem, clearing Java cache as the procedure requires. I've also used Mobilinc without any problems, both VPNed in to my home and using external WAN IP address/port forwarding, and I am 1500 miles away from my home. I've also used Mobilinc HD on my iPad2 from my hotel. I did not change any ISY settings or devices, nor did I perform a restore from backup. Elvis

not sure if this answers your question, my router has DDNS capability which I use no-ip.com and port forwarding in my router. works like a champ. my router is running open source dd-wrt.com firmware.

the difference is in max devices and programs. http://www.universal-devices.com/99i.htm Elvis

There are quite a few available for both the iPhone and iPad, but the two I highly recommend are the following: 1. eKeypad series of apps. A number of them are targeted apps for a specific purpose at lower price points, or you can just get the Pro version and get all the features in a single app. Supports both the ISY and Elk security system if you have one as well as IP cameras. http://www.ekeypad.net/eK_Family/Applications.html 2. Mobilinc series of apps. There is is a free lite version which you can test it out. The developer also has a native iPad version that is really slick. The developer plans to add IP camera and Elk support http://www.mobileintegratedsolutions.com/ While they may seem pricey, when you consider the price of a high end orbiter home controller is in the thousands, they are both bargains. Both are excellent apps and both developers provide excellent support. All the other INSTEON apps do not come close to the quality and finish of these apps. My recommendation to you, if you have or plan to add the Elk security system the eKeypad supports both in a single app. If you only have an ISY, go with Mobilinc HD universal app. Elvis

Upgraded this morning RDPed into my local W7 machine. Pleased to report the messaging issue UDI and Wes isolated fixed the keypadlinc status issue. Nice work! Elvis

OK. Thanks. Elvis P.S. Although I already regression tested the other scenerios in which I could previously cause the ISY to lock up, I am very pleased to report I had my first power outage during an electrical storm and the ISY did not lock up when connected to the Elk. Thanks for all your hard work and support.

Michel, Any chance we will see 3.1.7 this weekend? I'm looking to regression test the keypadlinc status issue for Wes before I hop on a plane Sunday morning. Elvis

Only the units displayed for the temperature RATE is not correct. Is DegF. I assume it should be DegF/h

Weatherbug temperature rate units are not correct.

Assuming your Elk is already running the latest firmware (most recent July 2011) and you have the Elk and ISY configured to communicate to one another, older ISY firmware (< 3.1.6) would lock up when you do one of the following: 1. Use the Elk RP software to change a XEP setting that requires a reboot or you can manually reboot the XEP 2. Reboot your router that is between your ISY and Elk. While I am sure there may be other ways to have induced the problem, if your ISY does not lock up using the above methods, then I believe the problem is resolved. Elvis

Michel, Thank you for addressing the Elk lockup issue! I confirmed the ISY does not lockup in all the scenerios i previously could induce the problem. Elvis

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

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

Thanks. Some people use their ISY for monitoring water, temperature, carbon monoxide, security, control sprinkler systems, etc. All of which could potentially cause loss of life or damage to property if the system fails at the most inopportune time. If UDI thinks of any particular problem in that light and categorizes the problem based on criticality, this might help prioritize changes. Thanks again. Elvis

I have not tried 3.1.5, but i did not read anything in the change log that would lead to beleive it would fix the problem. I would try 3.1.5, but I am 1500 miles away from my ISY which is currently locked up. Seems like a hardware WDT if implemented to trap register/program state would be helpful in addition other types program errors (i.e. divide by zero, overflow, etc.) The more end user programming cabability you provide, the more opportunity to induce these types of problems. But then I come from an industry of mission critical, human rated applications.

Ok I've been putting up with an issue with the isy firmware going back to 2.x.x builds and I know the problem exists with 3.1.4. The problem has to do with the connection to the Elk M1 gold. When the Elk XEP Ethernet module is manually rebooted (typically after tweaking the tcpip settings for example) this causes the ISY to lock up. I can also cause the isy to lock up by simply rebooting my router. The problem also occurs when I loose power to my home. My isy and router are not on a ups. Config: 1. Elk m1 gold with all the latest firmware from 2/21/2011. Elk configured with static ip address, DNS, etc 2. Isy 99i pro ir with 3.1.4 or any prior release of firmware. Isy configured with static ip address and communicates to the elk over the unsecured port as required. Exported the isy lighting for import into the elk. Which all usually works well. 3. Wired Ethernet connection between isy and elk through e3000 router running dd-wrt firmware. Steps to duplicate: 1. make sure elk is running. 2. Reboot router. Wait 2 min. 3. Unplug isy power and reconnect 4. Pick any one of the following: a. Reboot elk xep interface b. Reboot router It seems like for what ever reason the isy completely locks up. Does the isy have a watch dog timer? Or is just the networking interface getting locked up? Is there a way to remotely reboot the isy by sending WOL commands or equivalent to the isy? Thanks in advance Elvis