Node red doc for mqtt in (dynamic) is somewhat lackluster. Trying this for the first time, I see what's presented, but not sure what "broker" is (type?), compared url and port. Also I don't see anywhere to specify client id. Luckily, thanks to amazing community, there are some existing discussions w…

[image] ThingsTinkerer: assume "dynamic" config can't dynamically set client id? Asked 6 days ago Can the MQTT ClientID be set dynamically?

You should take a read of this great tutorial of MQTT: [image] MQTT Essentials - All Core Concepts Explained MQTT Essentials: Learn the core concepts of MQTT, its features and other essential information about the protocol for IoT and IIoT. to get a handle o…

Broker would be the IP of the broker (should possibly say server as in config title). But there are many topics on this in the forum, here is one from the nodes maintainer that has many examples Dynamic MQTT LWT birth, Close & Will Property - #2 by Steve-Mcl I am surprised these examples have not …

I want to set the connection credentials in function node. That requires "dynamic settings" to get input. Then the doc says the following: broker broker For the "connect" action, this property can override any of the individual broker configuration settings, including: broker port ur…

Thanks! Yeah the only official examples I found was the simplified version with hardcoded connection in config node. Broker is IP of broker? How does that compare to URL then? Cause I normally enter IP into url fields, ref http.

MQTT in gives linting error if not setting a broker config node. I don't want broker config node, as this is set dynamically. Unless broker config node can take dynamic env variables (which as far as I can see, it cannot). If I add a dummy broker config node, it too gives linting error if not setti…

[image] ThingsTinkerer: Broker is IP of broker? How does that compare to URL then? URl would be a ip or domain with port, and would override broker and port. e.g 192.168.1.20:1883

Got it thanks! Now onto client id... :thinking: Also struggling with getting the auto-connect feature of static config applied to dynamic config. Only way I found so far is to add status node, listen and filter status changes from mqtt-in and then send it to function node before mqtt-in node. A bit…

[image] ThingsTinkerer: "force" (boolean) arg in broker seems interesting and useful. Is this documented anywhere? It is mentioned at the bottom of the sidebar help text If this property is set and the broker is already connected an error will be logged unless it has the force property set …

Good find! Unfortunately node red hijacks browser ctrl+f to search doc, so I'm struggling a bit to change muscle-memory to use F3 instead. I assume "dynamic" config can't dynamically set client id?

Thanks, somehow that didn't show up when I made this topic and also failed at finding it when searching. Would be wonderful to have all these "secret" attributes documented in HELP section :star_struck: But for me, I get what I need now with that great community example.

Node-RED

Node-RED Forum

Insufficient dynamic mqtt documentation?

General

E1cid 17 October 2024 12:37 11

Asked 6 days ago Can the MQTT ClientID be set dynamically?

Topic		Replies	Views
MQTT nodes need a dummy broker entry to allow fully dynamic settings? Feature Requests mqtt	5	127	29 January 2026
Dynamic MQTT node's "actions->connect" guidance needed General mqtt	3	1535	10 March 2022
Other dynamic parameters in MQTT in General	4	431	4 September 2022
Configure mqtt-broker node from Dashboard General node-red-dashboard , mqtt	14	677	24 November 2022
Dynamic Settings on MQTT Node General mqtt	3	158	29 December 2024

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Insufficient dynamic mqtt documentation?

Related topics