DemoPad.com

I have most of the program done, I learned most commands from my original remotes using the WF2IR unit.

Often, I will go into Demopad on my iPad and push a button, it sometimes takes up to 3 seconds to see a change on my equipment. If I keep pushing the button to see a result it will all of a sudden spit out all the commands doing much more than I wanted.

Another example is the volume for my processor. I set a push and hold command with tenth of a second intervals. Often it goes much slower than that, I release the button when it is at the volume I want but it will keep going for many more seconds.

Any ideas?

It sounds like the Wifi connection to your iTach is not 100%. The app will attempt to resend any commands which fail the first time - which explains the 'catching up' bit. Recommend moving the WF2IR to somewhere where the signal is stronger & seeing if you still experience the problem.

I may be able to move it a couple feet closer but that is it. I ran the blaster in my wall and have the eye on top of my rear speaker where it will hit my rack. I also have 1 emitter ran in the wall and on the plate of my Lutron IR switch, the cable lengths are already pretty much maxed out. The WF2IR unit is only about 20-25' from my B/G/N router.

Try moving it much closer (disconnect the IR emitters temporarily) just to see if the IR LED flashes in line with the button pushes, or whether you still get the delay - this will tell you whether wifi signal is the problem here. I'm also assuming you have good wifi connectivity on your iPad/iPhone.

Really? 20' is getting to be too much for the WF2IR? I know it is B but that is pretty poor, I would've gotten the IP2IR if I knew that.

I will try experimenting while watching the red LED.

Could I use these to get more length?
http://www.ebay.com/itm/12-ft-3-5mm-Mal ... 35bc4cdd41

Yes, but get the mono versions, not stereo for Global Cache IR emitters.

Moving the WF2IR closer would just be to test initially - there are many factors involved in wireless communication - distance being one, but there is also external interference / home insulation etc etc - just trying to rule distance out, as it is the easiest thing to test - just plug in the WF2IR nearer to your access point / router & see if it responds quicker. I'd also look at changing the wifi channel you are using, in case there is any interference there. A wireless scanner (eg Wi-Spy) is useful in situations like this...

Also try using iTest from a computer hard wired to the network, as it might be the connection between your iPad/iPhone and the network, rather than the connection from the WF2IR to your network...

I'll have to play with it some more. Yesterday I left it in its current location and the LED's blinked almost immediately as I used DemoPad. I only had a few minutes to play with it so I will try again...

DemoPad wrote:Yes, but get the mono versions, not stereo for Global Cache IR emitters.

Moving the WF2IR closer would just be to test initially - there are many factors involved in wireless communication - distance being one, but there is also external interference / home insulation etc etc - just trying to rule distance out, as it is the easiest thing to test - just plug in the WF2IR nearer to your access point / router & see if it responds quicker. I'd also look at changing the wifi channel you are using, in case there is any interference there. A wireless scanner (eg Wi-Spy) is useful in situations like this...

Also try using iTest from a computer hard wired to the network, as it might be the connection between your iPad/iPhone and the network, rather than the connection from the WF2IR to your network...

I'm not really getting anywhere...
What do you mean by changing the WiFi channel? I don't have the money to purchase WiSpy, they are quite pricey.
I downloaded iTest, connected to the IP of my WiFi unit, pasted in a command I learned and hit the send literal. I got the same ASCII response as I sent (no error) and got the hex conversion. It took about 1/3 of a second to see the result in iTest after hitting send.
I also have thought about soldering in extension wires but before cutting the mono plugs off I wanted to try some other things to be sure it will fix it.

I have had this issue quite often, including by own setup. I have found that 90 percent of the time, it is the network - cheap wireless routers have been my biggest problem, even when hardwired using IP2IR iTachs, the cheap routers have given us problems. If it is a programming issue, it will happen constantly (I've been there many times), but if it is intermittent, it will pretty well much be network.

We started a project using a "top of the line" home Belkin ADSL router (cust supplied) and our client constantly had intermittent delays. We updated their system to a Ubiquiti network and they have not had issues since....touch wood... If you can borrow a decent router from a family or friend, you can at least rule out your own network.

I thought about that too, this is the router I currently have. It was provided by Qwest which is now Century Link...
http://www.actiontec.com/products/press ... hp?pid=200

You can also change your repeat times for press and hold, instead of say "repeat command every 0.10sec" change it to 0.30 or more if required. This may help and hopefully keep your volume going up and down at the same speed. If you look, you will see the first lot of commands when you hold the "press and hold" button down go through fast (if using the Global Cache emitters), then when you release the speed in which the following commands are sent are slower. I hope this also helps

Well, I'm still having this issue. I moved the WF2IR closer, it is now about 10' away from my router. I also made my own IR blaster because the one that came with the WF2IR went out on me. It seems to mostly be the volume which is set for a repeat command. The only thing I can think is to change it back to single action push. The thing that is holding me back doing that is if you push the button multiple times really fast it will do the same thing and keep sending signals long after you stop pushing the button. I looked at getting a different router for my Centurylink provider but they are very selective. I have the Q1000 now, Centurylink said the router must be VDSL2 if I buy another one. I looked and found that they are pricey. I did try changing my router channel, tried 1, 6 and 11 and it did not seem to make a difference.

Have you tried changing your repeat command to more than what you have set it too? Add at least .15 seconds to the command and go up from there until you have found the happy median to the repeats.

I did play with that but not since I moved it closer to the router. I can try that again but like I said if you manually push it multiple times quickly it will do the same thing.

How did you get on? I hope you solved the issue. Another little thing to check is in the "Device" window of your iTach.....make sure that "disconnect after each command" is NOT ticked, this will also help with repeating/delayed commands.