joBr99 / nspanel-lovelace-ui

Custom Firmware for NsPanel with the design of HomeAssistant's lovelace UI in mind, works with Tasmota.
GNU General Public License v3.0
872 stars 188 forks source link

[Help] Waiting for Content #1104

Closed nabilxp closed 9 months ago

nabilxp commented 9 months ago

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!

image

image


- [x] Provide your apps.yaml:

apps.yaml here:

image

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

Log output here:

image



### ADDITIONAL INFORMATION

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

I use the Ass_on AppDaemon of HomeAssistant 
thank you for your help, everything worked well before, but since the loss of my HM SD card, nothing works, despite the reconfiguration of all the modules, and 2 months of research

i think problem come from communication between AppDaemon and mqtt
joBr99 commented 9 months ago

You've posted the log from mosquitto - not from appdaemon

nabilxp commented 9 months ago

you are right, I just updated my comment, I first found that appdeamn was not starting because of a problem accessing the secret file, I commented on the line about using the secret file , it started well, but still same problem

joBr99 commented 9 months ago

First of all you need to fix this error with the mqtt configuration of appdaemon:

2023-12-2s CRITICAL Enrr: due to Not Authorised Could not ccztpiete MQTT Plugin initializaticn, for Connection was refused

Looks like the user/password in the appdaemon config doesn't work. Mosquitto log might provide you additional context on the issue.

(Also seen another issue, but please fix the MQTT one first, one step after another)

nabilxp commented 9 months ago

thnks for your help,I use a user that I created in homa assistant, I have to put quotes in the appdeam file configuration, for the user and the password?

joBr99 commented 9 months ago

it doesn't hurt to have " quotes - but in general you don't need them

https://stackoverflow.com/questions/19109912/yaml-do-i-need-quotes-for-strings-in-yaml

nabilxp commented 9 months ago

I checked login and password 10 times, each time restarting HA, but without success, can i use an other acount ,than the on from HA ? what is the http parameter, url of the appdeamon configuration for? What should I put as url?

nabilxp commented 9 months ago

I have something weird in the Mosquitto broker log, New connection from 172.xx.xx.1:49574 on port 1883, this IP address is not mine, it's as if appdeamon is trying to connect to an external address, and why port 49574? I will offer you coffee if you can find my problem :)

joBr99 commented 9 months ago

this is fine; 172.XX is the IP Address of the appdaemon container and 49574 is the client/source port of the connection

you can safely ignore the http stuff from appdaemon - it's not used

You can configure a username password in the mosquitto configuration.

image

nabilxp commented 9 months ago

It finally works, I had to add: broker: "core-mosquitto" in the appdaemon conf file

nabilxp commented 9 months ago

I found this in a forum, someone had the same problem as me :)

joBr99 commented 9 months ago

Is your app starting now? Please provide the appdaemon log again if it isn't.

nabilxp commented 9 months ago

It's working now thanks