Waiting for Content - This may be taking longer than usual... about nspanel-issue-graveyard

[joBr99]

where's your apps.yaml?
it belongs into /config/appdaemon/apps/ folder and not into /config/appdaemon/apps/nspanel-lovelace-ui

should look like this:

if it's still not working please post your apps.yaml

[burghs]

as follows:

this is the apps.yaml:

"
nspanel-1:
module: nspanel-lovelance-ui
class: NsPanelLovelanceUIManager
config:
panelRecvTopic: "tele/nspanel/RESULT"
panelSendTopic: "cmnd/nspanel/CustomSend"
timeoutScreensaver: 15 #in seconds, values between 5 and 60 are allowed
#brightnessScreensaver: 10
brightnessScreensaver:
- time: "7:00:00"
value: 10
- time: "23:00:00"
value: 0
locale: "de_DE"
timeFormat: "%H:%M"
dateFormat: "%A, %d. %B %Y"
weatherEntity: weather.burghs_home
pages:
- type: cardEntities
heading: Example Page 1
items:
- cover.garage_door
- input_boolean.away_lights
- binary_sensor.back_door_contact
- type: cardEntities
heading: Example Page 2
items:
- button.lamp_button
- input_button.alarm_button
- light.wled_2
- delete # To make sure we don't keep buttons from previous page (read this as 'empty')
- type: cardEntities
heading: Example Page 3
items:
- scene.morning
- scene.evening
- delete
- delete
- type: cardThermo
heading: Exmaple Thermostat
item: climate.example_climate
- type: cardMedia
heading: Exampe Media
item: media_player.spotify_user
"

[joBr99]

so panelRecvTopic and panelSendTopic looks good

so it looks like it's the server/username/password of your mqtt connection in appdaemon or on tasmota

you can check the appdaemon log and/or the log of your mqtt broker

appdaemon start should look like this:

2022-03-14 17:45:09.453310 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin
2022-03-14 17:45:09.456771 INFO MQTT: MQTT Plugin Initializing
2022-03-14 17:45:09.456895 INFO MQTT: Using 'appdaemon/status' as Will Topic
2022-03-14 17:45:09.456975 INFO MQTT: Using 'appdaemon/status' as Birth Topic
2022-03-14 17:45:09.457224 INFO AppDaemon: Initializing HTTP
2022-03-14 17:45:09.457395 INFO AppDaemon: Using 'ws' for event stream
2022-03-14 17:45:09.459305 INFO AppDaemon: Starting API
2022-03-14 17:45:09.461112 INFO AppDaemon: Starting Admin Interface
2022-03-14 17:45:09.461317 INFO AppDaemon: Starting Dashboards
2022-03-14 17:45:09.470341 INFO HASS: Connected to Home Assistant 2022.3.4
2022-03-14 17:45:09.494468 INFO MQTT: Connected to Broker at URL 192.168.75.30:1883
2022-03-14 17:45:09.497216 INFO AppDaemon: App 'nspanel-kueche' added
2022-03-14 17:45:09.497684 INFO AppDaemon: Got initial state from namespace mqtt
2022-03-14 17:45:09.497948 INFO MQTT: MQTT Plugin initialization complete

[burghs]

