iTach - Only Power Command sent

Hello,

I’m trying to setup an iTach device to control a TV via IR with commands from the Global Cache Database. The power command works, but the other commands aren’t even being sent (emitter not blinking).

I’ve tried using remote.send_command (service dev tool) which also works fine for on, but doesn’t work for the other commands. I enabled info logging and see the below error via logging (IP sanitized) when running the other commands.

2019-08-17 18:02:51 INFO (SyncWorker_13) [pyitachip2ir] Response:ERR_1:2,007
2019-08-17 18:02:51 INFO (SyncWorker_13) [pyitachip2ir] Response code:-7
2019-08-17 18:02:51 INFO (SyncWorker_13) [pyitachip2ir] tryConnect:192.168.1.xxx:4998
2019-08-17 18:02:51 INFO (SyncWorker_19) [pyitachip2ir] tryBeacon:
2019-08-17 18:02:53 INFO (SyncWorker_8) [pyitachip2ir] checkConnect: connected

Here is the iTach section from the configuration.yaml

remote:
 - platform: itach
   host: 192.168.1.xxx
   devices:
     - name: Master Bedroom TV
       connaddr: 2
       commands:
         - 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: "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: "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"
         - name: "INPUT ANTENNA"
           data: "0000 006D 0000 0022 00ac 00ac 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0689"

Your config looks ok. It does not have modaddr: though. It’s optional but may be required by your iTach.

Par of my config:

- platform: itach
  host: 10.1.1.19
  devices:
    - name: Cinema Amp
      modaddr: 1
      connaddr: 1
      commands:
        - name: "DSP+"
          data: 0000 006D 0000 0026 0154 00AA 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 0015 0016 0015 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 0015 0016 0015 0016 003F 0016 003F 0016 003F 0016 0015 0016 003F 0016 0015 0016 003F 0016 003F 0016 0015 0016 003F 0016 05B5 0154 0055 0016 0E35 0154 0055 0016 0EC6

And a script to send the command:

cinema_amp_dsp_up:
  sequence:
    service: remote.send_command
    data:
      entity_id: remote.cinema_amp
      command: "DSP+"

I used to have this problem:

https://github.com/home-assistant/home-assistant/issues/17744

Might be worth trying a home asssitant restart.

Thanks for your reply. I’ve definitely tried restarting.

Do you have any additional commands you are sending to your Cinema Amp? I’ll try adding modaddr to see if it makes a difference. I didn’t think it would since the Power On command works.

Yep. Lots of commands. All work.

Added modaddr but no change in behavior.

Do you mind me asking what version of Home Assistant you are on? I’m currently on 0.97.1, going to try updating to 0.97.2.

Edit: Upgrading to 0.97.2 didn’t fix the issue.

I’m on 0.97.2 and it has been working for over a year of previous versions.