Updated and Now Can't Load Front End

Configuration
1

Hi Guys

Recently I did an update as my front end told me there was, plus I also updated from Python 3.6.0 as I notifications about being on that version.

Following the instructions on this page I updated to 3.7.0 (confirmed that by using the “python3 -V” command) and just replaced any instance of 3.6.0 with 3.7.0 in the various command lines.

Now my front end doesn’t load. I’ve done reboots and even done another update command which has now updated me to 101.3 (the update that I did that was the beginning of my issues must have been 101.2??)

Anyway, I haven’t done any changes to any yaml files or anything. All I’ve done is run the command

sudo hassbian-config upgrade homeassistant

and updated Python and now my front end doesn’t load.

The start of my home-assistant.log file reads as follows:

2019-11-07 09:45:05 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds.
2019-11-07 09:45:05 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: [api_password] is an invalid option for [http]. Check: http->http->api_password. (See /home/homeassistant/.homeassistant/configuration.yaml, line 91). Please check the docs at HTTP - Home Assistant
2019-11-07 09:45:05 ERROR (MainThread) [homeassistant.setup] Setup failed for http: Invalid config.
2019-11-07 09:45:06 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of system_log. Setup failed for dependencies: http
2019-11-07 09:45:06 ERROR (MainThread) [homeassistant.setup] Setup failed for system_log: Could not set up all dependencies.
2019-11-07 09:45:06 INFO (MainThread) [homeassistant.setup] Setting up recorder
2019-11-07 09:45:07 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.9 seconds.
2019-11-07 09:45:07 INFO (MainThread) [homeassistant.setup] Setting up zone
2019-11-07 09:45:07 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.0 seconds.
2019-11-07 09:45:08 INFO (MainThread) [homeassistant.setup] Setting up vera
2019-11-07 09:45:08 INFO (MainThread) [homeassistant.setup] Setting up group
2019-11-07 09:45:08 INFO (SyncWorker_7) [homeassistant.loader] Loaded darksky from homeassistant.components.darksky
2019-11-07 09:45:08 INFO (MainThread) [homeassistant.setup] Setting up duckdns
2019-11-07 09:45:08 INFO (MainThread) [homeassistant.setup] Setup of domain duckdns took 0.1 seconds.

It continues with some more setups (like duckdns in the last line above) and then starts generating some errors such as:

2019-11-07 09:45:09 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.1 seconds.
2019-11-07 09:45:09 INFO (MainThread) [homeassistant.setup] Setting up weather
2019-11-07 09:45:09 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.8 seconds.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of webhook. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for webhook: Could not set up all dependencies.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of api. Setup failed for dependencies: http
2019-11-07 09:45:09 INFO (SyncWorker_10) [homeassistant.loader] Loaded moon from homeassistant.components.moon
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for api: Could not set up all dependencies.
2019-11-07 09:45:09 INFO (SyncWorker_9) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of conversation. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for conversation: Could not set up all dependencies.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of config. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for config: Could not set up all dependencies.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of system_health. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for system_health: Could not set up all dependencies.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of tts. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for tts: Could not set up all dependencies.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of websocket_api. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for websocket_api: Could not set up all dependencies.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of auth. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for auth: Could not set up all dependencies.
2019-11-07 09:45:09 INFO (MainThread) [homeassistant.components.weather] Setting up weather.darksky
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of history. Setup failed for dependencies: http
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for history: Could not set up all dependencies.
2019-11-07 09:45:09 INFO (MainThread) [homeassistant.setup] Setup of domain vera took 1.2 seconds.
2019-11-07 09:45:09 INFO (SyncWorker_12) [homeassistant.loader] Loaded command_line from homeassistant.components.command_line
2019-11-07 09:45:09 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2019-11-07 09:45:09 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds.
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of device_automation. Setup failed for dependencies: webhook
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for device_automation: Could not set up all dependencies.
2019-11-07 09:45:09 INFO (SyncWorker_17) [homeassistant.loader] Loaded switch from homeassistant.components.switch
2019-11-07 09:45:09 INFO (SyncWorker_15) [homeassistant.loader] Loaded lock from homeassistant.components.lock
2019-11-07 09:45:09 INFO (SyncWorker_16) [homeassistant.loader] Loaded light from homeassistant.components.light
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: auth, http
2019-11-07 09:45:09 INFO (SyncWorker_7) [homeassistant.loader] Loaded climate from homeassistant.components.climate
2019-11-07 09:45:09 INFO (SyncWorker_11) [homeassistant.loader] Loaded scene from homeassistant.components.scene
2019-11-07 09:45:09 INFO (SyncWorker_14) [homeassistant.loader] Loaded cover from homeassistant.components.cover
2019-11-07 09:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for onboarding: Could not set up all dependencies.

