Easiest I found to access /addon_configs folder is via Studio Coder Server i.e. Open Studio Code Server. Press the 3 lines at the top left. Then select File/Open Folder. Then you can select the /addon_configs folder. Then do the same again to get back to the /config folder.
so I would need this add on installing?
Or is it another pc program called “studio code server”
Sorry but this is way above what I have done so far.
TIA.
Yes. Go in your HA to Settings/Add-ons and add Studio Code Server (formerly Visual Studio Code i.e. if you type Visual Studio Code, HA will show you the Studio Code Server add-on). By default the add-on should show your /config folder. Press “Yes” regarding “Trust the Authors” when opening the first time.
Appdaemon is also above what I’m used to but Studio Code Server is my default add-on if I have to change something in my configuration.yaml, sensors.yaml and secrets.yaml. I also can manage all my HACS custom integrations with that tool. And since I’m using the Appdaemon based ELCO Remocon net AppDaemon (sensors for my ELCO heating system) custom integration, I had to find a simple visual way to access the hidden appdaemon.yaml and to change the secrets path. I’m not used to Terminal and Samba
Thanks for the promt reply, I have installed and followed your instructions, but I am unsure what to do when i get to the folder , I am trying to post what it says but its complaining its not formatted correct
Open appdaemon.yaml in the /addon_configs folder and adapt to your needs. I had only to change the secrets path from
secrets: /config/secrets.yaml
to
secrets: /homeassistant/secrets.yaml
to get Appdaemon running again
As an example, my appdaemon.yaml looks as follows:
---
secrets: /homeassistant/secrets.yaml
appdaemon:
latitude: 52.379189
longitude: 4.899431
elevation: 2
time_zone: Europe/Amsterdam
plugins:
HASS:
type: hass
ha_url: http://homeassistant.local:8123
token: !secret appdaemon_token
http:
url: http://homeassistant.local:5050
admin:
api:
hadashboard:
Thank you so much , that all makes sence now. I have it back up and running , but the NS panels dont work as they did. Thank you for your help
Unfortunately I don‘t use NS Panel. But check if the apps folder in the add_configs folder has the necessary .py files of that App (NS Panels) With my use case (Heating) the relevant .py file was not automatically copied to the addon_configs folder i.e. remained in the config folder. After copying the .py file to the addon_configs app folder and ensuring that the apps.yaml in the addon_configs folder is mounting the app, it worked again. The following pictures as a visual help to what I wrote
Good to know: If you don’t see the samba share folder addon_configs
, you probably are still on an older version of the Samba addon. So update it first and the folder addon_configs
will appear
Looks lame, but it took me an hour to figure this out
Make sure you have the latest samba share version: the addon_configs
share is added only recently!
Did you find the reason why NS Panel still did not work after fixing the path to the secrets file?
thanks!
That really doesn’t make sense to me ?
You need to find that “sentence” in your appdaemon.yaml
file.
-
Open your
appdaemon.yaml
file. The location has changed, so you need to follow the instructions in this thread (and several others) to find it after the update to addon file storage. -
Then find the line in
appdaemon.yaml
that mentionssecrets.yaml
, most likely it’s one of the first lines, and most likely the full line sayssecrets: /config/secrets.yaml
if you have not updated it since the new addon file structure. -
Change this line to
secrets: /homeassistant/secrets.yaml
, since this is how the addons reference anything in your oldconfig
directory, i.e., the one wheresecrets.yaml
is located if you have followed Home Assistant instructions for setting it up.
This is ho my appdaemon.yaml
looks now, the highlighted line (first line) is what was previously secrets: /config/secrets.yaml
:
@Aephir your ‘appdaemon.yaml’ file is identical to mine, however when I start the appdaemon addon I get the following errors reported in the logs:
ERROR Error loading secrets file: /homeasistant/secrets.yaml
Traceback (most recent call last):
File “/usr/bin/appdaemon”, line 8, in
sys.exit(main())
^^^^^^
File “/usr/lib/python3.11/site-packages/appdaemon/main.py”, line 417, in main
admain.main()
File “/usr/lib/python3.11/site-packages/appdaemon/main.py”, line 276, in main
if “appdaemon” not in config:
So clearly in my instance secrets: /homeasistant/secrets.yaml
is not the right path referencing.
Weird, but it looks like the same as here.
Where is you secrets.yaml
? It’s in the base directory of Home Assistant (same folder as configuration.yaml
), right?
You did update so you have the addon mounts as separate from the homeassistant
/config
mounts, right? That is, in the base directory where you have configuration.yaml
(and secrets.yaml
), there should be no appdaemon
directory (or if there is, it should be empty).
Yes - my secrets.yaml
file is in the same place its been since I began using Home Assistant in 2016, in the /config
folder, now renamed the /homeassistant
folder.
With regard to your query about the add on mounts, I’m not following you on that one. There is no appdaemon
directory in my /homeassistant
folder.
My Home Assistant install is via the HA OS method, running on a Rpi4 off a 32Gb SSD card. With the latest install documentation its the installation method as described here:
https://www.home-assistant.io/installation/#diy-with-raspberry-pi
In that context I’m presuming appdaemon
, like other add-ons, is running, with HA supervision, in its own docker container independent of the HA container, but is set-up to access the HA container file structure for configuration and data files.
appdaemon
all works fine save that clearly I don’t yet understand how to guide appdaemon
where to find the /homeassistant
folder relative to its own configuration folder, which is at the path /addon_configs/xxxxxxxx.appdaemon
. I’m presuming that both the /homeassistant
and the /addon_configs
folder are at the root level in the HA docker container.
OK, that sounds correct. The addon_configs/
is the “new” mount that appeared in late 2023 (if you kept everything up to date), where all… well, addon configs, are now located (basically the “persistent data” for the docker containers).
Not really sure what to say in that case (well, maybe check for typo’s, the first time I tried, it was pretty late, and I copied someone elses typo: /homeasistant/secrets.yaml
)
one thing I completely don’t understand about this entire setup: I don’t have a folder ‘homeassistant’ ?!
I’m running HA inside a VM on a windows 10 laptop.
And something else please; from the update 2024.4 there was a change in appdeamon yes?
That is why users with the NSpanel having isssues showing the weather card on the screensaver?
You should add this line to appdeamon.yaml: app_dir /homeassistant/apps but does this work without the actual folder ‘homeassistant’ ??
As I understood it, it’s the folder named config
, that Appdaemon (and other addons) now calls homeassistant
. So it’s just (mostly) an internal reference issue.
These are the “folders” (mounts) I have when using the Samba share addon:
.The one highlighted (config
) is where I have my secrets.yaml
, configuration.yaml
, etc., but in appdaemon.yaml
(now located on the other highlighted mount: addon_configs
in a subfolder named something with XXX_appdaemon
), it’s now referenced as /homeassistant/secrets.yaml
, not /config/secrets.yaml
as it “used to”.
Thank you, simple is always best. Done in a few seconds using the ever dependable File editor add-on.
Was getting very confused with all this talk of mounting and copying things, none of which are necessary.
Thanks for the help in this post. I solved it by just deleting the whole \addon_configs\a0d7b954_appdaemon directory.