[Help] Waiting for Content

pacohope commented 1 year ago

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: I have no MQTT password.

appdaemon:
latitude: 38
longitude: -77
elevation: 30
time_zone: America/New_York
plugins:
HASS:
  type: hass
  ha_url: http://172.30.0.100:8123
  token: stuff-and-things
MQTT:
  type: mqtt
  namespace: mqtt
  client_id: "appdaemon"
  client_host: 172.30.0.100
  client_port: 1883
  client_topics: NONE
http:
url: http://172.30.0.100:5050/
admin:
api:
hadashboard:
logs:
main_log:
filename: /conf/logs/appdaemon.log
access_log:
filename: /conf/logs/access.log
error_log:
filename: /conf/logs/error.log
diag_log:
filename: /conf/logs/diag.log
log_generations: 5
log_size: 1024
format: "{asctime} {levelname:<8} {appname:<10}: {message}"

[x] Provide your apps.yaml:

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

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

2022-09-29 23:12:11.709564 INFO AppDaemon: AppDaemon Version 4.2.1 starting
2022-09-29 23:12:11.710138 INFO AppDaemon: Python version is 3.9.9
2022-09-29 23:12:11.710607 INFO AppDaemon: Configuration read from: /conf/appdaemon.yaml
2022-09-29 23:12:11.711154 INFO AppDaemon: Added log: AppDaemon
2022-09-29 23:12:11.711641 INFO AppDaemon: Added log: Error
2022-09-29 23:12:11.712089 INFO AppDaemon: Added log: Access
2022-09-29 23:12:11.712528 INFO AppDaemon: Added log: Diag
2022-09-29 23:12:11.752755 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2022-09-29 23:12:11.792182 INFO HASS: HASS Plugin Initializing
2022-09-29 23:12:11.792689 INFO HASS: HASS Plugin initialization complete
2022-09-29 23:12:11.793348 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin
2022-09-29 23:12:11.807673 INFO MQTT: MQTT Plugin Initializing
2022-09-29 23:12:11.808207 INFO MQTT: Using 'appdaemon/status' as Will Topic
2022-09-29 23:12:11.808618 INFO MQTT: Using 'appdaemon/status' as Birth Topic
2022-09-29 23:12:11.809845 INFO AppDaemon: Initializing HTTP
2022-09-29 23:12:11.810656 INFO AppDaemon: Using 'ws' for event stream
2022-09-29 23:12:11.819283 INFO AppDaemon: Starting API
2022-09-29 23:12:11.825776 INFO AppDaemon: Starting Admin Interface
2022-09-29 23:12:11.826668 INFO AppDaemon: Starting Dashboards
2022-09-29 23:12:11.849642 INFO HASS: Connected to Home Assistant 2021.12.10
2022-09-29 23:12:11.869479 INFO MQTT: Connected to Broker at URL 172.30.0.100:1883
2022-09-29 23:12:11.877049 INFO AppDaemon: App 'nspanel-1' added
2022-09-29 23:12:11.879691 INFO AppDaemon: Found 1 total apps
2022-09-29 23:12:11.880830 INFO AppDaemon: Starting Apps with 1 workers and 1 pins
2022-09-29 23:12:11.882689 INFO AppDaemon: Running on port 5050
2022-09-29 23:12:11.885644 INFO AppDaemon: Got initial state from namespace mqtt
2022-09-29 23:12:11.886472 INFO MQTT: MQTT Plugin initialization complete
2022-09-29 23:12:11.981164 INFO HASS: Evaluating startup conditions
2022-09-29 23:12:11.988598 INFO HASS: Startup condition met: hass state=RUNNING
2022-09-29 23:12:11.989406 INFO HASS: All startup conditions met
2022-09-29 23:12:12.020321 INFO AppDaemon: Got initial state from namespace default
2022-09-29 23:12:13.903492 INFO AppDaemon: Scheduler running in realtime
2022-09-29 23:12:13.911160 INFO AppDaemon: Adding /conf/apps to module import path
2022-09-29 23:12:13.914450 WARNING AppDaemon: No app description found for: /conf/apps/hello.py - ignoring
2022-09-29 23:12:13.916319 INFO AppDaemon: App initialization complete

ADDITIONAL INFORMATION

Some things I'm observing:

Tasmota is working fine on the nspanel. i can interact with it, configure it, etc.

I can load the AppDaemon UI on port 5050. If I look at state, I see:


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

