I too am having problems with the new HASS (0.77.1) and appdaemon. I previously was NOT using authentication anywhere. After reading some of the threads here and the release notes for HASS, I made a bunch of changes but still can’t get appdaemon logged into HASS.
Here is the relevant portion of my configuraton.yaml file:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: ***
longitude: ****
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 157
# metric for Metric, imperial for Imperial
unit_system: imperial
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: America/Chicago
# Customization file
customize: !include customize.yaml
auth_providers:
- type: homeassistant
- type: legacy_api_password
# Show links to resources in log and frontend
#introduction:
# Enables the frontend
frontend:
# Enables configuration UI
config:
# Enables Python script processing
python_script:
auth:
http:
api_password: !secret http_password
I still get these errors in the appdaemon.log file:
2018-08-31 08:26:29.356869 INFO AppDaemon: HASS: Connected to Home Assistant 0.77.1
2018-08-31 08:26:29.362443 WARNING AppDaemon: HASS: Error in authentication
2018-08-31 08:26:29.363735 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
2018-08-31 08:26:34.393145 INFO AppDaemon: HASS: Connected to Home Assistant 0.77.1
2018-08-31 08:26:34.399790 WARNING AppDaemon: HASS: Error in authentication
2018-08-31 08:26:34.402093 WARNING AppDaemon: HASS: Disconnected from Home Assistant, retrying in 5 seconds
and these errors in the home assistant log:
2018-08-31 08:27:14 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 127.0.0.1
2018-08-31 08:27:19 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 127.0.0.1
2018-08-31 08:27:24 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 127.0.0.1
Can I just roll back HASS to an older version to get going again?
i hope you did create a new secret file for that?
you cant expect AD to know where your HA secret file is.
so AD expects a sercet file inside the appdaemon conficuration directory.
did you try to put in the api password directly ( i know others who have had problems with the secret file)?
and what system do you use? hassio, docker, hassbian with venv?
with a docker i believe you need to change somethings else (but i dont know what because im not using it)
with hassio localhost could be the problem
the ha_url normally is the url that you can use in a browser to reach HA.