Can't connect NodeMCU with MQTT

[salmanfaris]

Hi ,

Where did you installed the MQTT broker (server) and is it running background when your run the nodeRED application and is it installed on the same machine as nodeRED installed?

[sivanath]

@salmanfaris It is running locally on my computer. Yes, and is running in the background.

[salmanfaris]

@sivanath Before connecting via NodeRED , Could you try to create MQTT Subscribe and Publish client using the CLI and see it can transfer message payload with the same broker name?

[sivanath]

@salmanfaris Yes, I had tried that before and it was working fine. Infact, everything works perfectly when I connect with the online mqtt server, test.mosquitto.org. So, there's some problem with the local installation, while using my local IP. But I can't find that problem. I had also re-installed the mqtt, but still the same issue.

[salmanfaris]

@sivanath Does the local pub and sub is working over CLI?

[sivanath]

@salmanfaris It was working in CLI, but now it's showing multiple usages at the port

[swalahamani]

@sivanath

It looks like mosquitto is trying to register both IPv4 and IPv6 on the same port.

If IPv6 is not required for the application your use case, try changing the mosquitto.conf file as below for limiting it to ipv4:

# Set to `ipv4` to force the listener to only use IPv4, or set to `ipv6` to
# force the listener to only use IPv6. If you want support for both IPv4 and
# IPv6, then do not use the socket_domain option.
socket_domain ipv4

Please please make sure the default port 1883 is not already in use by any other programs. If yes, you can either kill those programs (not recommended) or change the port in mosquitto.conf file:

References: [1][2]

[sivanath]

@swalahamani @salmanfaris
I changed my conf file and specified ipv4
And this is the status of the port (from resource monitor):

Image: mosquitto.exe	
PID: 3732
Address: IPv6 loopback
Protocol: TCP
Port: 1883
Firewall Status: Allowed, not restricted

It is listening to mosquito..

[swalahamani]

@sivanath

Is it working now?

[sivanath]

@swalahamani No