HADashboard - Authentication problems

Third party integrations AppDaemon
1

Right, since upgrading to 0.80.3 I can’t get hadashboard to connect to HA.

I’ve made the changes to allow API authentication, I verified that this works when connecting, but hadashboard won’t connect at all.

Appdaemon.yaml

  logfile: STDOUT
  errorfile: STDERR
appdaemon:
  threads: 10
  plugins:
    HASS:
      type: hass
      ha_url: http://10.0.10.252:8123
      ha_key: 1234
hadashboard:
  dash_url: http://10.0.10.252:5050
  dash_dir: /config/appdaemon/dashboards

Configuration.yaml

http:
  api_password: 1234

homeassistant:
  auth_providers:
   - type: legacy_api_password

Getting this error:

2018-10-22 09:14:59.522058 WARNING AppDaemon: HASS: Error in authentication

Any ideas on what I’m missing?

2

I tried on my test bed, and wasn’t able to connect appdaemon at alll. So I reverted my test bed back to 0.79 and have stuck with that for now. I think it is broken, but nobody responded to my question on the 0.80 blog post.

3

I can downgrade, but I run docker on unraid, so that might be another learning curve. Hoping there’s an answer as my tablets are down :grinning:

4

this isnt needed

i got 0.80 running but only connected to my dev version from AD which already has long lived token auth.
ill try to connect to 0.80 with api key tonight.

hopefully the new auth release from AD will be ready for release end of this week.

5

Yeah I’ve tried pretty much everything I can think of.

I’ve downgraded to 0.79.3 and connecting fine again.

Can wait a little to update, having a working hadashboard is more important than HA being up to date.

1 Like
6

i just connected HA 0.80.3 succesfully to AD.

2018-10-22 13:54:07.231927 INFO AppDaemon Version 3.0.1 starting
2018-10-22 13:54:07.232651 INFO Configuration read from: /mnt/usbdrive/pi/appdaemon/ADdashboard/appdaemon.yaml
2018-10-22 13:54:07.237432 INFO AppDaemon: Starting Apps
2018-10-22 13:54:07.239037 WARNING config_dir: /mnt exists, but is not writeable, owner: root
2018-10-22 13:54:07.307958 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-10-22 13:54:07.343016 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-10-22 13:54:07.343808 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-10-22 13:54:07.344370 INFO Starting Dashboards
2018-10-22 13:54:07.359611 INFO API is disabled
2018-10-22 13:54:07.380358 INFO AppDaemon: HASS: Connected to Home Assistant 0.80.3
2018-10-22 13:54:07.412378 INFO AppDaemon: Got initial state from namespace default
2018-10-22 13:54:09.498221 INFO AppDaemon: Adding /mnt/usbdrive/pi/appdaemon/ADdashboard/apps/ to module import path
2018-10-22 13:54:09.504112 INFO AppDaemon: App initialization complete

and back to 0.79
i show this log to show there is no difference.

2018-10-22 13:57:35.766395 INFO AppDaemon Version 3.0.1 starting
2018-10-22 13:57:35.766928 INFO Configuration read from: /mnt/usbdrive/pi/appdaemon/ADdashboard/appdaemon.yaml
2018-10-22 13:57:35.771463 INFO AppDaemon: Starting Apps
2018-10-22 13:57:35.773078 WARNING config_dir: /mnt exists, but is not writeable, owner: root
2018-10-22 13:57:35.840632 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-10-22 13:57:35.866265 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-10-22 13:57:35.867052 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-10-22 13:57:35.867535 INFO Starting Dashboards
2018-10-22 13:57:35.883022 INFO API is disabled
2018-10-22 13:57:35.902073 INFO AppDaemon: HASS: Connected to Home Assistant 0.79.3
2018-10-22 13:57:36.059703 INFO AppDaemon: Got initial state from namespace default
2018-10-22 13:57:38.016857 INFO AppDaemon: Adding /mnt/usbdrive/pi/appdaemon/ADdashboard/apps/ to module import path
2018-10-22 13:57:38.020645 INFO AppDaemon: App initialization complete

so the problem must be somewhere else.

at least this:

homeassistant:
  auth_providers:
   - type: legacy_api_password

shouldnt be there.
and this url ha_url: http://10.0.10.252:8123 should let you connect to HA in a browser and you should be able to use the api password there.

1 Like
7

shouldnt be there.
and this url ha_url: http://10.0.10.252:8123 should let you connect to HA in a browser and you should be able to use the api password there.

Yeah I can do this successfully, which is why I thought it was odd.

I’ll have another go at this week, but on a test environment, but think from your previous comments authentication integration into AD isnt far away anyway.

8

right, Andrew is planning the release this coming weekend.

4 Likes
9

Great stuff, appreciate your help.

1 Like