There are a handful of reasons why a unit would not show up on your iHelp window.
One: GC-100 beacons broadcast every 60 seconds, and can therefore take up to one minute for iHelp to register the unit. If you would like to force a beacon broadcast, execute iHelp on the networked PC and then power up the GC-100. The unit will broadcast a beacon upon network connection negotiation.
Two: iHelp requires a network resource, in that it joins the multicast group in order to receive unit beacon messages. If your firewall is blocking iHelp from joining the multicast group, it would be unable to find the unit.
Three: Your PC is connected to multiple network interfaces simultaneously, causing iHelp to choose the incorrect one and join the incorrect multicast group. Make sure that you are connected to the same network as the iTach, and that you are connected to only one network in order to confirm that this is not the problem.
Four: You have a firewall, addressing issue or network setting which is blocking traffic at some juncture. As this is a relatively open statement, there are a few places that need to be checked. Router settings (UDP traffic, routing, subnetting and addressing) should be checked, as well as any connected network switch (in line between the iTach and the networked PC), and dedicated firewall programs.
If you continue to have this problem, using a different PC on the network to attempt to discover the unit will give you helpful information. Either the unit is not discoverable from both PCs, meaning that this is probably a network issue, or the unit is discovered by the second PC, meaning that the issue has to do with some sort of setting on the first PC.
If these suggestions did not help, please send an email to email@example.com and we will make sure to get you up and running as soon as possible.
Is there a Mac version of iHelp?
Yes there is. Follow the link below to the website of the developer who has created Mac beta utilities for testing.
Just to let you know that at the moment only iHelp is still in Beta, because I first want to add the firmware update functionality for the iHelp. The rest is now in normal release as I haven't received any problems with the applications. But for now I'm very busy with other things...
I can not get my gc-100-6 to be seen by iHelp on either of two computers. I was able to connect via the browser although it is hit and miss. About 1 out of 4 refreshes will result in a web page. Once the page is viewable I am able to configure, but I did not make any changes other than attempting to use other IP addresses to get it noticed by iHelp. I tuned off the firewall. The PC I used has been dynamically assigned to 192.168.1.100. Still it does not show up in iHelp.
If your GC-100 pre-dates the 3.0 firmware revision, your unit will not contain the discovery beacon, so it will not show up in the iHelp utility. Since you know the IP address of your unit, this should be of no concern to you.
It sure would be nice if I could enter the IP address of my GC100 into iHelp since i'm not "looking" for it and connecting to the network it is on with my computer is cumbersome.
Since iHelp was designed to discover our hardware on the network, there is no need to use iHelp since you already know the IP address of the unit. If you need to configure the unit's settings, input the unit's IP address into a web browser such as internet explorer to alter the network and connector settings.
I have a new FLEX (fimware 710-3000-03).
I can access the iTach flex on 192.168.1.71 (the .70 is already taken by an iTach WFIR), but...
1. I cannot have iHelp see the FLEX device (but cannot either see the WFIR, that perfectly works with Roomie Remote). How could I eventually upgrade my "old" FLEX firmware?
2. The FLEX web configuration doesn't expose any option to setup the FLEX serial cable that I've bought (it has only two options to configure IR blaster and tri-port IR Cable): how could I setup my serial connection?
I'm using Win7/64bit, with a single ethernet connection.
I too can not get ihelp to see my wired ip2ir unit. I can use my browser to see the setup pages without a problem. How do you update the firmware in this situation?