Page 1 of 1

OpenHAB MQTT broker connection failing all the time

Posted: 17 Apr 2017, 12:39
by lucaberta
Hi all,

I finally was able to spend some time learning Atom/PlatformIO and I quite like the new setup!

This enabled me to jump back onto ESPEasy after a few months of inactivity, and was able to compile and upload a 4M binary on a Wemos D1 Mini I have.

Everything worked at the first test, and I was able to configure my first ESPEast v2.0 build partly via the serial port and partly via the web interface.

I have a Mosquitto instance working well connected to both two Espurna instances (one on a NodeMCU and another on a Sonoff) and a Node-RED instance, all working well with Mosquitto, pulling and pushing messages from the MQTT broker.

Turns out the new ESPEasy instance cannot connect to same broker.

What I get in the serial console debug is:

Code: Select all

MQTT : Connection lost
MQTT : Failed to connected to broker
MQTT : Failed to connected to broker
What I get in the /var/log/mosquitto/mosquitto.log file is:

Code: Select all

1492425123: New connection from 192.168.1.104 on port 1883.
1492425123: Socket error on client <unknown>, disconnecting.
and I am getting quite a lot of these.

This happens no matter what choice of MQTT controller I choose, be it Domoticz, OpenHAB or PiDome. Same errors.

Is there anything I am missing? Is there any way to provide more debugging?

Many thanks,

Luca

Re: OpenHAB MQTT broker connection failing all the time

Posted: 17 Apr 2017, 14:07
by Shardan
Connections to Domoticz and FHEM seem not to work either.

See
https://www.letscontrolit.com/forum/vie ... 128#p15128

Shardan

Re: OpenHAB MQTT broker connection failing all the time

Posted: 17 Apr 2017, 14:37
by lucaberta
Shardan wrote: 17 Apr 2017, 14:07 Connections to Domoticz and FHEM seem not to work either.
not sure if the two things are related Shardan.

This is not about the web access to ESPEasy, which works well, but rather outgoing sockets from ESPEasy to the MQTT server.

Thanks, Luca

Re: OpenHAB MQTT broker connection failing all the time

Posted: 02 May 2017, 01:09
by psy0rz
Can you increase the serial log level to 10 (to get more debugging) and try again with the latest commit?

Could you also paste that log output somewhere?