Originally Posted by wkearney99
You MUST NOT have multiple devices on the same network using the same IP address. It's not allowed, by TCP/IP standards. The problem is there's a lot of 'behind the scenes' communication that occurs that translates the somewhat user-friendly dotted quad of an IP address into the downright cryptic 16 digit media access control address of the hardware itself. When something needs to send or receive packets over the network it has to know exactly which hardware addresses to use. There's no support in the protocol for more than one device to use the same IP address. Doing so can either cause immediate collisions and errors, or intermittent nonsense leading to mysterious timeout problems.
So first thing you HAVE TO DO is STOP using the same IP address for the phone and the tablet.
That this 'may have always worked' does not change the requirement. Lots of things done wrong get away with not immediately failing. With networking, however, you're asking for a LOT of trouble that way (especially when wireless is involved).
Let me be clear in what I'm saying, I'm talking about the IP addresses of the devices themselves (tablet and phone), NOT the IP address that they both use to communicate with another device being controlled.
For example, tablet and phone cannot both be on 192.168.1.123. They'd each have to use their own address. But once they're both on separate addresses they could both certainly attempt to communicate with OTHER devices (each with their own IP address). So the tablet on 192.168.1.123 and the phone on 192.168.1.231 could both be configured to control a receiver on 192.168.1.32. All numbers being just examples, of course.
Where you potentially run into complications is how the target devices handle being communicated with by multiple devices. Some equipment does not react well when more than one device tries to control it at the same time (or within a close timeframe). As in, both tablet and phone should not both try to send volume up/down commands to the receiver at the same time. The IP stack of some consumer electronics devices is not always robust enough to allow that to work reliably.
You can certainly run iRule on more than one device at a time, you just need to be sensible about how the devices being controlled will respond.
Originally Posted by wkearney99
Remember, a device connecting to the network gets it's address for ALL applications running on it. Not just the iRule client software.
I don't think we're communicating. By referring to the IP address I am referring to the IP address of the iTach2 which I enter in iRule on the gateway setting of the phone and tablet iRule app and NOT the addresses my phone and tablet. I've tried to I explain this several times. Nevertheless I do not have iRule running on both devices at the same time so this discussion appears academic.....unless I've totally misunderstood how iRule works and how android devices' IP address are set. I have encountered the situation when I cannot connect to the gateway and then realize iRule is also running on another device. When I close iRule on the 2nd the 1st one's connection works.
Which brings about a larger issue. Clearly your mastery of telecommunications surpasses mine and I respect and appreciate your taking the time to try and help me. The technical requirements you've described may be second nature to you but this along with mastering the ins and out of iRule can be mind-boggling. If I were going to summarize my experiences with iRule I would describe the product as extremely 'fiddly.' When putting the system together I had to read, re-read and re-re-read the documentation, post questions in threads here and watch the tutorials many times. I also asked questions at iRule, and another site.
While others might disagree I don't consider myself as particularly thick or dull-witted. I got everything running, had five different phones and tablets working, installed insteon lighting control over each of my home theater seats controlling them with iRule on my devices and then designed and implemented a system to control several fans over my exercise equipment with feed back indicating the speeds the fans were set to. I even got iRule working with my receiver and a streaming server.
I then sold some tablets and was left with the Samsung Galaxy S4 and a 12" Samsung tablet. I never got around to re-designing the large Samsung tablet screen...the process of using a freeware package to create forty or fifty new re-sized buttons and import them into iRule online into my panels is mind-numbingly tedious. In any case they worked without any further action on my part until a few weeks ago when neither the phone or the tablet could connect to the gateway. As I mentioned the IP set into the gateway space on the devices' iRule settings matches the IP address of the iTach2 server and iHelp sees the iTach2...and I NEVER have iRule running on both devices simultaneously.
Now here's the problem; once I walk away from actively developing panels and configuring my setup the knowledge starts to go stale. Further, I have no idea where to find and reset the individual IP addresses of the S4 or the Tablet. Moreover I've never needed to know them or where to find their IP addresses let alone how to get to my router to do the things you've suggested. All I want to do is control my AV devices from a single screen on my phone or tablet. At first it was a challenge and fun and immensely rewarding to see everything work; then it became drudgery. Now I'm not sure it's worth the time to re-re-learn all the items necessary to go back just to fix it.
I really appreciate the time you all have taken to help, but with three Macs to maintain, my digital photography, genealogical research, daily cycling and maintaining a house there is no spare time to backtrack and get iRule up to snuff. Thanks again and I apologize for taking for your time.