No topic causes all MQTT nodes to disconnect

[smcgann99]

Just noticed that injecting a message into MQTT out without setting a topic causes all MQTT nodes to disconnect for a few seconds.

I realise it should have a topic, but the node should really handle this more gracefully ?

It looks like the issue has been around for a few years -

Publishing to a wildcard MQTT topic disconnects all MQTT nodes

While playing with MQTT in Node-RED, I accidentally configured an mqtt out node to publish to a topic with a wildcard: topic/+. [{"id":"ca140429.24cef8","type":"inject","z":"3ac27de3.268a52","name":"","topic":"topic/+","payload":"","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":230,"y":140,"wires":[["ec98b238.b0cea"]]},{"id":"ec98b238.b0cea","type":"mqtt out","z":"3ac27de3.268a52","name":"","topic":"","qos":"2","retain":"true","broker":"72393540.a2a3fc","x":410,"y…

[Colin]

If you are using mosquitto then I think it may be that mosquitto disconnects you. In the mosquitto log I see
Client tigger disconnected due to malformed packet.

[smcgann99]

I am using Mosquitto, but if there is no topic defined, I think the node should just show an error and not pass to the broker, since this then affects all flows.

[knolleary]

Can you raise an issue on github so we can track and resolve?

[smcgann99]

Done -

No topic causes all MQTT nodes to disconnect