HACS installing problem via integration "error: Config flow could not be loaded"

Configuration
32

I’m running HA on Ubuntu 20 via a Snap image installed through the Ubuntu software store. My steps:

  • Install HA Community Store (HACS): sudo snap install home-assistant-hacs
  • Restart HA: sudo snap restart home-assistant-snap
  • Manually add connections: sudo snap connect home-assistant-hacs:components home-assistant-snap:components
  • Restart HA: sudo snap restart home-assistant-snap
  • Verify connections were configured: snap connections|grep hacs
  • Clear your browser cache (see: Initial Configuration | HACS)
  • Go into the web UI > Integrations > Add Integration > Search for “HACS” and install
  • Restart HA: sudo snap restart home-assistant-snap
  • Launch HACS. You’ll be prompted to connect to Github. Understand that this gives your HA the ability to log into your Github account using an OAuth token.

Some other tips about setting up Home Assistant Core in Ubuntu:

  • If you have a difficult time getting hardware communication to work with something like a Conbee II, try these:
  1. Make sure the user account is in the “dialout” group. For those of you new to Linux understand that Linux puts security onto things you might never think about (and in places you wouldn’t consider). If you are not from a subset of the IT world that lives and breathes this stuff you have a steep learning curve. To wit, your login account (JoeBlow) cannot just talk to the USB device over the serial channel it is mapped to. (Yes, even though this is a USB stick it uses a serial protocol with a set baud rate like an old modem which is why you need to be in the “dialout” group, a holdover from the 1970s Unix operating system, at least.)
  2. After adding your account to “dialout”, log off and log on for the easiest way to get that permission change to take effect. (Yes, you can reload your profile without doing that but you’ll need to search for how.)
  3. For those working with Zigbee, look up which devices have native support in something like the Zigbee Home Automation integration. From my little bit of research and experience, ZHA has more features than the simple deConz integration from the vendor. What a surprise :slight_smile:
  4. When connecting to a serial device use the by-id path such as /dev/serial/by-id/bigLongDeviceIDHereWithVendorInfoAndOtherJibberJabber instead of /dev/ttyACMX or whatever. The latter is subject to change.
  5. When in doubt, reboot. I’ve seen stuff start working after a reboot even though it wasn’t “supposed” to be necessary.

Feel free to reply and ask a question. I’ll do my best to help and I will not be rude to you unless you are rude to me. Deal?

1 Like