joBr99 / nspanel-issue-graveyard

place to move waiting for content issues to and to keep the search a bit cleaned up
0 stars 0 forks source link

[BUG] NSpanel "waiting for content.." #23

Closed MaxLaMenace10280 closed 1 year ago

MaxLaMenace10280 commented 1 year ago

Hello after having prepared the settings of the Nspanel, I am stuck at the "MQTT on AppDaemon" part. Indeed the NSPanel remains stuck on "waiting for content" The settings look correct to me. image image image image

joBr99 commented 1 year ago

You need to download the lovelace backend app in the homeassistant community store.

https://hacs.xyz/docs/setup/download/

image

image

MaxLaMenace10280 commented 1 year ago

this is already uploaded

image

joBr99 commented 1 year ago

Try to redownload or reinstall it, there has to be an Nspanel Lovelace UI folder in the Appdaemon folder.

MaxLaMenace10280 commented 1 year ago

I've already done it, I even deleted and restarted my "home assistant" server

joBr99 commented 1 year ago

deleted? so you are using homeassistant core with a docker container?

MaxLaMenace10280 commented 1 year ago

no the home assistant supervisor on windows 10 with virtual box

joBr99 commented 1 year ago

HACS is downloading to /appdaemon/apps/nspanel-lovelace-ui, without this folder and it's files it's not going to work.

try to use the redownload button in hacs

image

MaxLaMenace10280 commented 1 year ago

I already tried . Since my restart I have this kind of message in the log (appdaemon) image

joBr99 commented 1 year ago

Please paste your appdamen log after restarting the addon and your Appdaemon log here. there is something wrong with your mqtt config

MaxLaMenace10280 commented 1 year ago

image

joBr99 commented 1 year ago

You are using '192.168.1.92' as your mqtt host in tasmota and '192.168.75.30'. The IP in Appdaemon conf is wrong.

MaxLaMenace10280 commented 1 year ago

yes indeed it was me who made a mistake when restarting the server, but it's still the same image

joBr99 commented 1 year ago

might be related to your setup with virtualbox is 192.168.1.92 the ip address of your windows host?

you can try to use core-mosquitto.local.hass.io instead of the ip address

MaxLaMenace10280 commented 1 year ago

where can i find this address ?

joBr99 commented 1 year ago

put

       client_host: core-mosquitto.local.hass.io

into your config and try if that works

MaxLaMenace10280 commented 1 year ago

image

joBr99 commented 1 year ago

this usually means that your username/password isn't correct

you can get addional information on this from the log of your mosquitto addon

MaxLaMenace10280 commented 1 year ago

image it seems to be better, but my ns panel screen still shows the message "waiting..."

joBr99 commented 1 year ago

yes your mqtt topics don't match

the log says you have tele/mqtt_user/RESULT and in tasmota you are using nspanel_entree and not mqtt_user

adjust the panelRecv and Send in your apps.yaml to

    panelRecvTopic: "tele/nspanel_entree/RESULT"
    panelSendTopic: "cmnd/nspanel_entree/CustomSend"
MaxLaMenace10280 commented 1 year ago

sorry, i'm going to look stupid. lol but it's always the same image

joBr99 commented 1 year ago

sorry nspanel_entree was correct

please send the log in tasmota console and make sure that tasmota is connected to mqtt aswell

note that tasmota needs an mqtt password with more than 4 chars?

MaxLaMenace10280 commented 1 year ago

MQTT = image TASMOTA = image AppDaemon = image

joBr99 commented 1 year ago

go to the tasmota console (not config) and check the log there

MaxLaMenace10280 commented 1 year ago

image

joBr99 commented 1 year ago

yeah as expected tasmota isn't able to connect

you are using the wrong ip address, what's the ip address you are using to reach homeassistant and is this ip also working from a different computer/your phone

MaxLaMenace10280 commented 1 year ago

sorry, another error on my part, when restarting virtualbox the ip address had changed I now have my nspanel working. thank you very much for the help and sorry for the inconvenience