Is it common that updates to HA cause it to stop working if no changes were made to yaml files?

Should I just keep doing updates in the hope that one future one works nicely with my configuration files like it did prior to the last update?

Thanks

2

Did you read the breaking changes on the version you updated to? And if you made a big jump in versions there may be other breaking changes you didn’t pay attention to. Also read your logs. The error is referencing the HTTP component and the fact you have an invalid config for it, due to a breaking change you did not address in your config prior to updating.

Yes it’s common if breaking changes are ignored when updating.

1 Like
3

No. I didn’t even know where to go to read these. I just saw the updater indicate there was an update and assumed it was ok to just update. I didn’t think a working configuration file would have issues with updates in HA.

Oh well. It’s not like I really did much with it anyway, other than a custom alarm that turned on a light and made an announcement over my Google Home Minis when my motion detector was activated.

All the other stuff like being able to see what lights were on or off or the various reading from sensors (temp, UV, humidity, etc) can be seen in the various apps from those products. HA just made it visible for me from the one webpage interface.

HA looked interesting but I don’t think I’m getting enough out of HA that can’t be done via their apps to warrant the amount of effort needed to keep it from breaking. I’m not a programmer or anything like that so getting messages saying I need to upgrade Python from 3.6.0 to 3.6.1 etc and then spending ages searching through forums and help files to work out how to do that one thing, etc just isn’t worth it for me.

Thanks anyhow.

4

Before you give up, give Hassio a try. It overcomes All dependency issues by being entirely packaged for you.
I understand the frustration, I think most of us have been there, but this really is a fantastic platform and the satisfaction you’ll eventually get is really rewarding

5

For future reference, almost every release of Home Assistant have some kind of breaking changes.

The relesenotes are linked on the same “card” as where you clicked “update”, but here is a handy link https://www.home-assistant.io/blog/

As for your spesific issue, you had the answer in the log that you posted:

2019-11-07 09:45:05 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: [api_password] is an invalid option for [http]. Check: http->http->api_password. (See /home/homeassistant/.homeassistant/configuration.yaml, line 91). Please check the docs at https://home-assistant.io/integrations/http/
2019-11-07 09:45:05 ERROR (MainThread) [homeassistant.setup] Setup failed for http: Invalid config.

Remove api_password from your configuration (it’s located under http) and your installation will be able to start the frontend again.

6

I was waiting for Bruh to finish his tutorial on installing and setting up Hassio but he hasn’t uploaded any further videos.

My current setup connects to Z-Wave via Vera hub but I’m thinking of getting a Z-wave USB stick and getting rid of the Vera Hub and making everything cleaner, but without a simple instructional video (since I’m simple :slight_smile: ) I haven’t tried it.

My current set up was done following Dr Zzs but I couldn’t see a recent Hass.IO install/setup tutorial.

cheers

7

This has always been, and will always be the up to date installation tutorial:
https://www.home-assistant.io/hassio/installation/

8

A while ago a new icon appeared at the top of my page called “updater” and it changes if there was an update. When I see this icon, I would just go to Common tasks on Hassbian, copy the line:

sudo hassbian-config upgrade homeassistant

and then paste it into a PuTTY screen.

I never clicked on any “update” link. This is the only way I’ve ever done updates other than doing the individual commands on that page I linked to before (from memory, the one line update section at the top was added later which made it easier for me), but either way, I’ve always followed the instructions on that page to do updates.

I honesty find searching for how to do updates (eg updating Python) confusing as they talk about things like putting things in virtual containers (or something) and all the technical talk becomes confusing. To be honest, I would have to look back at Dr Zzs video I initially watched to remember what flavour of Hassbian I installed (I think it was “Stretch” (??)) and sometimes forum answers talk about different installs and I never know if it would work with mine.

Hence I was thinking of Hass.io as I heard I didn’t have to worry about stuff like that but wasn’t sure of the install.

9

Ahh, sorry mate, I saw chatter about hassio and assumed you where running that, bookmark the link I gave you for the next update :wink:

10

Thanks for the link

11

Thanks. Works again.

12

I too was having issue until I removed api_password. I coudln’t find where in the new Releases page that talks about api_password no longer supported. What is new that replaced api_password?

13

Really? https://www.home-assistant.io/blog/2019/10/30/release-101/#api-password-and-trusted-networks

That would be “Long-Lived Access Tokens” as described on the same place.

14

Thanks Ludeeus! Would that have caused my Ecobee to stop detected by HA upgrading from 100.3 to 101.3?

15

Note to anyone that finds this, I had a serious problem with this and couldn’t get the front end to load without rebooting the host/power cycling. It took me a lot longer to debug and test everything.

Ended up finding an obscure warning error about the Configurator add-on configuration. At some point it substantially changed with an update.

Anyway, go here and just copy the configuration: