Can you help a confused noob with basic first steps?

Sorry if these questions are answered elsewhere, but I’m very puzzled at this point.

I’m following https://www.home-assistant.io/getting-started/

I have a Raspberry Pi 3 B+. Installed “Hass .io Raspberry Pi 3 Model B and B+ 32bit”. (Is the 64bit Hass .io better?) Seemed to go ok. Here’s where my experience begins to disconnect form the documentation.

On first use of the web interface, it asks for a username and password. That’s not mentioned in the docs. Instead the docs talk about “securing” my Hass. I’ll come back to that. I created a login, all ok.

So I then install configurator. I read that it should be password protected, however any new lines in the configurator file don’t stick. It seems to save ok (if the syntax is valid), there are no error messages. But coming back to the screen (or even pressing the other save button) resets the config to default. Is it not necessary to configure the configurator any more? Like ip address filtering, credentials etc. etc.

I can still start configurator to go and edit my config files. Groovy. Am I safe? I don’t know… In “securing” the system, it recommends setting an http_password using secrets. Ok, managed that, but it doesn’t ask me for it when the machine reboots. Is that because I saved the credentials I created the first time I used the web interface, and adding more credentials in config.yaml is now redundant?

I’m guessing there have been a couple of updates since the docs were last updated, I guess my main concern here is to make sure I’m not doing anything unsafe by leaving configurator un passworded, or by not adding an http_password to config.yaml

Any advice is gratefully received!

The latest configurator doesn’t requite auth as it uses the Home Assistant user now. Additionally, http_password isn’t needed either (legacy api password)

The auth has been completely redone with username and password so some of that doc is out-of-date

2 Likes

Amazing, thank you for that info. So no need (or way?) to configure the configurator beyond this?
{
“dirsfirst”: false,
“enforce_basepath”: false,
}
Do I need to do anything else to secure HASS before setting up duckDNS?