Hass-configurator

[Yazmín Bohon]

Acommon reason for this is when you use https for Home Assistant but not for the configurator. By design browsers only embed resources that use the same protocol. So you either have to use https in both cases or plain http.

You have to adjust the path in the line that starts with ExecStart to use the path to your configurators executable. In the best case you can just put hass-configurator there. The rest is optional and depends on how you want to configure it. The wiki provides some details on configuration.

Today we are going to see how to install Home Assistant and some complements on docker using a docker-compose file. Consequently, this stack will provide the following services:

This procedure has been tested in arm (Raspberry Pi) and x86_64 architectures. For instructions on how to install docker and docker-compose on your Raspberry Pi you can check this article.

A few environment variables will be declared in a file named .env, in the same directory where the docker-compose file is. As a result, these variables will be populated later into our docker-compose file at the moment the containers are created.

The purpose of this stack is to have a working Home Assistant installation with some accessories. This means that it is not secure by default so you should NEVER expose it to the internet as is. I will explain some steps to secure it in a next article, for example how to password protect Node-RED and hass-configurator and how to hide Home Assistant behind a reverse proxy like nginx using ssl certificates.

If you are migrating from an older Home Assistant installation, you should copy over the content of your old configuration directory, including hidden files and folders, to the hass-config folder. Probably you will need to make some adjustments to your configuration, but it should work as expected.

We have seen how to install Home Assistant and some other components under docker using docker-compose. We will be improving this stack in next articles. If you have any question, leave a comment.

to the configuration file continue using mosquitto without authentication so that it will start. Here is a link to the mosquitto documentation about [Migrating from 1.x to 2.0]( -to-2-0/) that explains the options.

Sure! You can easily add any other container/service to this docker-compose stack. For wireguard I can recommend you the linuxserver/wireguard docker image, I have been using it flawless for a while. For nginx you can opt for the official image or any other out there depending of your needs.

Hi, thanks for your comment. This is probably because the user id with which you created the folder structure was not 1000 (the user id that the container runs with). You got it the right way. If I can help you in any manner please let me know.

Hi. Thanks for great tut. I created folder structure with root user, so it means ID 0. Everything is working except nodered. In HA, there are no any buttons in nodered panel everything is empty and with docker ps , I can see that nodered is starting on port 1880 straight after executing docker start nodered, but few seconds after that, it going to restart and not working (STATUS: Restarting (1) 18 seconds ago)

Hi, It can be by several reasons, like folder permissions, etc. I would need more info in order to help you further. Perhaps container logs could give a hint about what is happening. Paste the log here If you want me to take a look. Regards.

Hi, seems that cannot connect with the database, is mariadb container up and running without errors? If so, check your connection string for any misspelling. Have you made any extra change to the docker compose file?

Hi, I think so. It sounds to me that there are HA docker images for different architectures, check the image repo site to see if there is one that suits yours. The same goes for the rest of the containers. But from memory I would say that yes, you can install it in an arm architecture. Let us know if you succeeded at this. Hope this helps, Regards.

Thanks for the writeup. It worked pretty well for me, but I did run into some issues when everything started up for the first time. The logs indicated that the homeassistant user could not connect to the database. I fixed this by logging into the database and creating the homeassistant user, creating the ha_db database, and granting permissions for the homeassistant user on the ha_db database.

Hi, thanks for your comment. It sounds weird for me, provided you are using the compose and .env files, linuxserver mariadb container should create the user and database as specyfied in docker-compose.yml

In this article will we install the formally known hass-configurator, as a companion app to Home Assistant Snap. The configurator is a web-based editor, that will let you edit the configuration files within Home Assistant Snap through the web brower.

Login to Home Assistant web UI and go to your profile, scroll down to Long-Lived Access Tokens and press create token. Give it a descriptive name, such as Home Assistant Configurator and press OK.

3a8082e126