Restarted the appdaemon service to double check the logs:
"
2022-03-14 18:54:49.470323 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2022-03-14 18:54:49.667099 INFO HASS: HASS Plugin Initializing
2022-03-14 18:54:49.668524 INFO HASS: HASS Plugin initialization complete
2022-03-14 18:54:49.669726 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin
2022-03-14 18:54:49.710212 INFO MQTT: MQTT Plugin Initializing
2022-03-14 18:54:49.711919 INFO MQTT: Using 'appdaemon/status' as Will Topic
2022-03-14 18:54:49.713821 INFO MQTT: Using 'appdaemon/status' as Birth Topic
2022-03-14 18:54:49.716888 INFO AppDaemon: Initializing HTTP
2022-03-14 18:54:49.719685 INFO AppDaemon: Using 'ws' for event stream
2022-03-14 18:54:49.742862 INFO AppDaemon: Starting API
2022-03-14 18:54:49.756456 INFO AppDaemon: Starting Admin Interface
2022-03-14 18:54:49.759098 INFO AppDaemon: Starting Dashboards
2022-03-14 18:54:49.948929 INFO MQTT: Connected to Broker at URL 192.168.1.36:1883
2022-03-14 18:54:49.963791 INFO HASS: Connected to Home Assistant 2022.3.4
2022-03-14 18:54:50.040372 INFO AppDaemon: Got initial state from namespace mqtt
2022-03-14 18:54:50.043904 INFO MQTT: MQTT Plugin initialization complete
2022-03-14 18:54:50.114527 INFO AppDaemon: App 'nspanel-1' added
2022-03-14 18:54:50.118092 INFO AppDaemon: Found 1 total apps
2022-03-14 18:54:50.120797 INFO AppDaemon: Starting Apps with 1 workers and 1 pins
2022-03-14 18:54:50.124736 INFO AppDaemon: Running on port 5050
2022-03-14 18:54:50.321115 INFO HASS: Evaluating startup conditions
2022-03-14 18:54:50.336629 INFO HASS: Startup condition met: hass state=RUNNING
2022-03-14 18:54:50.338777 INFO HASS: All startup conditions met
2022-03-14 18:54:50.494491 INFO AppDaemon: Got initial state from namespace default
2022-03-14 18:54:52.159771 INFO AppDaemon: Scheduler running in realtime
2022-03-14 18:54:52.170397 INFO AppDaemon: Adding /config/appdaemon/apps to module import path
2022-03-14 18:54:52.172618 INFO AppDaemon: Adding /config/appdaemon/apps/nspanel-lovelace-ui to module import path
2022-03-14 18:54:52.181069 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/nspanel-lovelace-ui/nspanel-lovelace-ui.py - ignoring
2022-03-14 18:54:52.185570 INFO AppDaemon: App initialization complete
"
Tasmota:

NS Panel:

[joBr99]

can you post your appdaemon.yaml?

[joBr99]

nevermind, found the issue

in your apps.yaml

replace

module: nspanel-lovelance-ui
class: NsPanelLovelanceUIManager

with

module: nspanel-lovelace-ui
class: NsPanelLovelaceUIManager

[burghs]

oh my, cant believe i missed that. will give it a try and confirm. thank you.

[joBr99]

well is this typo still somewhere in the documentation? should be fixed at all locations

[burghs]

well is this typo still somewhere in the documentation? should be fixed at all locations

I will go over my entire config again to make sure it is all accurate. I fixed it in the apps.yaml but it was still stuck on the same screen after restarting the appdaemon service in HA and the NSPanel.

[joBr99]

Any change in your AppDeamon log?, previously it didn't load the app with the adjusted config it should now load it.

[burghs]

still getting the "WARNING AppDaemon: No app description found for: /config/appdaemon/apps/nspanel-lovelace-ui/nspanel-lovelace-ui.py - ignoring" in the log.

[burghs]

thank you, will give it another go by reinstalling.

…

On Tue, Mar 15, 2022 at 10:40 AM FraZe69 ***@***.***> wrote: I had the same problem until I realized that I did the installation in the wrong order. Please check in the Studio Code Server if you have the directory "nspanel-lovelace-ui" under /config/appdaemaon/apps. If not, then uninstall nspanel-lovellace-ui in the HACS and reinstall it. — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APD4UFVNEMYCDYRHBMXNAP3VABEI5ANCNFSM5QWBLKKQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[burghs]

All sorted, I ended up rolling back the entire installation of appdaemon, studio code and the tasmota configuration. I followed the guide again step by step and as soon as I got to the part of adding the mqtt topics in the appdaemon.yaml the nspanel screen changed from the "waiting for content". thank you for the quick responses and help !

[jormus]

well is this typo still somewhere in the documentation? should be fixed at all locations

its not, I don't know where it got the example from, but took me some time to figure this one out. :-)
have a look at this tool: https://rtyley.github.io/bfg-repo-cleaner/