Node-RED runtime and external MQTT broker: Effect of disabling the built‑in editor on subscription persistence

Answer

Disabling the built‑in editor (setting httpAdminRoot: false) does not prevent MQTT nodes from automatically re‑establishing QoS 1/2 subscriptions after a Node‑RED restart, nor does it affect the persistence of those subscriptions. The runtime that loads flows and manages MQTT connections operates independently of the editor HTTP server.

Explanation

Node‑RED consists of two loosely coupled parts:

• Editor HTTP server – provides the flow‑based UI; it is turned off by httpAdminRoot: false.
• Runtime engine – loads flows from disk (or memory), initializes nodes, and maintains MQTT connections. This engine runs regardless of the editor’s availability.

MQTT subscription persistence depends on:

• How flows are stored: if flows.json (or Projects) is written to disk, a restart reloads the exact same flow definitions, causing MQTT input nodes to recreate their subscriptions.
• Whether the broker retains messages (QoS 1/2) – this is a broker‑side property, unrelated to Node‑RED’s editor.
• Any in‑memory only mode (--no‑save) where flows are not persisted; in that case subscriptions are lost after a stop, independent of the editor setting.

Consequently, with editor disabled but flows persisted to disk, the behavior is identical to the editor‑enabled case.

Resource usage

For an idle MQTT‑only flow, disabling the editor saves the memory and CPU overhead of the admin HTTP server (typically a few megabytes of RAM and negligible CPU). The MQTT nodes themselves consume the same resources in both configurations.

Verification steps

1. Create a settings.js snippet:

   httpAdminRoot: false,

2. Deploy a flow containing an MQTT input node subscribing to a test topic (QoS 1 or 2).
3. Publish a retained message to that topic via the external broker.
4. Stop Node‑RED, then start it again with the same httpAdminRoot: false setting.
5. Observe that the flow receives the retained message, confirming the subscription was restored.
6. Repeat with the flow file set to a temporary location or using --no‑save; the subscription will be lost after restart, showing that flow persistence—not the editor—determines the outcome.