MQTT : publish failed

[kenmullins64]

I've been struggling with this for a while. I'm using ESP_Easy_mega-20180507_dev_ESP8266_1024.bin on a Sonoff wifi smart switch and trying to send/receive MQTT messages to interface with Open Hab2.

I'm using MQTT.fx and MQTT spy to see the messages to/from. I can see messages coming from OH2 but nothing coming from or being consumed by ESPEasy.

I've tried connecting to my localhost:1883 via name and IP. I've tried connecting to test.mosquitto.org in case it was a localhost issue but all fail. I've tried with authentication and without.

I'm running everything on a Windows 8.1 install.

I'm just looking at the logs at the moment but may have to hook up the serial interface to see what is actually happening as the logs don't give a great deal of info. I've set the logs to debug dev.
10551: MQTT : publish failed
10551: MQTT : /ESP_Easy1/Status/uptime 0.00
The above 2 lines are all that I'm getting from the logs. There are no details about MQTT login errors.

I have cycled power after changes to the ESPEasy config with the same result.

I presume this is something very simple as so many peeps have this working. I may have fallen from the dumb tree today and hit a number of the branches on the way down though. I have many years in Software Development so I should be able to resolve this but it would seem not.

Any and all help gladly accepted.

[TD-er]

What broker are you using? (or am I in need of new coffee and did you mention it? I did see test.mosquito.org )

As far as I can see MQTT.fx (I just installed it here to see what it was) is just a client.
So ESPeasy and OpenHab must both connect to the same broker (and also your MQTT.fx to see the messages)

And what topics do you try to subscribe to?
When using "#" as subscription, you get to see all messages sent through the broker.

[kenmullins64]

Thanks for replying.

I'm using eclipse mosquito 3.1 as the broker. I thought mqtt.fx had it's own broker but I just found mosquito 3.1 running in the background from a previous attempt to get it running before moving to mqtt.fx.

I have been subscribing to all topics # locally and also narrowing the topics down when using a cloud broker (ESP_Easy1/#)

I'm only using the macro version of espeasy because the R120 wouldn't put my sonoff into AP mode (ESP_1). I also tried to upload the r120 using Arduino using the DOUT flash mode but it wouldn't compile. I could go back and blow away the Arduino install and do a fresh install and try and flash R120 again through Arduino if I can't get this macro version to fire.

All the messages below are coming from my OH2. 10.0.0.150 is my local Win 8.1 machine which is running everything (OH2, mosquito etc). I have tried using localhost instead of the IP with no luck.

mqtt.PNG (27.25 KiB) Viewed 7814 times

[kenmullins64]

I just reflashed a NodeMCU esp8266 that I have with r120 to see if I could see messages through that.

The install went fine and I can address it through the browser to turn an LED on/off (http://10.0.0.198/control?cmd=GPIO,13,1 http://10.0.0.198/control?cmd=GPIO,13,0) But it still won't talk to mosquito on 10.0.0.150?

This is doing my head in. I'm tempted to try TASMOTA to see if I can get any joy out of that

This is what the serial log is telling me.
10 ps:44 uS 1 ps:55
WD : Uptime 9 ConnectFailures 34 FreeMem 28072
MQTT : Connection lost
MQTT : Failed to connected to broker
MQTT : Failed to connected to broker
FLASH: Settings saved
FLASH: Settings saved
WD : Uptime 9 ConnectFailures 36 FreeMem 26736
MQTT : Connection lost
MQTT : Failed to connected to broker
MQTT : Failed to connected to broker
SW : GPIO 0 Set to 1
WD : Uptime 10 ConnectFailures 38 FreeMem 27992
MQTT : Connection lost
MQTT : Failed to connected to broker
MQTT : Failed to connected to broker

[ThomasB]

I'm using OH2 (Openhabian on RPI) with ESPEasy. I was using R120 but have recently switch to the Mega Branch. Both branches work for me.

I am using the eclipse MQTT broker. The OH2's services mqtt.cfg has been configured with my broker info (mosquitto.url & mosquitto.clientId).

I see that your main settings page is missing the Controller User and Password. Just a reminder: Be sure to populate those two fields with your MQTT login.

- Thomas

[waspie]

also, it sounds like you're trying to send commands *to* the esp via MQTT. you'll need the MQTT-Import plugin for that.
First you need to fix your other MQTT issues (see post above)