"Setup failed for dependencies: http"

Installation
1

After updating my docker install of Home Assistant, everything has gone nuts.

Basically all of the components are returning “Setup failed for dependencies: http”

So now the frontend and all my automations aren’t loading. Though it still looks like some things are running in the background according to the log.

1 Like
2

I am facing the same issue since the update

3

Well, I’m glad I’m not the only one. Guess we will need to hear from the devs.

4

SeLLeRoNe

They phased out support for Python 3.6. I’m updating to 3.7 to see if it helps.

Edit: Nope. Updated to 3.7.3. No luck. Don’t know if I’m missing some other dependency or what.

5

This is what bit me, Installing HA in docker on Ubuntu as non-root user

6

Ahh. Yeah I’m one of those crazies who runs as privileged in docker. Need access to USB serial ports.

I ended up reverting. Motivated me to add a version selector to my installation script.

7

I’m actually running in Python Env not as root.

8

same unable to get past the frontend error got this message when I reverted back to .90.1 Unable to install package home-assistant-front end==20190321.0: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE.

My install was a fresh clean install on Raspberry 4 frontend failed in all instances

9

I found my error to be a “trusted_network” option in the “http:” configuration, that is now compeltely deprecated and was causing my issue.

Once removed (or to better say, moved to auth_providers), everything started to work again.

Hope this help you.

Andrea

10

did not help a bit no idea what this trusted_network option is

11

Not sure how you manage your config (not even sure if you use this option), but it is a configurable option.

Before those those “Setup failed for dependencies: http” lines, I had a few lines that were complaining about that configuration parameter.

Might be worth analyze the logs from the “HA Restart Point” to see if you got something before it starts to complain about dependecis.

12

this is what I get for errors that I found so far

2019-11-03 17:27:23 ERROR (MainThread) [homeassistant.setup] Error during setup of component lovelace
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 172, in _async_setup_component
    hass, processed_config
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/lovelace/__init__.py", line 66, in async_setup
    hass.components.frontend.async_register_built_in_panel(
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 421, in __getattr__
    component: Optional[ModuleType] = integration.get_component()
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/loader.py", line 223, in get_component
    cache[self.domain] = importlib.import_module(self.pkg_path)
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/frontend/__init__.py", line 10, in <module>
    import hass_frontend
ModuleNotFoundError: No module named 'hass_frontend'
13

ok the solution I found was here https://github.com/home-assistant/home-assistant/issues/28198

boils down to use line before starting with hass " pip install home-assistant-frontend "

2 Likes
14

I still had the api_password option in my yaml config. This caused the same error.

3 Likes
15

mine was a fresh bare steel install no config was built yet

16

Ended up being my problem, so I’ll mark it as the solution. Not sure if that stops the conversation, but good info, folks!

1 Like
17

Commented out api_password and issue resolved for me too. Thanks!

1 Like