I have node-red running on a groov Epic(192.168.1.130) and I'm editing it on a laptop (.160). I installed the eclipse MQTT broker on a different computer (.150) plugged into the same unmanaged switch as the Epic. I have mosquitto running on the .150 and have opened port 1883 in the firewall. I can ping the .130 from the .150 so I know they can talk.
Have you got mosquitto and the Eclipse broker (whatever that is) both running on .150? You can't run two brokers on one machine (at least not on the same port).
Sorry. I am new to this so my terminology may be incorrect. The MQTT broker I downloaded is the Eclipse version. That may mean nothing at all but I didn't know so I included it.
Yes I did open the port. I created a rule for both outgoing and incoming.
I opened a second command line window on the .150 and published to a topic that I had subscribed to in the other window. I received 'hello world' from myself.
I will try the same thing on the .130 right now.
I read somewhere that the Eclipse version of MQTT broker may be the legacy version, so I checked that box in my troubleshooting efforts.
On the machine that is running node-red I changed the IP address for the config to the 192.168.1.130. Is that the correct method for testing it on the local machine? It is doing the same thing (connecting forever).
I still don't understand this. You must only run one broker. You can't run mosquitto and the eclipse broker at the same time. I suggest you disable the Eclipse one and stick to mosquitto.
I didn't see whether you tried running mqtt explorer or similar on the node red machine and see if it can talk to the .150 broker. That will tell you whether it is a node red problem or a problem accessing the broker.