Git Pull Failing Configuration Test

Hey folks,

I’m just getting started with Home Assistant and I’m working on getting my dev pipeline setup setup with Git Pull. Unfortunately, Git Pull seems to throw an error every time it grabs an updated version of the config. Here is the error message I’m getting in the logs:

[Info] Checking if something has changed... [Info] Something has changed, checking Home-Assistant config... /usr/bin/hassio: line 1: Not: command not found [Error] Configuration updated but it does not pass the config check. Do not restart until this is fixed!

The weird thing is that if I manually trigger the config check in Configuration>General it passes without any issues so I know my config file is fine.

From the github page for git pull it appears that the error is getting thrown on this line:

if hassio homeassistant check; then

From my initial research it looks like that is just calling an internal hassio command that is somehow not found.

Any suggestions or recommendations on where to go from here?

Thanks!

That’s odd. If I open a terminal into my machine and run that command, it seems to work fine, so I don’t think the command missing is a problem:

➜  /config hassio homeassistant check
Error: Testing configuration at /config
ERROR:homeassistant.util.yaml:YAML file /config/themes/transparent.yaml contains duplicate key "dark-primary-color". Check lines 10 and 11.
ERROR:homeassistant.util.yaml:YAML file /config/themes/transparent.yaml contains duplicate key "dark-primary-color". Check lines 11 and 12.
WARNING:homeassistant.components.http:Configuring trusted_networks via the http component has been deprecated. Use the trusted networks auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#trusted-networks

I then fixed those issues, and now this is what it returns:

➜  /config hassio homeassistant check
ok

Do you get an ok result if you run it manually?

I just ssh’ed into the pi and ran

# hassio homeassistant check

which does return ok.

Any update here? I’m having the same issue since updating to 0.92.1.

Unfortunately not. It looks like other users have reported the issue here as well: