[{"data":1,"prerenderedAt":300},["ShallowReactive",2],{"node-red-\u002Fnode-red\u002Fflowfuse\u002Fmqtt\u002Fmqtt-in":3},{"id":4,"title":5,"body":6,"description":292,"extension":293,"meta":294,"navigation":295,"path":296,"seo":297,"stem":298,"__hash__":299},"nodeRed\u002Fnode-red\u002Fflowfuse\u002Fmqtt\u002Fmqtt-in.md","MQTT In",{"type":7,"value":8,"toc":276},"minimark",[9,17,27,32,37,40,58,62,65,81,85,88,92,95,115,119,122,136,140,143,200,204,207,228,239,243,269,273],[10,11,13],"h1",{"id":12},"",[14,15],"binding",{"value":16},"meta.title",[18,19,20,21,26],"p",{},"This is an enhanced version of the standard MQTT In node, designed exclusively for FlowFuse users. The node features automatic configuration upon deployment. The ",[22,23,25],"a",{"href":24},"\u002Fdocs\u002Fuser\u002Fteambroker\u002F","MQTT broker client"," is created automatically alongside the node configuration when added to the canvas.",[28,29,31],"h2",{"id":30},"configuration-options","Configuration Options",[33,34,36],"h3",{"id":35},"server-configuration","Server Configuration",[18,38,39],{},"The server is automatically configured and managed by the FlowFuse platform. All FlowFuse MQTT nodes within an instance share a single broker connection, ensuring efficient resource utilization and consistent connection management across all flows. Access control can be managed through the broker client management interface, where permissions for subscribe and publish operations can be configured.",[41,42,43],"blockquote",{},[18,44,45,49,50,53,54,57],{},[46,47,48],"strong",{},"Note:"," When the first node is added to the canvas, a new ",[46,51,52],{},"Team Broker User"," linked to the FlowFuse instance is automatically created. By default, this user has ",[46,55,56],{},"subscribe-only"," permissions.",[33,59,61],{"id":60},"subscription-mode","Subscription Mode",[18,63,64],{},"The node supports two operational modes:",[66,67,68,75],"ul",{},[69,70,71,74],"li",{},[46,72,73],{},"Single topic mode",": Allows subscription to a fixed topic configured directly in the node settings",[69,76,77,80],{},[46,78,79],{},"Dynamic subscription mode",": Enables runtime control of subscriptions through input messages",[33,82,84],{"id":83},"topic-configuration","Topic Configuration",[18,86,87],{},"When operating in single topic mode, specify the MQTT topic to subscribe to in the node configuration. The topic field supports MQTT wildcard patterns for flexible message routing.",[33,89,91],{"id":90},"quality-of-service","Quality of Service",[18,93,94],{},"Select from three QoS levels:",[66,96,97,103,109],{},[69,98,99,102],{},[46,100,101],{},"Level 0",": Fire-and-forget delivery",[69,104,105,108],{},[46,106,107],{},"Level 1",": At-least-once delivery",[69,110,111,114],{},[46,112,113],{},"Level 2",": Exactly-once delivery (default)",[33,116,118],{"id":117},"output-format","Output Format",[18,120,121],{},"The node can automatically detect the message format or convert it to a specific type including:",[66,123,124,127,130,133],{},[69,125,126],{},"Buffer",[69,128,129],{},"String",[69,131,132],{},"Parsed JSON object",[69,134,135],{},"Base64 encoded string",[28,137,139],{"id":138},"message-output-properties","Message Output Properties",[18,141,142],{},"Each received message includes the following properties:",[66,144,145,152,158,164,170,176,182,188,194],{},[69,146,147,151],{},[148,149,150],"code",{},"msg.payload",": The message content as string or buffer",[69,153,154,157],{},[148,155,156],{},"msg.topic",": The MQTT topic from which the message was received",[69,159,160,163],{},[148,161,162],{},"msg.qos",": The quality of service level (0, 1, or 2)",[69,165,166,169],{},[148,167,168],{},"msg.retain",": Boolean indicating whether the message was retained on the broker",[69,171,172,175],{},[148,173,174],{},"msg.responseTopic",": MQTT version 5 response topic for request-response patterns",[69,177,178,181],{},[148,179,180],{},"msg.correlationData",": MQTT version 5 correlation data for message tracking",[69,183,184,187],{},[148,185,186],{},"msg.contentType",": MQTT version 5 content type descriptor",[69,189,190,193],{},[148,191,192],{},"msg.userProperties",": MQTT version 5 custom user properties",[69,195,196,199],{},[148,197,198],{},"msg.messageExpiryInterval",": MQTT version 5 message expiry time in seconds",[28,201,203],{"id":202},"topic-wildcard-patterns","Topic Wildcard Patterns",[18,205,206],{},"MQTT supports two wildcard characters for flexible topic matching:",[66,208,209,219],{},[69,210,211,218],{},[46,212,213,214,217],{},"Plus sign (",[148,215,216],{},"+",")",": Single-level wildcard",[69,220,221,227],{},[46,222,223,224,217],{},"Hash symbol (",[148,225,226],{},"#",": Multi-level wildcard",[41,229,230],{},[18,231,232,235,236,238],{},[233,234,48],"em",{},"* The ",[148,237,226],{}," wildcard can only be used at the end of a topic when defining subscriptions.",[33,240,242],{"id":241},"example-patterns","Example Patterns",[66,244,245,251,257,263],{},[69,246,247,250],{},[148,248,249],{},"sensors\u002F+\u002Ftemperature"," - Receives temperature readings from all sensor locations",[69,252,253,256],{},[148,254,255],{},"factory\u002F#"," - Receives all messages published under the factory topic hierarchy",[69,258,259,262],{},[148,260,261],{},"devices\u002F+\u002Fstatus"," - Receives status updates from all devices",[69,264,265,268],{},[148,266,267],{},"building\u002Ffloor1\u002F#"," - Receives all messages from floor 1 of the building",[28,270,272],{"id":271},"version-support","Version Support",[18,274,275],{},"This node fully supports MQTT version 5 features including response topics, correlation data, content types, user properties, message expiry intervals, and topic aliases. It maintains backward compatibility with earlier MQTT versions.",{"title":12,"searchDepth":277,"depth":277,"links":278},2,[279,287,288,291],{"id":30,"depth":277,"text":31,"children":280},[281,283,284,285,286],{"id":35,"depth":282,"text":36},3,{"id":60,"depth":282,"text":61},{"id":83,"depth":282,"text":84},{"id":90,"depth":282,"text":91},{"id":117,"depth":282,"text":118},{"id":138,"depth":277,"text":139},{"id":202,"depth":277,"text":203,"children":289},[290],{"id":241,"depth":282,"text":242},{"id":271,"depth":277,"text":272},"Enhanced MQTT In node for FlowFuse with automatic broker setup, dynamic subscriptions, wildcard topic support, and full MQTT v5 compatibility.","md",{},true,"\u002Fnode-red\u002Fflowfuse\u002Fmqtt\u002Fmqtt-in",{"title":5,"description":292},"node-red\u002Fflowfuse\u002Fmqtt\u002Fmqtt-in","fYS-gBVbUBAnCjhd2tSgBfcAEfjfNw5Z_xkQre1HL7w",1780070556888]