I finally managed to get an iTachWF2IR unit connected and successfully configured using the UC provided Global Cache integration on the same network as the remote. I am trying to use the iTach to send IR commands more effectively than the Remote 2 which requires my disgruntled wife to standup and move to the front of the TV to turn it on.
Even though I have used the database previously and converted code sets for successful IR use, I’m stymied on the integration SendIR Code values to insert on the Web configurator (software 2.2.4). The GitHub description is not helpful regarding what contents should be input into the WebConfigurator SendIR values, including if native GC code or pronto hex. They are:
- Emitter (this I can figure out if it is 1-3 on back)
- Format (code1, hex code 1?)
- Port (?)
- Repeats (assume number of repeats….)
I have tried many educated guesses (e.g., strip off values before the IR code, etc.) This should be pretty straightforward and documented - or why have an integration.
Please help on what these values are/should be. Discord and GitHub has not yielded the answer.
With some retries, actually many, it became clear that NOT doing the expansion of the fields first. In order add the HEX code (no double quotes) THEN expand the SendIR entry THEN change the format to HEX, and edit retries optionally (default is 1). I did not change PORT (default is blank).
Hopefully this helps someone. It works better than my custom ESP32 devices (with Albinator’s invaluable help) or the ridiculously places and cabled dock, which never worked reliably.
I did have to get the WIFI2IR iTach for the integration to be discovered by the remote. Smarter people with docker or NAS may have been connect it via wired LAN.
It would be nice if these simple things would be documented vs hours of frustration, particularly since effort was put into create the integration.
One slight tangent is the browser and popup blocking will make WebConfigurator behave differently, so YMMV.
I just got an iTach IP2IR unit and have some questions. First, the port function in the UC integration doesn’t seem to work - the iTach will always use port #1 no matter what value I enter. Have you had the same experience? Also, regarding the codes, did you use the iLearn app to learn the commands or did you just download them from Global Cache? I assume the latter given your description of how to get the hex values? I have to learn the values so just setting the format in iLearn to Hex and the UC integration seems to take it.
Any help would be appreciated - TIA.
I did use the global hex database. It is a send command which i do a couple times woth delays to make sure the discrete code (in my case primarly the samsung tv) to trigger with the blaster (not the other emitters). I believe it is port 1 as default) attached to the top of the iTach unit. The iLearn was a little cryptic as well as I think I had to run it in a Windows 8 emulation to set up the device, other than that I stopped using iLearn.
So after setting up the Global Cache integration which found the unit on the same wireless network and subnet as the remote, the iTachxxx SENDIR command is just the content of the HEX code from Global cache within the parenthesis. It is non-intuitive where the vale is set, but for example the Samsung Discrete Power on is
0000 006D 0000 0022 00ac 00ac 0016 0040 0016 0040 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0015 0016 0040 0016 0015 0016 0040 0016 0040 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 071c
directly from the Global Cache individual entry. You can download the full list of commands from Global Cache for a device, but you need to manually enter the hex string into the sendIR command. You also have to remember (or capture) the code related to the action, because it is not self documenting.
So for each activity which uses the TV I blast the SendIR in each ON Sequence (and the corresponding discrete power off in the off sequence.
On an emitter port I do a similar command with my Pio receiver, but the blaster on the iTach port 1 is more reliable.
I think I had more info in the Discord IR conversation, but once you get one sequence triggered it’s easy to figure the rest. It still bothers me that a built in integration is so undocumented. I hope this helps at least a little.
So I got my learned codes to work (yeah) on port #1 but I can’t get it to send the commands out of port #3. There seems to be a bug in the UC3 integration - no matter what value you put in the port field, it uses port #1.
To get it to stick I had to tab after the port number entry to go past it and subsequently going back and check. Didn’t stick most of the time. Irritatiing
I did something like that and it always displays 3 when I go back and check the button, but let me try again. Thanks.