@danielperna84 Really great work, I’ve just found out about this tool and I love it!
I am having one issue: I cannot get the link to the HA api to work. I’m using SSL. See the error I’m getting below and my settings.conf file. Any ideas what could be causing this? 192.168.1.1 is my router IP, I’m not totally clear why that is listed here. I assume it’s because the traffic is going out to my dynamic dns address and then back in through my router, but i can’t make heads or tails of it.
If it makes a difference, I’m using regular Home Assistant, not hass.io. !
It’s been a while since I have tested with SSL, but when using the regular configurator you should be able to set the HASS_API to the internal IP of HASS. If I recall correctly, then SSL is not verified. So you don’t need to use the hostname. And the configurator is accessing the API by itself from within the network. So for this feature external access to the API is irrelevant und shouldn’t be routed to the outside.
@danielperna84 Thanks for the reply. When you setup SSL on Home Assistant, you can no longer access HA from the local IP address, you have to use the external dynamic DNS address. This doesn’t seem to be a problem actually; using curl commands, I verified that I can access the api from the external address. However, it seems like there is something wrong with the bootstrap part of the api; I get a 404 error response when calling it, while all of the other REST commands work fine. See the image below. Thoughts? It’s not an authentication issue, all of the other REST commands work. I should be getting a result that looks like what is posted in the REST api documentation. @bloody2k Maybe you can try the same thing and post your results? It sounds like you had it working previously, and it broke when upgrading to 0.57.1.
Apparently the bootstrap part of the API is not working anymore, as reported here:
If that’s really the case, then none of the thrid party tools will work anymore. So this probably is a bug within Home Assistant. I myself haven’t upgraded to 0.57 yet, so I didn’t experience the problem for probably exactly this reason.
Does anyone have any tips for getting this working with SSL? I’m using the “out of the box” DuckDNS/LetsEncrypt plugin for Hass.io. My configuration is set like so:
Those are the correct paths to the cert and key files, which is what is used by the DuckDNS plugin and I’ve verified those paths are correct via an SSH terminal. But when I try to start the Configurator plugin, I get this:
starting version 3.2.2
INFO:2017-12-29 18:19:11,394:__main__:Starting server
Traceback (most recent call last):
File "/configurator.py", line 3659, in <module>
main(sys.argv[1:])
File "/configurator.py", line 3649, in main
server_side=True)
File "/usr/lib/python3.6/ssl.py", line 1142, in wrap_socket
ciphers=ciphers)
File "/usr/lib/python3.6/ssl.py", line 741, in __init__
self._context.load_cert_chain(certfile, keyfile)
FileNotFoundError: [Errno 2] No such file or directory
@danielperna84 I just loaded your repository but upon trying to install I get this log error:
Supervisor Logs
18-01-04 07:53:31 WARNING (MainThread) [hassio.addons.data] Can’t read /data/addons/core/homematic/config.json
18-01-04 07:53:31 WARNING (MainThread) [hassio.addons.data] Can’t read /data/addons/core/tellstick/config.json
18-01-04 07:53:31 INFO (MainThread) [hassio.addons] Load addons: 17 all - 1 new - 0 remove
18-01-04 07:55:20 INFO (MainThread) [hassio.addons.addon] Create Home-Assistant addon data folder /data/addons/data/b794684e_hass-configurator
18-01-04 07:55:20 INFO (SyncWorker_0) [hassio.dock.addon] Start build b794684e/amd64-addon-hass-configurator:0.1.1
18-01-04 07:55:20 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 410, in start
resp = yield from self._request_handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web.py”, line 325, in _handle
resp = yield from handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 93, in impl
return (yield from handler(request))
File “/usr/lib/python3.6/site-packages/hassio/api/util.py”, line 33, in wrap_api
answer = await method(api, *args, **kwargs)
File “/usr/lib/python3.6/site-packages/hassio/addons/addon.py”, line 515, in install
if not await self.docker.install(self.last_version):
File “/usr/lib/python3.6/site-packages/hassio/dock/util.py”, line 18, in wrap_api
return await method(api, *args, **kwargs)
File “/usr/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/lib/python3.6/site-packages/hassio/dock/addon.py”, line 251, in _install
return self._build(tag)
File “/usr/lib/python3.6/site-packages/hassio/dock/addon.py”, line 264, in _build
image = self.docker.images.build(**build_env.get_docker_args(tag))
File “/usr/lib/python3.6/site-packages/docker/models/images.py”, line 179, in build
raise BuildError(chunk[‘error’])
docker.errors.BuildError: Error parsing reference: “%%BASE_IMAGE%%” is not a valid repository/tag: invalid reference format
18-01-04 08:05:22 INFO (SyncWorker_2) [hassio.dock.addon] Start build b794684e/amd64-addon-hass-configurator:0.1.1
18-01-04 08:05:23 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 410, in start
resp = yield from self._request_handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web.py”, line 325, in _handle
resp = yield from handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 93, in impl
return (yield from handler(request))
File “/usr/lib/python3.6/site-packages/hassio/api/util.py”, line 33, in wrap_api
answer = await method(api, *args, **kwargs)
File “/usr/lib/python3.6/site-packages/hassio/addons/addon.py”, line 515, in install
if not await self.docker.install(self.last_version):
File “/usr/lib/python3.6/site-packages/hassio/dock/util.py”, line 18, in wrap_api
return await method(api, *args, **kwargs)
File “/usr/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/lib/python3.6/site-packages/hassio/dock/addon.py”, line 251, in _install
return self._build(tag)
File “/usr/lib/python3.6/site-packages/hassio/dock/addon.py”, line 264, in _build
image = self.docker.images.build(**build_env.get_docker_args(tag))
File “/usr/lib/python3.6/site-packages/docker/models/images.py”, line 179, in build
raise BuildError(chunk[‘error’])
docker.errors.BuildError: Error parsing reference: “%%BASE_IMAGE%%” is not a valid repository/tag: invalid reference format
I have this installed through Hass.io, but I’m a bit confused as to how the GIT options work.
I’d assumed that it’s used to commit and push to my own repository for an easy backup, but I can’t see anywhere to enter my github details, and when I try a commit anyway it complains (obviously) about “could not read Username for https://github.com”
Is it possible to get this working or is it a remnant of some previous functionality?
It’s a feature primarily intended for the standalone version of the configurator. There you have shell access and can setup the remote manually, along with details needed for authentication.
However, in the menu on the top right you have an option called “execute shell command”. I have never tried it with hassio, but maybe adding a remote works from there as well.
I don’t know how well this works with GitHub though. I have a SSH based remote with Pubkey authentication and it works like a charm.
Well, as I’ve been pushing to git manually, I’ve already set up a repository etc in my config folder, and that does seem to be reflected in Configurator. I was also able to add a branch, and I can also commit through Configurator, it’s just push doesn’t work from the UI. If I SSH in and do a push, my commits through Configurator then go through,
Seems to be pretty close to working, just not quite…
In that case I’m not sure what the issue is. Maybe the used Git module (GitPython) doesn’t support pushing to github. The one time I was pushing to Github from shell it was an interactive process where I had to manually authenticate and paste some long key. This interactiveness isn’t available for the configurator. I guess this can be automated with environment variables, but these then would be needed for the user the configurator is running, and again, the Git module would need to make use of that.
In the end all the configurator does is git push. Setting up the remote and authenticating has to be done manually, since this depends on what the user is doing.
Not sure if this is the right place or not.
I am running Hass.io on an RPI 3. I had the Configurator addon (from the Built-in Add-ons) installed and working fine. Then I tried to update to the latest version. Now whenever I try to start the addon I get the following error:
18-01-23 20:41:05 ERROR (SyncWorker_12) [hassio.docker] Can’t create container from addon_core_configurator: 409 Client Error: Conflict (“Conflict. The container name “/addon_core_configurator” is already in use by container “4c679a5758ea26b7987058155c29f566af419f989750fe703a5f811fbe16f3d9”. You have to remove (or rename) that container to be able to reuse that name.”)
I’m not sure how to remove the old container (if that is what I need to do)
!
