core: iTach remote device not starting correctly

Home Assistant release with the issue:

0.80.3

Last working Home Assistant release (if known): 0.78.x

Operating environment (Hass.io/Docker/Windows/etc.):

HassOS, raspi 3b Component/platform:

https://www.home-assistant.io/components/remote.itach/

Description of problem:

When restarting HA more often than not, one or more remote devices defined for the iTach component will not work (will not send IR command). The device that fails is random. A restart of HA may correct the issue (all devices work as expected) or a different defined device may stop working. Other devices defined for the iTach component do operate as expected so it is not the component failing as a whole.

This is a problem with the HA component as I can still send a command directly to the non functioning device using putty to communicate directly with the iTach unit.

I note that quite a bit of ‘tidy up’ work was done on this component about the time the issue appeared. I have removed the redundant “device:” requirement but this made no difference.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

script.yaml

lounge_tv_menu:
  sequence:
  - service: remote.send_command
    data:
      entity_id: remote.lounge_tv
      command: "Menu"

remotes.yaml

- platform: itach
  name: Lounge
  host: 10.1.1.18
  devices:
    - name: Lounge TV
      modaddr: 1
      connaddr: 1
      commands:
        - name: "Menu"
          data: "0000 006D 0000 0044 0158 00AA 0016 0040 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 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 0040 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0614 0158 00AA 0016 0040 0016 0040 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0040 0016 0015 0016 0040 0016 0015 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 0040 0016 0015 0016 0015 0016 0040 0016 0040 0016 0015 0016 0ECF"

Traceback (if applicable):

No errors in log.

Additional information:

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 1
  • Comments: 47

Most upvoted comments

Next step would be to go to “configuration” and “server controls” and “check configuration” to make sure there is not any errors in your yaml.

Lastly, “restart” to restart Home Assistant.

Then, you should be able to go to “Developer Tools” and “Services”.

Service is shell (and then should auto populate).

You can call for this in an automations by using “call service” under “action type”. Service is “shell” and again - this should auto populate.

Sorry to be long winded with the codes. I wanted to help you get up and running quickly in case you have any of this gear.

Good luck!

The issue has been identified and a fix has been created. It just needs someone to implement it in the core integration.