Closed PeterAndreS closed 8 months ago
Would it be possible to have a symlink from /config/appdaemon
pointing to /addon_configs/a0d7b954_appdaemon
?
I guess that would
Would it be possible to have a symlink from /config/appdaemon pointing to /addon_configs/a0d7b954_appdaemon?
Not hat is not possible.
HACS is downloading appdaemon scripts to that folder:
HACS will not work with this add-on.
HACS will not work with this add-on.
What do you mean?, pretty sure that it is broken with the new version - but is it not fixable at all? Also not on HACS Side?
There are 60+ AppDaemon Scripts downloadable though HACS. https://github.com/hacs/default/blob/master/appdaemon
but is it not fixable at all? Also not on HACS Side?
HACS runs in Home Assistant, Home Assistant cannot access the new location of the add-on configuration. So, that isn't fixable.
but is it not fixable at all? Also not on HACS Side?
HACS runs in Home Assistant, Home Assistant cannot access the new location of the add-on configuration. So, that isn't fixable.
So we have no way of running our HACS scripts? I really need to roll back to 0.14, any info on how to do this would be great as I rely on a HACS script to manage my battery storage system
So we have no way of running our HACS scripts?
Sure, HACS downloads script from online and puts them in your apps
folder. You can do that yourself too 🤷
So we have no way of running our HACS scripts?
Sure, HACS downloads script from online and puts them in your
apps
folder. You can do that yourself too 🤷
But I don't have any access to anything but the homeassistant/ folder on HAOS
But I don't have any access to anything but the homeassistant/ folder on HAOS
no? You can access all these folders using one of the SSH add-ons, VSCode add-on, File-editor add-on or Samba add-on. There is even choice :)
But I don't have any access to anything but the homeassistant/ folder on HAOS
no? You can access all these folders using one of the SSH add-ons, VSCode add-on, File-editor add-on or Samba add-on. There is even choice :)
I do use the File editor add-on but my installation (HAOS VM) doesn't seem to allow access to anything outside of the homeassistant/ folder, when clicking the back button on File editor it does not do anything. I will try Visual Studio Code and pray.
But I don't have any access to anything but the homeassistant/ folder on HAOS
no? You can access all these folders using one of the SSH add-ons, VSCode add-on, File-editor add-on or Samba add-on. There is even choice :)
I deleted everything to do with AppDaemon and all my previous HACS scripts, installed AppDaemon again and it's still giving errors:
[17:17:09] INFO: Starting AppDaemon...
s6-rc: info: service legacy-services successfully started
ERROR Error loading secrets file: /config/secrets.yaml
Traceback (most recent call last):
File "/usr/bin/appdaemon", line 8, in <module>
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:
^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable
[17:17:21] INFO: Service AppDaemon exited with code 1 (by signal 0)
This is what I see in VSC in terms of file structure.
@OliveFinch
You can open the folder from VSCode.
https://github.com/joBr99/nspanel-lovelace-ui/issues/1028#issuecomment-1812901630
Sorry posted this in the wrong issue.
https://github.com/joBr99/nspanel-lovelace-ui/issues/1028#issuecomment-1813004321
For me the new Update Worked: Install the latest Update, Open the Folder in VSCode (Three Lines on Top, Open Folder like here Link appdaemon.yaml: Change the Line:
secrets: /homeassistant/secrets.yaml
Then i had to Change the apps.yaml -> my App was Missing, i had to add it again.
Thanks for all the Work!
Change it to:
logs: main_log: filename: /config/logs/appdaemon.log
Finally all is running again as before with the new path: 🙂👍, Thanks for the support!
This did not work for me
At first for me not as well, I had to manually create the logs-folder: /addon_configs/a0d7b954_appdaemon/logs Now it works again... 👍
HACS will not work with this add-on.
What do you mean?, pretty sure that it is broken with the new version - but is it not fixable at all? Also not on HACS Side?
There are 60+ AppDaemon Scripts downloadable though HACS. https://github.com/hacs/default/blob/master/appdaemon
@frenck I hate to say it but maybe this should be backed out for now, I don't really see any advantage to the change and lots of issues?
hate to say it but maybe this should be backed out for now
Sorry, I will not back out to support HACS, that makes zero sense.
This change is to make backup & restore actually work normally and as expected for people. There must be a very very very strong other reason to make that move not the best move.
hate to say it but maybe this should be backed out for now
Sorry, I will not back out to support HACS, that makes zero sense.
This change is to make backup & restore actually work normally and as expected for people. There must be a very very very strong other reason to make that move not the best move.
What I was trying to explain was that AppDaemon was working fine without issue, there are many add-ons that use AppDaemon that are installed and updated with HACS. Without HACS it's very hard to maintain these add-ons and is likely longer term to be a reason to move away from AppDaemon.
Surely there must be a way to allow HACS installs with AppDaemon to still work correctly?
Surely there must be a way to allow HACS installs with AppDaemon to still work correctly?
HACS runs in Home Assistant, Home Assistant itself has no access to the add-on configuration folders.
HACS runs in Home Assistant, Home Assistant itself has no access to the add-on configuration folders.
So why not allow users to install the apps in the old location (config/appdeamon) if they want to, knowing they aren't backed up?
Because I don't want too.
Adding more options isn't always the right thing. I'll end up with more support questions and unpredictable setups. That is not what these add-ons are about. If you are looking for maximum customizability, this add-on is not for you (as a matter of fact, add-ons are probably not for you at all in that case).
This change is to make backup & restore work, which is about the most important thing I can think of. Losing the ability to single-click install 60 different apps from HACS, is a small loss compared to that one (it even didn't cross my mind it was there when making the decision for this change).
../Frenck
Losing the ability to single-click install 60 different apps from HACS, is a small loss compared to that one (it even didn't cross my mind it was there when making the decision for this change).
For me as an app developer (https://github.com/springfall2008/batpred) it's a major issue as I can no longer give people automatic updates.
I'm afraid I don't have many alternatives:
Thoughts?
Thoughts?
Not really. As said, I haven't even considered all of this making the decision, and at this point, still don't consider it at all.
../Frenck
Losing the ability to single-click install 60 different apps from HACS, is a small loss compared to that one (it even didn't cross my mind it was there when making the decision for this change).
For me as an app developer (springfall2008/batpred) it's a major issue as I can no longer give people automatic updates.
I'm afraid I don't have many alternatives:
- Fork AppDaemon - this could be fine as I don't really need any updates for it going forward, but it will mean two versions out there forever.
- Migrate away from AppDaemon and build a HA add-on instead, this is extra work and doesn't add much value but will avoid the issue.
- Build my own automatic update system inside the app itself, this could probably work if AppDaemon apps are allowed to overwrite their own code?
- Have people manually update the app all the time - this isn't really desirable.
Thoughts?
seems this startup script is the easy way: https://docs.nspanel.pky.eu/prepare_ha/#required-configuration-for-appdaemon-addon-15
@weltmeyer That will work for now, the goal eventually is to remove access to Home Assistant itself (right now, it is available to make the migration possible).
@weltmeyer That will work for now, the goal eventually is to remove access to Home Assistant itself (right now, it is available to make the migration possible).
I think the fork is probably the best bet then.
Ultimately I don't see AppDaemon as very useful without a way to update the apps it runs :(
would it be possible to add the ability to to add a custom mapped folder? this makes to user decide if he want to keep his apps in a different folder. addons in that folder wont be backed up but in most cases will come from hacs anyway and dont need a backup
would it be possible to add the ability to to add a custom mapped folder?
You are repeating questions. This was asked and answered above.
All, upgraded to 15.2 and appdaemon now will not start with the error the appdaemon folder is empty since upgrade so am not able to edit the secrets line as mentioned elsewhere, I am at a complete loss here for now. Do I copy the previous contents of the appdaemon folder back from backup? Any ideas or am I waiting for 15.3?
s6-rc: info: service legacy-services successfully started
Traceback (most recent call last):
File "/usr/bin/appdaemon", line 8, in <module>
sys.exit(main())
ERROR Error loading secrets file: /config/secrets.yaml
^^^^^^
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:`
Losing the ability to single-click install 60 different apps from HACS, is a small loss compared to that one (it even didn't cross my mind it was there when making the decision for this change).
For me as an app developer (springfall2008/batpred) it's a major issue as I can no longer give people automatic updates. I'm afraid I don't have many alternatives:
- Fork AppDaemon - this could be fine as I don't really need any updates for it going forward, but it will mean two versions out there forever.
- Migrate away from AppDaemon and build a HA add-on instead, this is extra work and doesn't add much value but will avoid the issue.
- Build my own automatic update system inside the app itself, this could probably work if AppDaemon apps are allowed to overwrite their own code?
- Have people manually update the app all the time - this isn't really desirable.
Thoughts?
seems this startup script is the easy way: https://docs.nspanel.pky.eu/prepare_ha/#required-configuration-for-appdaemon-addon-15
Or as a workaround for now you just move the apps folder back to /homeassistant/appdaemon/apps folder.
Add: app_dir: /homeassistant/appdaemon/apps/ to your appdaemon.yaml
And all works as before :-)
Add: app_dir: /homeassistant/appdaemon/apps/ to your appdaemon.yaml
If if that's simple then it's all good :)
Thanks a lot that's way simpler than my workaround - should have checked appdaemon's documentation.
Hello, I have reverted to appdeamon 14.0 backup in panic and know cannot find my config anywhere, even in addon config I got only hello.py apps !!!
Hello, I have reverted to appdeamon 14.0 backup in panic and know cannot find my config anywhere.
Hi, try to rollback one version of AppDaemon. This worked for me.
It seems that AppDaemon 0.15.2 deletes the files inside the directory appdaemon
. But manually placing in the files does not solve it.
To rollback on the update follow these steps:
Hopefully this helps
EDIT: Remember to start the service after restore and uncheck the auto update for now until a fix is places.
All, upgraded to 15.2 and appdaemon now will not start with the error the appdaemon folder is empty since upgrade so am not able to edit the secrets line as mentioned elsewhere, I am at a complete loss here for now. Do I copy the previous contents of the appdaemon folder back from backup? Any ideas or am I waiting for 15.3?
I'm having exactly the same issue, upgrading directly to 15.2 deleted my appdaemon folder. Not sure if or how I can extract my script and yaml from Home Assistant backup.
Hi, try to rollback one version of AppDaemon. This worked for me.
Thanks, I'll try that!
Not sure if or how I can extract my script and yaml from Home Assistant backup.
If you can't seem to restore the backup. You could always
Then upload it to the correct directory in your HomeAssistant. For ease of use I used the add-on Samba Share. I use Windows and I just navigate to my HomeAssistant IP-address when Samba Share was active..
Hello, I have reverted to appdeamon 14.0 backup in panic and know cannot find my config anywhere.
Hi, try to rollback one version of AppDaemon. This worked for me. It seems that AppDaemon 0.15.2 deletes the files inside the directory
appdaemon
. But manually placing in the files does not solve it.To rollback on the update follow these steps:
- Go to settings
- System
- Backups
- Click on the backup from 0.14.0
- Select the mark and press restore.
- After restoring, restore your latest HomeAssistant backup. That way your configs files will restore. Which includes the files inside the appdaemon directory.
- Ones the HA backup is restored, restart AppDaemon.
- Should now work again.
Hopefully this helps
EDIT: Remember to start the service after restore and uncheck the auto update for now until a fix is places.
Thank you, I have restored my last core update that include config folder, unfortunately, I missed one week of work.
Restoring the previous version of the plugin from the backup seems to work, but those backup doesn't contain anything from my appadeamon folder. Where did you find yours?
Restoring the previous version of the plugin from the backup seems to work, but those backup doesn't contain anything from my appadeamon folder. Where did you find yours?
Inside the HomeAssistant backups, not the AppDaemon backups.
Damn, the core one from last friday then :-/
Damn, the core one from last friday then :-/
No, just download the backup and extract from HomeAssistant.tar.gz only the AppDaemon folder!
Yes, I understood, it's just that my last backup is from friday and I'll lost all the work I have done this weekend :-/
What worked for me:
HTH, success with recovering!
Op wo 15 nov 2023 om 21:47 schreef Devid Treuling @.***
:
Damn, the core one from last friday then :-/
No, just download the backup and extract from HomeAssistant.tar.gz
— Reply to this email directly, view it on GitHub https://github.com/hassio-addons/addon-appdaemon/issues/287#issuecomment-1813238827, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5ASZANHTHC7ZEZ5XAFLLMTYEUS4TAVCNFSM6AAAAAA7MJDCX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGIZTQOBSG4 . You are receiving this because you commented.Message ID: @.***>
Following this thread I got AD working again, but I can no longer find the log files?
They used to be at: /config/appdaemon/logs but nothing here, also checked: /homeassistant/appdaemon/logs nothing here either
There is a log at: /addon_configs/a0d7b954_appdaemon/logs but it's old and hasn't been updated
My appdaemon.yaml has the logging sestup like:
logs: main_log: filename: /config/appdaemon/logs/appdaemon.log error_log: filename: /config/appdaemon/logs/error.log
Also, dashboards no longer work and I can't check the logs to see why!
Must admit, kinda confused as to what happened here!
Thanks, Bob
keep in mind the "incorrect migration" did copy over the current files like apps.yaml to the new location (at least in my situation), so I could reuse this including changes from just before the upgrade..... which was better as the HA backup version.
Hope this is clear ;-)
Op wo 15 nov 2023 om 21:51 schreef Pierre-33 @.***>:
Yes, I understood, it's just that my last backup is from friday and I'll lost all the work I have done this weekend :-/
— Reply to this email directly, view it on GitHub https://github.com/hassio-addons/addon-appdaemon/issues/287#issuecomment-1813244248, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5ASZAKEKO3F5BG5L6JMFY3YEUTOJAVCNFSM6AAAAAA7MJDCX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGI2DIMRUHA . You are receiving this because you commented.Message ID: @.***>
@xtalker
I guess you want the logs in your AD directory? Try changing your logging paths to logs/appdaemon.log
and logs/error.log
respectively. Not sure where the add-on has the working directory but if that doesn't work you can try prepending the path to the AD config, so addon_configs/a0d7b954_appdaemon/logs/..
keep in mind the "incorrect migration" did copy over the current files like apps.yaml to the new location (at least in my situation), so I could reuse this including changes from just before the upgrade..... which was better as the HA backup version.
Wait what... where is this magical folder which should contain all my precious file? :)
keep in mind the "incorrect migration" did copy over the current files like apps.yaml to the new location (at least in my situation), so I could reuse this including changes from just before the upgrade..... which was better as the HA backup version.
Wait what... where is this magical folder which should contain all my precious file? :)
The release page has the information you need: https://github.com/hassio-addons/addon-appdaemon/releases/tag/v0.15.2
Unfortunately in my case the addon_configs folder is empty when I try to access it with Samba. It was too good to be true :-/
try \addon_configs\a0d7b954_appdaemon (I access it via the Samba share addon_configs, but ofcourse also on the filesystem itself)
Op wo 15 nov 2023 om 22:08 schreef Pierre-33 @.***>:
keep in mind the "incorrect migration" did copy over the current files like apps.yaml to the new location (at least in my situation), so I could reuse this including changes from just before the upgrade..... which was better as the HA backup version.
Wait what... where is this magical folder which should contain all my precious file? :)
— Reply to this email directly, view it on GitHub https://github.com/hassio-addons/addon-appdaemon/issues/287#issuecomment-1813263223, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5ASZAMEW3WTTQDWOFPVT6TYEUVLRAVCNFSM6AAAAAA7MJDCX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGI3DGMRSGM . You are receiving this because you commented.Message ID: @.***>
Problem/Motivation
Expected behavior
Actual behavior
Steps to reproduce
Proposed changes
Log: