[Help] Waiting for Content

[deggle]

PROBLEM DESCRIPTION

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

[X] 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:

appdaemon: latitude: 0 longitude: 0 elevation: 30 time_zone: Europe/London plugins: HASS: type: hass ha_url: https://xxx token: xxx MQTT: type: mqtt namespace: mqtt client_id: "appdaemon" client_host: 10.0.3.1 client_port: 1883 client_user: "mqttuser" client_password: "mqttpassword" client_topics: NONE http: url: http://10.0.0.10:5051 admin: api: hadashboard:

- [X] Provide your apps.yaml:

apps.yaml here:

hello_world: module: hello class: HelloWorld

nspanel-bedroom: module: nspanel-lovelace-ui class: NsPanelLovelaceUIManager config: panelRecvTopic: "tele/nspanel-bedroom/RESULT" panelSendTopic: "cmnd/nspanel-bedroom/CustomSend"

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

Log output here:

2022-08-08 15:19:39.093445 INFO AppDaemon: AppDaemon Version 4.2.1 starting 2022-08-08 15:19:39.093541 INFO AppDaemon: Python version is 3.9.9 2022-08-08 15:19:39.093633 INFO AppDaemon: Configuration read from: /conf/appdaemon.yaml 2022-08-08 15:19:39.093730 INFO AppDaemon: Added log: AppDaemon 2022-08-08 15:19:39.093832 INFO AppDaemon: Added log: Error 2022-08-08 15:19:39.093919 INFO AppDaemon: Added log: Access 2022-08-08 15:19:39.093990 INFO AppDaemon: Added log: Diag 2022-08-08 15:19:39.102879 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin 2022-08-08 15:19:39.111263 INFO HASS: HASS Plugin Initializing 2022-08-08 15:19:39.111362 INFO HASS: HASS Plugin initialization complete 2022-08-08 15:19:39.111481 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin 2022-08-08 15:19:39.114192 INFO MQTT: MQTT Plugin Initializing 2022-08-08 15:19:39.114277 INFO MQTT: Using 'appdaemon/status' as Will Topic 2022-08-08 15:19:39.114334 INFO MQTT: Using 'appdaemon/status' as Birth Topic 2022-08-08 15:19:39.114543 INFO AppDaemon: Initializing HTTP 2022-08-08 15:19:39.114687 INFO AppDaemon: Using 'ws' for event stream 2022-08-08 15:19:39.116196 INFO AppDaemon: Starting API 2022-08-08 15:19:39.117508 INFO AppDaemon: Starting Admin Interface 2022-08-08 15:19:39.117780 INFO AppDaemon: Starting Dashboards 2022-08-08 15:19:39.160434 INFO HASS: Connected to Home Assistant 2022.6.7 2022-08-08 15:19:39.162153 INFO MQTT: Connected to Broker at URL 10.0.3.1:1883 2022-08-08 15:19:39.173244 INFO AppDaemon: Got initial state from namespace mqtt 2022-08-08 15:19:39.173415 INFO MQTT: MQTT Plugin initialization complete 2022-08-08 15:19:39.174378 INFO AppDaemon: App 'hello_world' added 2022-08-08 15:19:39.174916 INFO AppDaemon: App 'nspanel-bedroom' added 2022-08-08 15:19:39.175490 INFO AppDaemon: App 'nspanel-testarea' added 2022-08-08 15:19:39.175786 INFO AppDaemon: Found 3 total apps 2022-08-08 15:19:39.175980 INFO AppDaemon: Starting Apps with 3 workers and 3 pins 2022-08-08 15:19:39.176708 INFO AppDaemon: Running on port 5051 2022-08-08 15:19:39.211580 INFO HASS: Evaluating startup conditions 2022-08-08 15:19:39.214306 INFO HASS: Startup condition met: hass state=RUNNING 2022-08-08 15:19:39.214443 INFO HASS: All startup conditions met 2022-08-08 15:19:39.217698 INFO AppDaemon: New client Admin Client connected 2022-08-08 15:19:39.236754 INFO AppDaemon: Got initial state from namespace default 2022-08-08 15:19:41.180115 INFO AppDaemon: Scheduler running in realtime 2022-08-08 15:19:41.182743 INFO AppDaemon: Adding /conf/apps to module import path 2022-08-08 15:19:41.183723 INFO AppDaemon: Loading App Module: /conf/apps/hello.py 2022-08-08 15:19:41.185713 INFO AppDaemon: Initializing app hello_world using class HelloWorld from module hello 2022-08-08 15:19:41.228771 INFO hello_world: Hello from AppDaemon 2022-08-08 15:19:41.229293 INFO hello_world: You are now ready to run Apps! 2022-08-08 15:19:41.230044 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)_

HA and AD running in docker.

[joBr99]

Hey, can you add your docker compose of the appdaemon container?

[deggle]

version: '3'

services:

  appdaemon:
    container_name: appdaemon
    image: acockburn/appdaemon:latest
    entrypoint: "./dockerStart.sh"
    environment:
      HA_URL: "https://ha.url"
      TOKEN: "xxx"
      DASH_URL: "http://10.0.0.10:5051"
    ports:
      - 5051:5051
    volumes:
      - /share/path_to_storage/appdaemon:/conf

[deggle]

There's no obvious errors. I can see MQTT messages coming from the NSPanel (and it shows in HA etc). I'm not really understanding the data/mqtt flows between the various parts (tasmota/appdaemon/ha) so struggling to debug. Would welcome any pointers.

[joBr99]

Can you see the downloaded application from the appdaemon container? Maybe this is helpful: https://github.com/joBr99/nspanel-issue-graveyard/issues/12

[deggle]

Oh, I see - right - that may change things. Odd there's this interdependency on files. Will report back shortly...

[deggle]

Brill sorted, thank you. So is this becasue HACS is responsible for keeping \apps\nspanel-lovelace-ui up to date, but other than that's it operates independently?

[joBr99]

HACS AppStore runs within HomeAssistant and downloads the App to /config/appdaemon/apps/nspanel-lovelace-ui within the HomeAssistant Container. AppDaemon needs to have access to this folder to see the downloaded app.

[deggle]

Ok, thank you. Shame AppDaemon can't manage it's own downloads but I guess for most users it's easier to manage centrally. I am thinking of moving to HA OS in a VM rather than containers, but not made my mind up yet.

Thanks for your rapid help!

[joBr99]

I guess it makes kinda sense to reuse existing Community Store, as it's already there, but yeah something that is causing confusion.