Odd MQTT connect behavior. Maybe AEDES broker node, maybe not

General
1

I am using project management. I maintain the project on one computer, push it to github, and then pull it down to another computer.

I am using Aedes broker node and it is installed on both computers.

I can create a MQTT Server node for localhost:1883 (I have also tried 127.0.0.1:1883) and it works just fine on the source node-red. But when I push and pull it, the MQTT-out node, for example, will not connect.

2

I don't know why Aedes might not work, but my advice would be to install Mosquitto.

3

If I understand correctly, you are using this node-red-contrib-aedes (node) - Node-RED ?
Like Colin, I prefer using mosquitto... However, as it avoids an external broker, that may be interesting in some cases.
Are you using authentication on MQTT ? It don't think you can "transfer" authentication through github.

4

Thanks.

I have previously used mosquito but I have a need to grab some of the messages from the broker and I take action based on what I see in node-red.

I have determined that it is an Aedes node issue and have posted an issue stating

I manage node-red replicated projects through github.

When I push and pull a node-red instance that contains the Aedes broker node, the node will not respond to MQTT nodes that are configured with either localhost or 127.0.0.1 as their server. I can change the server on the MQTT nodes to any other server and it works.

If I delete the Aedes broker node and drop it on the workspace and redeploy then it all works as expected. localhost and 127.0.0.1 can be accessed.
5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.