search

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

Confused by MQT Settings #6

Closed pabutterworth closed 2 years ago

pabutterworth commented 2 years ago

Hi, I dont think this is an issue, rather me getting confused with mqtt settings.

I'm really looking forward to getting this going, it's just what I was looking for.

I've got Tasmoto running, and have the waiting for content spinner.

I must admit I'm getting a little confused over the MQTT settings for this.

On the device, in Tasmota settings I setup the IP, username & password for the MQTT server, but also a channel. MQTT Host 192.168.1.68 MQTT Port 1883 MQTT TLS Disabled MQTT User mqtt_user MQTT Client panel-1 MQTT Topic panel-1-mqtt MQTT Group Topic 1 cmnd/tasmotas/ MQTT Full Topic cmnd/panel-1-mqtt/ MQTT Fallback Topic cmnd/panel-1_fb/ MQTT No Retain Disabled

Now this is where I'm a little confused, how do these map to the settings in apps.yaml?

What should I have in?

panelRecvTopic: "cmnd/panel-1-mqtt/" panelSendTopic: "cmnd/panel-q/CustomSend"

Thanks Paul

joBr99 commented 2 years ago

panelRecvTopic: "tele/panel-1-mqtt/RESULT" panelSendTopic: "cmnd/panel-1-mqtt/CustomSend"

The settings in this picture are correct for the example apps.yaml https://github.com/joBr99/nspanel-lovelace-ui/blob/main/doc-pics/tasmota-mqtt-config.png

pabutterworth commented 2 years ago

Thanks for the fast response, i'll take a look, bit I think I may have more fundamental issues!

pabutterworth commented 2 years ago

So, i'm a little confused.

My Appdaemon log shows: 2022-04-13 15:02:52.324838 INFO HASS: Connected to Home Assistant 2022.4.3 2022-04-13 15:02:52.339991 CRITICAL MQTT: Could not complete MQTT Plugin initialization, for Connection was refused due to Not Authorised 2022-04-13 15:02:52.346445 CRITICAL MQTT: Could not complete MQTT Plugin initialization, trying again in 5 seconds 2022-04-13 15:02:52.350926 CRITICAL MQTT: MQTT Client Disconnected Abruptly. Will attempt reconnection

But I've definitely got the correct IP, username and password in it, as I've tested it using MQTT_explorer, any suggestions? image

joBr99 commented 2 years ago

take a look at the log of your mqtt broker, maybe there's more information why the authentication fails

pabutterworth commented 2 years ago

So I'm using Mosquitto.

What's in there is lots of this. This confuses me too, 192.168.1.31 is my work laptop, from which I was using mqtt_explorer successfully. I've closed that app and it still seems to be appearing.

1649856321: New connection from 172.30.32.1 on port 1883. 1649856321: New client connected from 172.30.32.1 as 360WkqCL2aukvcmgFrbMrS (p2, c1, k60, u'mqtt_user'). 1649856321: New connection from 192.168.1.31 on port 1883. 1649856321: Socket error on client , disconnecting. 1649856323: New connection from 192.168.1.31 on port 1883. 1649856323: Socket error on client , disconnecting.

pabutterworth commented 2 years ago

AH just noticed one of these:

1649856699: New connection from 192.168.1.26 on port 1883. 1649856699: Socket error on client , disconnecting.

Thats the IP address of the NSPANEL.

joBr99 commented 2 years ago

The connections from appdaemon are looking like this in my mosquitto log:

1649789611: New connection from 172.30.32.1 on port 1883.
1649789611: New client connected from 172.30.32.1 as appdaemon (p2, c1, k60, u'mqttuser').
1649789685: Client appdaemon disconnected.
1649789691: New connection from 172.30.32.1 on port 1883.
1649789691: New client connected from 172.30.32.1 as appdaemon (p2, c1, k60, u'mqttuser').
pabutterworth commented 2 years ago

OK, so not exactly sure what I did, but it's working now. Now the fun starts, trying to build the UI!