Yeah, forgot about _msgid
@wcx
(and others)
So if one of the flows works and can send all the messages, and this one doesn't.....
Yes, Colin just mentioned the _msgid part.
On the SENDING machine (Oh, also it may be handy to ..... join all the wires before going to the MQTT out node.) then you can simply add ONE wire to a debug node:
Put a debug node and check that part of the message and check for things like that being common to all messages.
(join the wires... `alt shift LMB (drag) the mouse over all the wires and they will be connected together.)
Team,
Here is what resolved my issue, I had one MQTT server configuration for all flows, I ended up trying a MQTT server configuration per flow and this magically sorted out my issue.
Perhaps all the flows each establishes new connections with the same specified client id and my broker does not like this.
Thanks for everyone's help though, much appreciated.
You must either use unique ClientIDs or nothing at all (which is the most common approach) when connecting to the same broker.
A broker will disconnect an existing connection if a new one with the same ClientID connects
my thinking was it will maintain a open connection for all the flows instead of starting and stopping a connection if and when messages are being sent
Since you did not respond to my request to see what the logs said it is difficult to comment further.
Normally one would only use one broker node as that is the most efficient way of doing it.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
