martinav (Customer) asked a question.
I was hoping to use Node-Red and a MQTT broker to run data to/from an SQL table on my server. The AEDES (or whatever) wont install proper, but there is another one I found that seems fine, but It will never resolve connection. I need some help here. Seems rather typical to setup, but you know how that goes.
My BRX:
The logic:
The node:
Main setup
Brx connection info (I think???)
I would recommend you also try posting your question on Node-Red's community forum:
https://discourse.nodered.org/
@ADC Community_02 (Automationdirect.com)
Oh, nice! I will. I didnt know they had one.
Does it look setup correct? I feel like this is a port, authentication problem... yet I dont see these kind of errors on the BRX.
I was able to get AEDES installed on Node-Red and used the below setup for MQTT publish and subscribe on Do-More using the simulator.
@ADC Community_02 (Automationdirect.com)
What is your version on nodered? I cant get AEDES installed. I currently have the mosco (???) one installed. My version of nodered is 1.x. I'm trying to get it updated. I setup exactly as you did too. Careful to match QoS and port numbers.
I'm still waiting to hear back from my IT admin to see if the port is open.
Hi @martinav (Customer)
I have a series on Node-RED and use some MQTT Brokers.
https://accautomation.ca/series/node-red-iot-enabling-software/
This post shows the AEDES broker running within Node-RED on a Raspberry Pi.
https://accautomation.ca/productivity-plc-node-red-mqtt-p1000-p2000/
The broker you choose will depend on how many clients you want to connect with and where they are located.
Regards,
Garry
@Garry (Customer) ,
Now that I have basic connection made. Do you have a general theme on how I would setup 4, 5, 6+ plc's all needing to use MQTT at once? I'm guessing you would use a broker node on every PLC, and you would have a different port for each? This is if I want to use a single server for the NodeRed. Otherwise, I would need a rasberry pi or something on each PLC rig. Thoughts?
Thanks,
Rod
Well, I finally got t his. It helped a lot to use a MQTT simulator. I found one called MQTT.fx from www.softblade.de. Its a lot easier to get the broker setup, then setup your PLC. You arent fighting settings on both sides. So much easier to make setting tweaks on the node-red side.
Also, clairty of settings when you are asked for "server" settings also got me off center. Server is always the IP address of where to access your NodeRed broker. This was not clear to me for quite a while. I couldnt get past a server/slave kind of thing where one setting points to the IP of the other, etc. You actually never enter the IP of the actual PLC. Everything is pushed to/from the broker IP.
Thanks to all that helped.
Setting up a decent MQTT server for production use can be a bit tricky, but it's definitely doable. If you're having trouble with AEDES, there are other MQTT brokers like Mosquitto that are popular and reliable.
For your Node-RED setup, make sure you're using the correct MQTT node and that your broker's connection settings are configured properly. It's not uncommon to run into issues during setup, but with some troubleshooting, you should be able to get it working smoothly.If you're still struggling, consider asking for help on forums or communities dedicated to Node-RED or MQTT. Sometimes a fresh pair of eyes can spot the issue.Also, if you're looking for a reliable hosting solution, dedicated server hosting could be a good option. Check out https://www.ewebguru.com/dedicated-server-hosting.html for more info.
Well, I finally got t his. It helped a lot to use a MQTT simulator. I found one called MQTT.fx from www.softblade.de. Its a lot easier to get the broker setup, then setup your PLC. You arent fighting settings on both sides. So much easier to make setting tweaks on the node-red side.
Also, clairty of settings when you are asked for "server" settings also got me off center. Server is always the IP address of where to access your NodeRed broker. This was not clear to me for quite a while. I couldnt get past a server/slave kind of thing where one setting points to the IP of the other, etc. You actually never enter the IP of the actual PLC. Everything is pushed to/from the broker IP.
Thanks to all that helped.