New to the product - but have been using Mosquitto for a fair amount of time and have MQTT running from a number of android devices etc.

Flashed a Node-MCU with your software - absolutely brilliant how easy it was.

Stumbled my way through the initial config and all seems fine

However i am not getting anything showing up at the Mosquitto broker.

I fired up MQTT SPY on my laptop and changed the controller (Openhab MQTT) to point to my laptop IP address rather than the Mosquitto VM (I have mosquitto running on my laptop also)

I have told it to use IP address

192.168.1.134

I have changed the default Sub and pub templates to

%sysname%/#

%sysname%/%tskname%/%valname%

i.e. i have removed the leading /

IN MQTT Spy i can see the messages coming in

When i change the IP address to point to my Mosquitto on my Ubuntu VM - no messages come in

I have logging enabled to All on Mosquitto - on the Ubuntu VM - i am tailing the log file and can see all the other connection messages coming in from Node-red and the other clients - but nothing from ESP_Easy

I have the firewall disabled on Ubuntu.

They are both on the same flat IP network 192.168.1.x

I will roll back to an older firmware and see if that makes any diference - otherwise - any ideas ?

I went back to the 1.20 release and it worked fine to my Mosquitto on Node-Red (Ubuntu 16.04)

I was then curious to see what was going on

So i flashed a brand new Sonoff Basic - with ESP_Easy_mega-20180910_normal_ESP8266_1024

Flashing is fine - same problem.

My testing setup is as follows

Windows 10 laptop - IP 192.168.1.134

Mosquitto 1.5.1 running on there in a console window - started as Administrator

run Mosquitto with mosquitto -v

On my live setup - Ubuntu 16.04 192.168.1.35 - all latest updates applied as of yesterday through Webmin - Firewall/IPTables disabled, running Mosquitto V 1.4.8 as a daemon - this is live and has 6 different clients (Arduino Ether and ESP8266) talking to it with Arduino sketches - Node-Red also runs on the same box - i am running a tail-f of the mosquitto log file for all testing

On my firewall i have defined a static IP 192.168.1.104 for the sonoff - after a reboot it gets that IP and i can hit it with Chrome.

After flashing the latest mega (as above) to the Sonoff - i setup Openhab MQTT as the broker and point it at the IP address of my ubuntu system

I define a switch on GPIO12 in devices.

I remove the leading forward slash from both the pub and sub on the ESPEASY

I see nothing at all coming into the mosquitto broker on my ubuntu system (from the Sonoff)

If i change nothing except the IP address of the OpenHab broker to point to my laptop i can see messages coming in - i can also publish messages to the sonoff and turn the relay on and off from a command line mosquitto_pub on the windows box - so all is working OK

I have MQTT spy setup on my laptop so i setup two connections on it - one pointing at my ubuntu system to monitor all topics and one pointing at the windows mosquitto to monitor all topics.

I then fire up my 2nd ESPEasy on the nodemcu from my initial testing which is now running
Build: 120
Core Version: 2_3_0

It immediately connects to my Ubuntu system and starts pumping out measurements and i can see them turn up in my node-red dashboard

So in summary Build 120 connects to Ubuntu Mosquitto 1.4.8 no problems,
mega-20180910 will not - this is from two different devices

Remembering i also did this initial test on mega-20180904

I have no security on my Mosquitto broker on either machine (i.e. username/password/machine names are not needed or checked)

Any ideas guys ? I would really much prefer to run the newer builds and am happy to help you get to the bottom of this.

No i have not tried that - but i have no security on my setup i.e. i do not demand user/password combos nor do i tie it down to ClientIDs/IP addresses etc.

The sticking point i have is that i can take the exact same hardware i.e. the same physical device - put 1.2 on it and it works as expected - as soon as i flash the Mega 2 - it fails to connect - i can not see how that is anything in the Mosquitto setup - but as a pointer the exact same version of mosquitto on windows (10) - does work - so it would see to point to something that is different in the underlying comms

The client ID is not about security it is about identity. Every MQTT client introduces itself with an ID when connecting to the broker. I observed similar behavior when a client ID was not unique. The broker would reject connections from clients using an ID that is already in use by another connected client.

OK but that would then imply that there is something fundamentally different in the code in ESPEasy. V1.2 works fine to the broker, flash with 2 and it stops working. THats with Zero changes to the Broker