besides enabeling the api password there are some more lines needed in the configuration.
homeassistant:
auth_providers:
- type: legacy_api_password
downgrading should not be neccesary.
1 Like
I don’t have
auth_providers:
- type: legacy_api_password
in configuration and api_password works (HA 0.77.1).
hmm, strange. that shouldnt. they have put in that part esspecially for that.
are you sure you have restarted everything (including the device) and have AD up and running and HA 0.77.1?
Ever since the new HA updates I am trying to run appdaemon by this command sudo appdaemon -c /home/homeassistant/.homeassistant/conf -D DEBUG to check if its working fine. I get the following errors:
2018-08-31 12:07:43.598280 INFO AppDaemon Version 3.0.1 starting
2018-08-31 12:07:43.600309 INFO Configuration read from: /home/homeassistant/.homeassistant/conf/appdaemon.yaml
2018-08-31 12:07:43.601672 DEBUG AppDaemon Section: None
2018-08-31 12:07:43.602833 DEBUG HADashboard Section: None
2018-08-31 12:07:43.613513 INFO AppDaemon: Starting Apps
2018-08-31 12:07:43.624643 DEBUG AppDaemon: Creating worker threads ...
2018-08-31 12:07:43.636071 DEBUG AppDaemon: Done
2018-08-31 12:07:43.638270 DEBUG AppDaemon: Entering run()
2018-08-31 12:07:43.640335 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2018-08-31 12:07:43.705103 INFO AppDaemon: HASS: HASS Plugin Initializing
2018-08-31 12:07:43.707987 INFO AppDaemon: HASS: HASS Plugin initialization complete
2018-08-31 12:07:43.709833 DEBUG AppDaemon: Starting utility loop
2018-08-31 12:07:43.711361 INFO Starting Dashboards
2018-08-31 12:07:43.752413 INFO API is disabled
2018-08-31 12:07:43.754252 DEBUG Start Loop
Traceback (most recent call last):
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1044, in create_server
sock.bind(sa)
OSError: [Errno 98] Address already in use
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/appdaemon", line 11, in <module>
sys.exit(main())
File "/usr/local/lib/python3.6/site-packages/appdaemon/admain.py", line 375, in main
admain.main()
File "/usr/local/lib/python3.6/site-packages/appdaemon/admain.py", line 371, in main
self.run(appdaemon, hadashboard)
File "/usr/local/lib/python3.6/site-packages/appdaemon/admain.py", line 92, in run
loop.run_until_complete(asyncio.gather(*pending))
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 467, in run_until_complete
return future.result()
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1048, in create_server
% (sa, err.strerror.lower()))
OSError: [Errno 98] error while attempting to bind on address ('0.0.0.0', 5066): address already in use@ReneTode so I changed the port for HAdashboard and it worked fine. However if I restart my raspberry pi I get the same error as above.
Why is the port for HAdashboard being replaced by something else?
I think .77 has it built in by default and the auth part is not required anymore…
for clarification, read this post and the next one from baloob.
1 Like
the dashboard is a server and you can chose your own port.
if you have something else running on those ports you get conflicts.
@aidbish ballob did tell Andrew that it needs to be used that way.
@ReneTode there is nothing running on the port chosen for HAdashboard.
Its flaky as I have rebooted my rpi, debugged it and it seems to be connecting fine. Lets see how long it lasts!
Works for me with just:
configuration.yaml:
http:
api_password: 'pass'
Adding auth_providers breaks things.
do you have a username password combination when you go to HA in a browser?
what do you use hassio, hassbian, anything else?
There’s no prompt for username / password, but I do have an username and a password set (does the browser remember me?).
I use HASS on Raspbian.
Hey all,
I’m guessing plans are to move away from HA requiring the API_password method for Appdaemon and use the new default method of HA??
yeah, thats it. i was misinformed and auth_providers isnt needed.
@robg the plan at this moment is that you get a web frontend for AD where you can do all kind of stuff, and you set the user/password combination for HA there.
WEB frontend for AD, sounds interesting good luck!
1 Like
Don’t need or want a web frontend for AD.
From what I understand, HA is building out authentication tokens (can’t remember the official name). So you can generate one for each application. They would be used in a similar way as the api password, just instead of one, you have many and can revoke them, etc, etc.
AD just needs to support that, when it is ready.
Andrew has spoken with balloob and came to the conclusion that the best and easiest way is to create a frontend where you connect AD with HA.
so AD will support the new authentication in that way.
after you have set the authentication, you dont need to use the frontend if you dont want to.
but it will get more functions, like an easy way to shutdown and restart apps.
If I am running AD in a docker, now I’ll have to open another port in it, just to configure one thing?
If they are creating a way to create long lived access tokens, just let me create on in HA, then I’ll paste it in the config for AD. Then it sends the key over.
I understand some benefits of a UI, but I’d rather not be forced to use one.
i have no clue how the new authentication works.
so i cant tell you if there will be a workaround.
Andrew will create something in a way he sees best, with the best possible options.
i know andrew and if something is optional he will make it optional.
at least you can be sure that when you dont want the port opened continously, it will be possible to just open it during the install and then close it again.
Hi @ReneTode
I just migrating from RPi3 to Intel NUC via Virtualbox
I installed the image 2.9 with updated to v. 0.87.1 then I discovered Appdaemon do not start…
it show me
2019-02-16 22:42:29.828109 INFO AppDaemon: HASS: Connected to Home Assistant 0.87.1
2019-02-16 22:42:29.841593 WARNING AppDaemon: HASS: Error in authentication
but I didn’t modified configuration… why?
i would love to give you an answer, but i cant.
i dont even know what image 2.9 is
but the warning says: you got a problem with authentication.
so HA wont allow you access with the settings you have in appdaemon.yaml.
so in general i would say: check your url and check your token. and make sure that both AD and HA have access in and out the container you created.