Closed pacohope closed 1 year ago
Hey, how does your folder structure look?
Are you using Homeassistant OS / HASS OS or your own docker containers?
Check the folder structure, if there are no files redownload or reinstall in HACS. Restart the AppDeamon Addon afterwards.
Please restart the AppDeamon Addon and post the log here.
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.
a bit harsh, but true, please open up a separate issue with logs and config attached
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.
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.
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"
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.
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:![Screenshot 2022-09-29 at 23 17 57](https://user-images.githubusercontent.com/2158041/193183338-6311fa2f-5083-49ee-94e8-e824206b42aa.png)
[x] Provide your appdaemon.yaml: I have no MQTT password.
[x] Provide your apps.yaml:
[x] Go to Settings>Add-ons>AppDaemon>Log and then, provide the output of the log after restarting the appdaemon container:
ADDITIONAL INFORMATION
Some things I'm observing:
state
, I see:tele/nspanel/RESULT
topic and see messages. If I subscribe to thecmnd/nspanel/CustomSend
topic I never see anything.Thanks for your help!