Editing configuration.yaml to add Cyberpower UPS

Configuration
1

I’m new to HA, and first time editing configuration.yaml.
I applied all available updates.

  • Core 2024.6.3
  • Supervisor 2024.06.0
  • Operating System 12.3
  • Frontend 20240610.1

I’m following this article specifically the post by @Simon_Bunn with “configuration.yaml for a cyberpower UPS and the entities card setup.”

I have not yet needed to edit configuration.yaml, so I searched and found this article. Which said: If you are unsure which option to choose, install the file editor add-on.

It says “Once you have the add-on installed, you can edit files within your /config directory.”

I completed the installation of Current version: 5.8.0, and clicked Open in Web UI.

I clicked the “Browse Filesystem” icon at the upper left.

It shows the current directory as /homeassistant, and lists about a dozen files, including configuration.yaml.

Next to the /homeassistant path, there is a left arrow. Thinking it will take me up a level to then select the “/config” directory, I click it. Nothing happens.

I can open /homeassistant/configuration.yaml, but I’m not sure that is the correct one. What is my configuration directory? Does it move?

I read “To look up the path to your configuration directory, go to Settings > System > Repairs.”
That only shows me “There are currently no repairs available”, not the dialog shown on this page. The link to System Information is not there. I thought it might be under “About”, but it is not there either.

Can anyone point me to current documentation on editing configuration.yaml?

Edit: I looked from the terminal and it appears that both /config and /homeassistant contain configuration.yaml:

Welcome to the Home Assistant command line.


  OS Version:               Home Assistant OS 12.3
  Home Assistant Core:      2024.6.3

  Home Assistant URL:       http://homeassistant.local:8123
  Observer URL:             http://homeassistant.local:4357
[core-ssh ~]$ ls
addon_configs  addons         backup         config         homeassistant  media          share          ssl
[core-ssh ~]$ cd config
[core-ssh config]$ ls
automations.yaml          deps                      home-assistant.log.fault  home-assistant_v2.db-wal  secrets.yaml              zigbee.db-shm
blueprints                home-assistant.log        home-assistant_v2.db      scenes.yaml               tts                       zigbee.db-wal
configuration.yaml        home-assistant.log.1      home-assistant_v2.db-shm  scripts.yaml              zigbee.db
[core-ssh config]$ cd /
[core-ssh /]$ cd homeassistant/
[core-ssh homeassistant]$ ls
automations.yaml          deps                      home-assistant.log.fault  home-assistant_v2.db-wal  secrets.yaml              zigbee.db-shm
blueprints                home-assistant.log        home-assistant_v2.db      scenes.yaml               tts                       zigbee.db-wal
configuration.yaml        home-assistant.log.1      home-assistant_v2.db-shm  scripts.yaml              zigbee.db
[core-ssh homeassistant]$
2

that’s the correct one. i’m not quite sure why file editor remaps the name from /config to /homeassistant but regardless, you’re ok.

personally i prefer studio code server. but that’s personal preference. you might take a look at that and see what suits your preference better.

3

The config directory is renamed homeassistant from now on. There is a symbolic link for config so things do not break if you reference it through the old name. So the reason you see the same contents is because it is exactly the same folder.

Note that Home Assistant evolves fast paced. So a three year old guide may contain screenshots and references to more things that have changed since.

1 Like
4

thanks! maybe i’m just an old fart, but i like my tools to reflect the reality underneath.
but regardless, the reason why is good to know!

5

Thank you for the explanation!

1 Like