I can subscribe to the tele/nspanel/RESULT topic and see messages. If I subscribe to the cmnd/nspanel/CustomSend topic I never see anything.

Thanks for your help!

joBr99 commented 1 year ago

Hey, how does your folder structure look?

Are you using Homeassistant OS / HASS OS or your own docker containers?

joBr99 commented 1 year ago

Check the folder structure, if there are no files redownload or reinstall in HACS. Restart the AppDeamon Addon afterwards.

joBr99 commented 1 year ago

Please restart the AppDeamon Addon and post the log here.

pacohope commented 1 year ago

Dude. @bdonnell if you would like help on YOUR problem, could you post your OWN issue, and not jump in here on mine? You're just confusing things. I get it that you might be seeing the same symptom ("Waiting for Content") but your reasons will be different from mine. For crying out loud. Issues are free, get one of your own.

joBr99 commented 1 year ago

a bit harsh, but true, please open up a separate issue with logs and config attached

lethargus commented 1 year ago

Dude. @bdonnell if you would like help on YOUR problem, could you post your OWN issue, and not jump in here on mine? You're just confusing things. I get it that you might be seeing the same symptom ("Waiting for Content") but your reasons will be different from mine. For crying out loud. Issues are free, get one of your own.

You're absolutely right, my apologies. I initially thought they were caused by the same thing, but that doesn't look to be the case after all. Looking at your config and comparing to mine it looks like yours is failing to pick up the card configuration for the panel itself, since that should be reflected in the appdaemon state. A completely different problem after all. Again, sorry.

pacohope commented 1 year ago

Yeah, I guess that was harsh. Sorry. 🙏

Ok. I have fixed at least part of my problem. The question about the file system was key. I run HomeAssistant in a docker container. I'm running AppDaemon in a DIFFERENT docker container. They don't share the same filesystem. So when HACS downloads something to /appdaemon/apps in my HA container, AppDaemon (in another container) can't see it. I moved the 2 directories (config-check and nspanel-lovelace-ui) from the filesystem for HA to my apps directory in my AD container, and my NSPanel. I might try some outside-of-Docker filesystem hocus-pocus to make the two directories the same. But for now, I understand how they're related.

So my nspanel connected to AppDaemon. Yay!

My next issue is that I have the US panel and I was planning to do it in portrait mode. I had downloaded the correct tft file, so things were looking right (i.e., the "Waiting for Content" stuff was displayed in the correct orientation). When the panel connected to AppDaemon, it said "hey, there's an updated firmware, do you want to load it?" I tapped YES and it downloaded a landscape version of the firmware. So now I have content from AppDaemon (yay!) but it's displayed in landscape mode (boo!).

Should I just run FlashNextion http://nspanel.pky.eu/lui-us-p-release.tft again?

I think this works. I think I can take it from here and adjust my apps.yaml file to put things on the panel. I guess any time HACS "updates" my nspanel-lovelace-ui, I need to make sure the changes get synchronised over to the AppDaemon container.

joBr99 commented 1 year ago

Yes, the issue with Docker HA/HACS and the seperate AppDaemon Container occured before. See joBr99/nspanel-issue-graveyard#12 for example. Unfortunately there is only documentation for Homeassistent OS.

You need something like this to map the folder of the appdaemon container to the location where hacs downloads it's stuff.

version: "3.5"
services:
  homeassistant:
...
    volumes:
      - ./docker-files/homeassistant/:/config

  appdaemon:
...
    volumes:
      - ./docker-files/homeassistant/appdaemon:/conf

For the screen orientation, just add model: "us-p" to your config. Without the model configued you will acually end up with the EU Firmware, which has a touch offset on US Models. There should be a message on the screen after adding model to your config, telling you that the model has changed asking for the update.

https://docs.nspanel.pky.eu/config-overview/

---
nspanel-1:
  module: nspanel-lovelace-ui
  class: NsPanelLovelaceUIManager
  config:
    panelRecvTopic: "tele/nspanel/RESULT"
    panelSendTopic: "cmnd/nspanel/CustomSend"
    model: "us-p"

pacohope commented 1 year ago

Thanks so much for your help. I got it working and everything was awesome. Then, while reassembling it, I manhandled it a bit and broke it. It doesn't power on any more. I'm such a moron. But, hey, the software works now and you were really quick and supportive! Thanks.

joBr99 / nspanel-issue-graveyard