elvisimprsntr

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

Michel, Sorry about my delayed response, but I have been on business travel. To answer your questions: 1. Yes i have both the network and weather modules installed. I have some simple http and tcp network resources set up to allow me to create programs to control my Global Cache IP2IR and my IP2IR blaster (thinkflood redeye) which supports http messages to issue IR blaster signals. The programs are configured to send network resource messages upon time of day events. I don't have any web other other network resources configured. 2. I did not try to to monitor what would happen if I manually turned a device on since I was pressed for time before traveling. 3. Unfortunately, once I tried to change a light from within the admin console the ISY would lock up and I would have to force a reboot by removing power. I assumed the errors logs are stored in RAM and would be lost upon power cycle. As i said before ALL my other IP devices ALL work correctly on the LAN side of the client bridged router. This includes a W7 PC, slingbox, NAS storage drive, apple TV2, and Denon AV receiver. All are configured with static IP addresses with my primary router acting as the DHCP and DNS server, with DNSMask enabled. If you can provide me a list of other things to capture, I can try.

upgraded from 2.8.14 without any problems following the very specific instructions. although I have both a mac and windows 7 machine, i always use windows for upgrades. Not sure if the following is specific to 2.8.16 or not, or what forum might be more appropriate, but here it goes... I have two routers using DD-WRT client bridge so i can relocate my IT equipment. when I connected the ISY-99i to the client bridged router, I had all sorts of problems access the ISY-99i admin console. I could log in, but once I clicked on an action to turn a light on the unit would stop communicating on the network which required me to reboot the ISY. All my other IT equipment works fine on the LAN side of the client bridged router. Hopefully it's just some obscure router setting that is causing the problem. Any suggestions would be appreciated. Elvis

This time I upgraded EXACTLY per the instructions. Version number rolled first time. Everything thing seems to be working properly, except learning new IR codes. BACKGROND 1. because the default codes conflicted with other IR codes, I had previously deleted the default codes and picked a Philips remote and used it to send the AUX digits 0 through 9. Of course I had to modify the default codes download to my Harmony remote to match as well. Since then I have been using my harmony remote for nearly a year to control lighting scenes without any problems. LEARNING MODE PROBLEM 2. Now I am trying to get the ISY to learn some additional codes. First I used the new remote to make sure the codes did not conflict with the existing codes learned by the ISY. 3. Then i proceed to follow the instructions entering learning mode and depressing the button on the new remote I want the ISY to learn. The ISY indicated that it as entered learning mode, but when i depress the buttons, they are not added to the IR code list. The remote I am trying to get the ISY to learn are the buttons off a Comcast DTA remote. UPDATE: I even tried to get my ISY to learn other codes from the Philips TV remote I used to program the ISY originally and of course I verified the previously programmed codes do still work. QUESTIONS Is there a problem with 2.8.12 or is thee some limitation that prohibits the ISY from learning codes from a Comcast DTA remote? Elvis FYI, I have the network and weather modules installed UPDATE I think i found my answer. I have read the Comcast DTA uses UEI XMP protocol. I think the ISY only supports RC5, not RC6 or any other protocol. Not sure if this is a hardware or software limitation.

i don't recall it being that complicated before. I guess i missed a number or steps.

i've been updated my ISY the same way I have always done per the instructions, which the version reporting problem started occurring with 2.8.10 betas. 1. backup system 2. manually update 3. exit all browsers and download managers 4. open java control panel to clear cache 5. clear browser cache 6. launch browser and enter url http://192.168.xx.xx/admin I have tried to perform upgrades from safari on a mac successfully in the past, but following the same procedure when i launch the admin console it hangs or never opens the credentials dialog and had to kill the safari process. only upon a second launch of safari of the admin console does the creds dialog get displayed, but then some of the isy pages are not displayed properly. this seemed to start happening with 2.8.10 betas. thus i have resorted to only performing updates via my W7 64-bit client. I am starting to wonder if there is a compatibility problem with 64-bit OSs running 32-bit java, and the ISY update process. FYI, I bricked two Elk M1 Golds trying to perform firmware updates using the ElkRP application running on my W7 64-bit client. I have received reports from others about other problems using the Elk RP application on W7 64-bit as well. I've given up making Elk firmware updates until i create a windows xp VM for such tasks.

i upgrade from 2.8.10rc6 to 2.8.11 and the about screen still says 2.8.10. I upgraded from a W7 64-bit client and cleared java cache after upgrade. UPDATE: I upgraded a second time and now the about screen says 2.8.11. Seems like the same thing happended to me with several betas of 2.8.10

my first attempt to update to 2.8.9 appeared to work successfully, then i read the posts concerning the version number. I repeated the upgrade once using the same file, then again after re-downloading the file which seemed to take. I can't recall if I also cleared all browser cache in addition to using the java control panel to clear java cache the second time. config: W7 Ultimate 64-bit, java 6u22 32-bit.

A program that is constantly triggering or a link issue or clear java cache? http://www.universal-devices.com/mwiki/ ... r_Messages

Michel explained this a number of posts back: they are there so you can say, for example, IF Thermostat Cooling is On .... I'm not sure why that couldn't be just one of the many tests that you could do on the main thermostat status. Edit: Oh, now I understand, you can have put the device in as a controller for a scene so you could, for example, have a light go on when the Thermostat went to Cool mode. Not sure why you would want to do that but it is a capability of the v2.0 thermostats that UDI made accessible to us. I guess having some KPL buttons show you when heat or AC is running might be nice. Not sure yet why anyone would want to add it so a scene either, unless one needs to open a damper or turn on a secondary HVAC device. I'm considering removing the device and using the manual "add insteon device" method, which I did initially and didn't create 4 entries. I had less issues that way.

I sent UDI support an updated test results matrix that inlcudes log artifacts in case you need it. In short, FS is incorrect in ALL modes upon power up or manual query. SPs are incorrect in program modes upon power up or manual query. Elvis,

1. Regardless of the fact the tstat is not queried when first added, once power is cycled or the isy is reboot, the ISY does not restore the FS in any mode and SPs in program modes. 2. In program auto mode, when I perform a manual query of the tstat, I only see messages for ST, CLIMD/SP/HUM and do not see CLIFS/SPC/SPH. 3. In auto mode, I see query messages for ST,CLIMD/SP/SPC/SPH/HUM, but not CLIFS 4. I do not see where these states can be queried individually in programs. Only query as a device. It appears to me that not all values are queried in all modes. Elvis

OK, I retested everything after using the start linking method. The significant issues I noticed are: 1. Fan state is now commanded every time a mode change is made. This leads me to believe that CLIFS is not an item that can be queried. Unfortunately, upon power up, fan state is not correctly reported in any modes. 2. Set points will be zero upon power up and even after a query in any of the program modes. Thus this leads to confusing and misleading information in third party apps like eKeypad ISY and iLinc Pro the way it is currently implemented. The question is can the ISY query CLISP,C,H values even in program modes? 3. Wasn't fan mode to be removed? Questions If this is the way it works given some technical limitation, then is the work around to execute a program upon power up to: 1. Command the mode to auto and fan state to auto upon power up at least once, then set the mode and fan to your preferred states to get the ISY and tstat to sync up? 2. Or is there a way to query/report the CLIFS, CLISP, CLISPH, CLIPSC values during a query upon power up and/or when mode changes are mode? Any other ideas? Thanks, Elvis