How-to Upgrade to AppDaemon 15 #1029
Comments
|
@joBr99 Are they any recommended steps if we are starting from AppDaemon 14 (I did a restore this morning to a backup this morning when I got in trouble because the clock time stopped). |
|
wdym? The steps above should be everything you need to do the update. |
|
OK, I wasn't sure if there would be something I could do pre-emptively to configure the directories/yaml so that it worked when upgrading to 15. I am assuming after redownloading nspanel-lovelace-ui the custom configs we have will still work. |
|
Your apps.yaml&appdaemon.yaml won't be touched by redownloading the app from HACS. However the update from AppDaemon moves all files to a different directory, see my link to the docs on how to access the new folder. |
|
regarding these setting: so if i update on nspanel exists two times on my system
i assume, that's only on the upgraded systems the case and i can safely delete /addon_configs/a0d7b954_appdaemon/apps/nspanel-lovelace-ui? |
|
yes, the appdaemon upgrade moves the folder to |
|
sadly no... |
|
so here my appdaemon.yaml In my last post you can see, that the hello_world app gots running - > because it is still exists in addon_configs/........ |
|
It needs to be like this: However I'm currently trying to figure out how I convince appdaemon to load my apps.yaml ... |
|
thanks... is working |
|
So now I have a weird problem. I restored to my previous backup of 14.0, then reupgraded to 15.2. As expected AppDaemon is not running again, but now, without making the changes to my appdaemon yaml (at least that I can tell), I still see logs in AppDaemon and my NSPanel seems to be working. |
|
idk what you did, but without the appdaemon add-on running it's not going to do anything |
|
I see all of the following in the logs despite the main page info dialog saying Add-On is stopped. |
|
So I followed your instructions. The module will be loaded but then, these error messages come up. Any ideas? My NS-Panel is waiting for content. Tasmota and MQTT (configured inside Tasmota) work. 2023-11-15 22:06:49.367061 INFO HASS: All startup conditions met |
okay, never mind. I copy the apps.yml from the appdaemon addon into the old /homeassistant/appdaemon/apps folder, restarted everything and now it works :) |
|
so i followed all the steps above i have appdaemon running and my nspanel seemed to have refreshed and when i touch the screen my normal screen comes on but if i try to tap or swipe to the next screen it goes blank/black screen with the backlight on and is unresposive untill it dims and goes back to the normal screen again any ideas |
|
please provide the logs from appdaemon during this issue |
I have gone as far as removing appdaemon, and reinstalling after a reboot. |
|
|
@karlc28 Hard to tell like this, there is something wrong with your connection to home assistant. Please open a Waiting for Content Issue with your configs and the startuplog from appdaemon. |
|
@Jelloitsalive12 it has to run somewhere - you cloud check the docker containers running on the terminal or try to reboot hour Homeassistant OS (Advanced Options in the Restart Dialog - Reboot System) |
which configs would you need |
|
It's explained in the issue template, but basically apps.yaml and appdaemon.yaml - just open a new issue with that template. |
Thank you just to make it easier to see this is what I'm seeing |
|
Cannot help you like this, please open that issue and fill out the requested information. You Backend is dead - if you restart tasmota it's going to show the Waiting for content screen |
Thank you for the reminder about full reboot vs restarts I'd been doing! That was it, seems to be working as expected again. |
I'm having the same issue, I will this evening do some further investigation and provide some diagnostic logs. I don't think it's an AppDaemon 15 release issue. It started after the update of the Core and or the Supervisor to 2023.11.x |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Your indentation is wrong type has to be on the same level als entity. Also see #1204 and the latest release notes: |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
cannot tell you anything without the appdaemon log, also this is kina off topic here - please open a waiting for content issue with all of the requested information, tasmota config, appdaemon logs etc. |
|
perhaps the BABEL package is missing, by comparing the old settings from the backup this line is gone |
|
gave it up.....................restored backup.........................zzzzzzzzzzzzzzzzzzz...................thanks......................... |
|
did some more investigation: when I comment-out the 'app_dir: /homeassistant/appdaemon/apps/' line the file in the old location are used and the panel is working. 2024-04-21 19:23:57.465441 INFO AppDaemon: Configuration read from: /config/appdaemon.yaml the appdaemon.yaml is not there ?!? thanks |
|
if you change the app_dir to
You can get the folders back by uninstalling and reinstalling the apps in HACS. |
|
Yes of course they are there, I can see the date stamp is updated after uninstalling and reinstalling in the new location.For some reason the appdaemon is not working when pointed to a new directory Thanks
-------- Original message --------From: Johannes ***@***.***> Date: 21/04/2024 19:44 (GMT+01:00) To: joBr99/nspanel-lovelace-ui ***@***.***> Cc: madebywitteveen ***@***.***>, Comment ***@***.***> Subject: Re: [joBr99/nspanel-lovelace-ui] How-to Upgrade to AppDaemon 15 (Issue #1029)
if you change the app_dir to /homeassistant/appdaemon/apps/ you need to make sure that the apps you've installed though HACS are still there
image.png (view on web)
You can get the folder back by uninstalling and reinstalling the apps in HACS.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
This is a summary of the action you have to do after you've upgraded from AppDaemon 14 to 15.
You config files have been moved from
/config/appdaemonto/addon_configs/a0d7b954_appdaemonSee this if you need assistance to access the new folder:
https://docs.nspanel.pky.eu/configure_mqtt/#note-for-appdeamon-addon-version-15
There is one important change that you have to do to your
appdaemon.yaml, which is also mentioned in the release notes of the new version.appdaemon.yaml:from:
secrets: /config/secrets.yamlto:
secrets: /homeassistant/secrets.yamlThis should already fix appdaemon, but do not stop here; next steps are required to get updates though hacs.
appdaemon:key)move your apps.yaml from
/addon_configs/a0d7b954_appdaemon/appsto the old location within/homeassistant/appdaemon/apps/redownload the nspanel-lovelace-ui app from HACS
optional cleanup; delete the apps folder in the addon's directory
/addon_configs/a0d7b954_appdaemon/appsSee #1028 if you are interested in more Details around this mess.
The text was updated successfully, but these errors were encountered: