Core: Harmony Remote component stops Home Assistant from loading if hub is not reachable

[nkgilley]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.36.1

Python release (python3 --version):
3.5

Component/platform:
remote.harmony

Description of problem:
If the hub is not online, home assistant will not start

Expected:
Home Assistant should start and log an error

Problem-relevant configuration.yaml entries and steps to reproduce:

remote:
  - platform: harmony
    name: Basement
    host: 192.168.1.131
    activity: Watch TV

Traceback (if applicable):

17-01-19 17:53:52 INFO (MainThread) [homeassistant.components.remote] Setting up remote.harmony
17-01-19 17:53:52 DEBUG (Thread-11) [homeassistant.components.remote.harmony] Loading Harmony platform: Basement
17-01-19 17:53:52 DEBUG (Thread-11) [homeassistant.components.remote.harmony] Calling pyharmony.ha_get_token for remote at: 192.168.1.131:5222

[RePeet13]

I can confirm I'm having the same problem still, in version 0.37.1
I also have an easier way to reproduce: Just set the ip where it looks for the hub to something that isn't the hub. (I ran into this problem because my router reset and lost my static leases)

[dpeet]

Same issue here, Same wrong IP messing things up. I only got to "Setting up remote.harmony" before it hung.

[RePeet13]

I know some components (like ecobee and the automatic part of the plex component) pop up a configurator when they aren't correct, is that approach a good candidate here too? To alert the user there's a problem and a common solution is check the IP address

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

[RePeet13]

Yes this is definitely still happening.

• I just updated to the latest (.43), restarted Hass, and it took 5 minutes (with a good config, probably because it was the first startup after being updated).
• I changed the config so that it had the wrong IP for Harmony, restarted, and in 10 minutes it did not start.
• I restarted Hass again, and it still did not start in 10 minutes.
• I reverted the IP change (so it was correct again), and restarted Hass, then it started up in 30 seconds.

[RePeet13]

The best part is that there is no indication this is the problem. There's no error message in the log or systemctl status output. I only know this is it by guessing and checking

[antsar]

Working on this.

[Nex81]

Problem still exists after Hassbian update to 0.46.

In case of harmony hub has no power connection following error will be written on startup:

2017-06-04 23:28:59 ERROR (MainThread) [homeassistant.components.remote] Setup of platform harmony is taking longer than 60 seconds. Startup will proceed without waiting any longer.

But Home Assistant do not start.

[antsar]

@Nex81, that seems to be fixed by #7970 which was released with 0.47.