Itach stops working

Hardware
21

Thanks so much. I have some GC100 and iTach IP2IR units, and I think the network issues show up much more on the GC100 devices… I have switched to multiple IP2IR instead, and on top of that, I’m running 2 hassio slaves on Pis… so I’ve attached 2 IP2IR on the master, and one IP2IR each on the slaves; so far I’m not seeing any problems on my install!

22

@wmaker Are your changes to pyitachchip2ir still working for you in current versions of Home Assistant?

23

Yes I still use it. I use to run this only with HA-core in a python venv, but a few months ago I switched over to a new hassio system and have adapted things to work with it. You can read more in details here:

1 Like
24

@wmaker Thanks for the confirmation. I followed the instructions and was able to change out the itachip2ir.so and reboot HA.

However, I’m still having trouble sending any command but ON, when using the Services via Dev Tools. The ON command caused the IR emitter to light up red but none of the other commands do. Any ideas on how to troubleshoot this?

YAML code for reference:

data:
  num_repeats: 1
  delay_secs: 0.4
  hold_secs: 0
  command: "OFF"
target:
  entity_id: remote.living_room_itach
25

I’ll have to admit, its actually been several years now since I set this up so I’m rusty on it.
Did you look at the HA itach documentation?
You need a “remote” in your YAML configuration. If you have it, then maybe post it and we can take a look.

26

This is what I have so far.

  - platform: itach
    host: 192.168.1.42
    devices:
      - name: living.room.itach
        modaddr: 1
        connaddr: 1
        ir_count: 3
        commands:
          - name: "OFF"
            data: "0000 006D 0022 0000 00ad 00ad 0015 0041 0015 0041 0015 0041 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0041 0015 0041 0015 0041 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0041 0015 0041 0015 0015 0015 0015 0015 0041 0015 0041 0015 0041 0015 0041 0015 0015 0015 0015 0015 0041 0015 0041 0015 0015 0015 0728"
          - name: "ON"
            data: "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"
          - name: "INPUT HDMI 1"
            data: "0000 006D 0022 0000 00ad 00ad 0015 0041 0015 0041 0015 0041 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0041 0015 0041 0015 0041 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0041 0015 0015 0015 0015 0015 0041 0015 0015 0015 0041 0015 0041 0015 0041 0015 0015 0015 0041 0015 0041 0015 0015 0015 0041 0015 0015 0015 0015 0015 0015 0015 0728"
27

This config looks good to me. I don’t know what the problem may be. Maybe as a test, set OFF’s data to be the same as ON’s data. If the IR LED lights up for both ON and OFF in that setup, then it kinda suggests its an IR code issue.

28

Circling back on this issue. You were correct, this was an IR Code issue. Some of the commands from the GlobalCache Database for Samsung have lower case letters in the hex code.

I was able to figure this out by converting the GlobalCache commands (starts with sendir) to Hex Code via iConvert, and using an online text-comparision.