Sure you are using 7-Zip? Seems like it is still WinZip or something.
okay, so I am back at 14.0 and see my AD files.
Can you please explain point 2?
with File Editor I dont see a folder name addon_configs
what do I need to access the folder by using the Terminal & SSH addon?
ah, I used WinZip - didnt know that there is a difference 
Just struggle with point 2 :/(
1 Like
Thank you, @andarotajo! I used to have the config Samba share mapped to a drive letter (H:) so I may need another mapped share to access the AppDemon configuration folder as well.
Now I tried to open both folders right from \\HOMEASSISTANT. They are visible and accessible:
In VS Code, the config part works but the AD folder does not seem to be accessible:
It seems that VS Code tries to retrieve the AD folder from within in the config share which fails. Is there another way to connect to both folders there?
Edit:
Now it works! 
Please see below!
Mhh haven’t done anything with my mapped drive yet but I also have it on config currently. Just tried opening the folders in VS Code and the following worked for me:
- New VS Code window
- File → Open Folder
- Open the Samba share using
\\<IP>\ - Open the first folder
- File → Add Folder to Workspace
- Select the other folder
Now I have both folders open. I’m on Windows if that matters
2 Likes
Now I got it working!
In the meantime, I tried it the other way around: As a first step, I have added the AD apps folder to the workspace. After that, I have added the config folder. For whatever reason, both folder do appear now within VS Code which is exactly what I wanted to achieve!
Thanks again and much appreciated, @andarotajo!
2 Likes
Hi,
struggling hard to get my sonoff NSPanel running with the Lovelace/AppDaemon combo…
I can’t find ANY of the folders and files that are mentioned for AD over the internet, not a single yaml-file, no folder, nothing. The AD server is, however, running fine, but I can’t find the missing yaml-files to edit and since AD has moved the locations, all previous online help documentations and videos have become redundant over night 
Could someone help me on locating those files that can’t seem to be localized by both file editor and VSCode?
I’m not using the File editor add-on but I’ve just installed it to see if I can help. If you go to the add-on configuration, is the option Enforce Basepath turned on? If yes, turn that off and reload the add-on and you should be able to navigate a level up where you find addon_configs
3 Likes
I did not change any of the options/configuration, just plain install.
Where can I set this up? go to the addon dashboard, click on AppDaemon and then third tab “configuration”? There is no option such as “Enforce Basepath”.
This option is available in the File editor add-on, not AppDaemon.
1 Like
I’m reeling from a dead AppDaemon after upgrades. I have an AD app that loads data from a CSV. Can someone give me the correct path to use after all of Home Assistant’s recent path updates? I used to look for
/config/appdaemon/apps/contacts.csv
I tried the path to where I now see AD via my Samba share…
/addon_configs/a0d7b954_appdaemon/apps/contacts.csv
and also simply contacts.csv
1 Like
For reference:
Where is the app located that reads this CSV? A relative path is better but it depends where the app is. Using contacts.csv requires the app to be in the same directory
It was in the same folder as the app, but simply using the file name didn’t work. Taking in @NathanCu 's tip, this worked: /config/apps/contacts.csv
1 Like
Yeah I think we all need to get familiar with that article. I’ve helped people with at least 6 variants of this issue today alone
With all these variants running around I’m beginning to feel like Mobius and the TVA 
1 Like
None of the proposed answers worked. No apps_config folder present. Nothing in backup, …
Tried to uninstall and install it again but still same error.
Is there way to completely remove it and do a fresh installation which works?
Please do not thread everyone as a linux expert. I don’t think that “It’s moved to its own folder” is a helpful answer. I’ve solved my problem and will share my way step by step so someone that does not familiar with linux can copy it.
My solution was using “Terminal & SSH” add on that you can install from the addons menu in HA. After launching it enter the web interface section and you’ll see a terminal screen. If you enter “ls” it will list you the directories of the root folder and you should see addon_configs folder mentioned in the earlier posts above. Enter “cd addon_configs” command to enter this folder. You’ll have to use “ls” command again because I understand that appdaemon creates a folder with different names in different systems. Mine was a0d7b955_appdaemon so I used “cd a0d7b955_appdaemon” to enter that folder, yours can be different, so please check it. Now type “nano appdaemon.yaml” to edit the config file. Change the secrets line as “secrets: /homeassistant/secrets.yaml” and press CTRL+X to quit. It will ask you if you want to save your changes, answer yes and you’ll return to terminal screen. Now go back to appdaemon addon and restart it, it should start without any errors.
Peace…
4 Likes
Thank you for your post. It help me to get my NSPanel back online. I try to understand what to do before you posted step by step direction , and it’s HELP. Thank you again
1 Like
With above contributions I also managed to fix AppDeamon. It now seems to work as intended in version 0.15.2. This is very much appreciated.
In AppDeamon I run the SchedyApp to maintain heating schedules. It works perfectly under AD version 0.14. Under AD version 0.15.2 it behaves different. The logs state all is fine.
For instance the
schedy_room.schedy_xyz
entities are not created and choice of schedules seem to be ignored by HA. Am I missing something out. The SchedyApp works with information frm the home assistant customize.yaml-file Do I also need to “re-map” this one -just a thought?
-----------------------------------------------------------
Add-on: AppDaemon
Python Apps and Dashboard using AppDaemon 4.x for Home Assistant
-----------------------------------------------------------
Add-on version: 0.15.2
You are running the latest version of this add-on.
System: Home Assistant OS 11.1 (aarch64 / yellow)
Home Assistant Core: 2023.11.2
Home Assistant Supervisor: 2023.11.3
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[removed part to shorten]
s6-rc: info: service init-appdaemon successfully started
s6-rc: info: service appdaemon: starting
s6-rc: info: service appdaemon successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023-11-18 22:49:55.695462 INFO AppDaemon: AppDaemon Version 4.4.2 starting
2023-11-18 22:49:55.696043 INFO AppDaemon: Python version is 3.11.6
2023-11-18 22:49:55.696533 INFO AppDaemon: Configuration read from: /config/appdaemon.yaml
2023-11-18 22:49:55.696973 INFO AppDaemon: Added log: AppDaemon
2023-11-18 22:49:55.697771 INFO AppDaemon: Added log: Error
2023-11-18 22:49:55.698230 INFO AppDaemon: Added log: Access
2023-11-18 22:49:55.698652 INFO AppDaemon: Added log: Diag
2023-11-18 22:49:56.090509 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2023-11-18 22:49:56.471088 INFO HASS: HASS Plugin Initializing
2023-11-18 22:49:56.471609 WARNING HASS: ha_url not found in HASS configuration - module not initialized
2023-11-18 22:49:56.472070 INFO HASS: HASS Plugin initialization complete
2023-11-18 22:49:56.472914 INFO AppDaemon: Initializing HTTP
2023-11-18 22:49:56.473802 INFO AppDaemon: Using 'ws' for event stream
2023-11-18 22:49:56.479807 INFO AppDaemon: Starting API
2023-11-18 22:49:56.484062 INFO AppDaemon: Starting Admin Interface
2023-11-18 22:49:56.484874 INFO AppDaemon: Starting Dashboards
2023-11-18 22:49:56.513681 INFO HASS: Connected to Home Assistant 2023.11.2
2023-11-18 22:49:56.748447 INFO HASS: Evaluating startup conditions
2023-11-18 22:49:56.785437 INFO HASS: Startup condition met: hass state=RUNNING
2023-11-18 22:49:56.791360 INFO HASS: All startup conditions met
2023-11-18 22:49:56.806642 INFO AppDaemon: App 'hello_world' added
2023-11-18 22:49:56.809114 INFO AppDaemon: App 'schedy_heating' added
2023-11-18 22:49:56.811253 INFO AppDaemon: Found 2 active apps
2023-11-18 22:49:56.812341 INFO AppDaemon: Found 0 inactive apps
2023-11-18 22:49:56.813448 INFO AppDaemon: Found 0 global libraries
2023-11-18 22:49:56.814540 INFO AppDaemon: Starting Apps with 2 workers and 2 pins
2023-11-18 22:49:56.818163 INFO AppDaemon: Running on port 5050
2023-11-18 22:49:56.856969 INFO AppDaemon: Got initial state from namespace default
2023-11-18 22:49:58.829966 INFO AppDaemon: Scheduler running in realtime
2023-11-18 22:49:58.837164 INFO AppDaemon: Adding /config/apps to module import path
2023-11-18 22:49:58.839884 INFO AppDaemon: Loading App Module: /config/apps/hello.py
2023-11-18 22:49:58.907509 INFO AppDaemon: Loading app hello_world using class HelloWorld from module hello
2023-11-18 22:49:58.910669 INFO AppDaemon: Calling initialize() for hello_world
2023-11-18 22:49:59.020654 INFO hello_world: Hello from AppDaemon
2023-11-18 22:49:59.022599 INFO hello_world: You are now ready to run Apps!
2023-11-18 22:49:59.024705 INFO AppDaemon: App initialization complete
Did anyone else have come across this? Thank you very much for a respond!
Update: I solved this issue by myself. I have not copied/created the hass_apps_loader.py into the AD-apps-folder. Automations now work as expected.