[Help] Waiting for Content

[Montaneste]

PROBLEM DESCRIPTION

I'm seeing the waiting for content message on the Panel and I'm unable to find the configuration issue.

[] I've double checked each step explained in the FAQ:

https://docs.nspanel.pky.eu/faq/#waiting-for-content-this-is-taking-longer-than-usual-on-the-screen

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

• [x] Provide a screenshot of your tasmota mqtt configuration:

• [x] Provide your appdaemon.yaml:

  
  appdaemon.yaml here:

- [x] Provide your apps.yaml:

apps.yaml here:

- [x] Go to Settings>Add-ons>AppDaemon>Log and then, provide the output of the log after restarting the appdaemon container:

Log output here:

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting

---

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: Debian GNU/Linux 11 (bullseye) (aarch64 / qemuarm-64) 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.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-appdaemon: starting Looking in indexes: https://pypi.org/simple, https://wheels.home-assistant.io/musllinux-index/ Collecting babel Downloading Babel-2.13.1-py3-none-any.whl (10.1 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 10.1/10.1 MB 9.6 MB/s eta 0:00:00 Installing collected packages: babel Successfully installed babel-2.13.1 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv 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 [12:58:59] INFO: Starting AppDaemon... 2023-11-21 13:59:08.377385 INFO AppDaemon: AppDaemon Version 4.4.2 starting 2023-11-21 13:59:08.378045 INFO AppDaemon: Python version is 3.11.6 2023-11-21 13:59:08.378763 INFO AppDaemon: Configuration read from: /config/appdaemon.yaml 2023-11-21 13:59:08.379510 INFO AppDaemon: Added log: AppDaemon 2023-11-21 13:59:08.380271 INFO AppDaemon: Added log: Error 2023-11-21 13:59:08.381106 INFO AppDaemon: Added log: Access 2023-11-21 13:59:08.381810 INFO AppDaemon: Added log: Diag 2023-11-21 13:59:08.920060 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin 2023-11-21 13:59:09.483020 INFO HASS: HASS Plugin Initializing 2023-11-21 13:59:09.483582 WARNING HASS: ha_url not found in HASS configuration - module not initialized 2023-11-21 13:59:09.484245 INFO HASS: HASS Plugin initialization complete 2023-11-21 13:59:09.485299 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin 2023-11-21 13:59:09.683115 INFO MQTT: MQTT Plugin Initializing 2023-11-21 13:59:09.683746 INFO MQTT: Using 'appdaemon/status' as Will Topic 2023-11-21 13:59:09.684356 INFO MQTT: Using 'appdaemon/status' as Birth Topic 2023-11-21 13:59:09.686329 INFO AppDaemon: Initializing HTTP 2023-11-21 13:59:09.687547 INFO AppDaemon: Using 'ws' for event stream 2023-11-21 13:59:09.698047 INFO AppDaemon: Starting API 2023-11-21 13:59:09.705710 INFO AppDaemon: Starting Admin Interface 2023-11-21 13:59:09.706921 INFO AppDaemon: Starting Dashboards 2023-11-21 13:59:09.771717 INFO HASS: Connected to Home Assistant 2023.11.2 2023-11-21 13:59:09.878390 INFO MQTT: Connected to Broker at URL core-mosquitto.local.hass.io:1883 2023-11-21 13:59:09.894038 INFO AppDaemon: Got initial state from namespace mqtt 2023-11-21 13:59:09.895466 INFO MQTT: MQTT Plugin initialization complete 2023-11-21 13:59:09.896863 INFO AppDaemon: App 'nspanel-1' added 2023-11-21 13:59:09.899738 INFO AppDaemon: Found 1 active apps 2023-11-21 13:59:09.900931 INFO AppDaemon: Found 0 inactive apps 2023-11-21 13:59:09.902263 INFO AppDaemon: Found 0 global libraries 2023-11-21 13:59:09.903483 INFO AppDaemon: Starting Apps with 1 workers and 1 pins 2023-11-21 13:59:09.906201 INFO AppDaemon: Running on port 5050 2023-11-21 13:59:10.028209 INFO HASS: Evaluating startup conditions 2023-11-21 13:59:10.057954 INFO HASS: Startup condition met: hass state=RUNNING 2023-11-21 13:59:10.058774 INFO HASS: All startup conditions met 2023-11-21 13:59:10.213213 INFO AppDaemon: Got initial state from namespace default 2023-11-21 13:59:10.384857 INFO AppDaemon: New client Admin Client connected 2023-11-21 13:59:11.919180 INFO AppDaemon: Scheduler running in realtime 2023-11-21 13:59:11.937598 INFO AppDaemon: Adding /homeassistant/appdaemon/apps/ to module import path 2023-11-21 13:59:11.939170 INFO AppDaemon: App initialization complete

### ADDITIONAL INFORMATION

_Add information about your setup here, if any. (For example docker version of AppDaemon instead of the HomeAssistant Add-on)_

[joBr99]

you need to move your apps.yaml to /config/apps/appdaemon/apps

[Montaneste]

you need to move your apps.yaml to /config/apps/appdaemon/apps

i have /config/appdaemon/apps/apps.yaml

also made /config/apps/appdaemon/apps/apps.yaml

The result is the same :s

[joBr99]

try uninstalling the app in hacs and reinstalling it

[Montaneste]

try uninstalling the app in hacs and reinstalling it

unfortunatly already done that 2 :'(

[joBr99]

please send a screenshot of the folder structure of the /config/apps/appdaemon/apps/ folder

[marcinbojko]

Had exactly same problem 10 minutes ago - moved apps.yaml to /config/appdaemon/apps/apps.yaml Works as a charm.

[Montaneste]

uploaded again Berry Driver to Tasmota and is working again... xD

twilight zone device... o.O