From fe0eaab9159fa304b22fb675a835b429fc080755 Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Mon, 6 Jul 2026 19:41:08 +0200 Subject: [PATCH 1/4] docs: clarify EMQX broker dependency and dependent features The docs still described Mosquitto as the platform broker and did not say which features depend on EMQX specifically. Consolidate the duplicated broker configuration sections, describe EMQX as the shipped broker with Mosquitto as legacy, explain what the Team Broker is and why it requires EMQX, state the self-hosted prerequisites for FlowFuse Expert, and add the Kubernetes Mosquitto to EMQX upgrade note. --- docs/install/configuration.md | 33 +++++++++++++++++-------------- docs/install/kubernetes/README.md | 2 +- docs/upgrade/README.md | 14 +++++++++++++ docs/user/expert/index.md | 2 ++ docs/user/teambroker.md | 16 +++++++++++++++ 5 files changed, 51 insertions(+), 16 deletions(-) diff --git a/docs/install/configuration.md b/docs/install/configuration.md index 2f57f84d3b..40063e65ca 100644 --- a/docs/install/configuration.md +++ b/docs/install/configuration.md @@ -115,8 +115,24 @@ Option | Description ## MQTT Broker configuration -By default, the platform runs without an MQTT broker. This restricts some features -in the platform, such as the Project Nodes, Device Actions and Remote Device Editing. +The platform uses an MQTT broker to provide real-time messaging between devices, +Node-RED instances and the platform. The broker shipped with the platform's +Docker Compose and Kubernetes installations is [EMQX](https://www.emqx.io/). It is +deployed and configured automatically by those installers. + +By default, the platform runs without an MQTT broker. This restricts what features +are available: + +- Without a broker: Project Nodes, Device Actions and Remote Device Editing are unavailable. +- The following features additionally require the platform broker to be EMQX, as they + rely on EMQX-specific capabilities (its authentication hooks, per-team topic + namespacing and management API): the [Team Broker](/docs/user/teambroker.md), + [FlowFuse Expert](/docs/user/expert/index.md) and real-time updates in the platform UI. + +[Mosquitto](https://mosquitto.org/) is supported at a legacy level for existing +installations: core platform messaging works, but the EMQX-dependent features listed +above are unavailable. Replacing the platform broker with a different customer-supplied +broker is not supported. If a broker has been setup in the platform, the following configuration is required: @@ -216,19 +232,6 @@ Option | Description `support.frontend.hubspot.trackingcode` | The numerical identifier within your [HubSpot Tracking Code](https://knowledge.hubspot.com/conversations/chat-widget-is-not-appearing-on-your-pages). Default: `null` -## MQTT Broker configuration - -The platform depends on the [Mosquitto MQTT Broker](https://mosquitto.org/) to -provide real-time messaging between devices and the platform. - -This is currently an *optional* component - the platform will work without the -broker, but some features will not be available. - -Option | Description ----------------|-------------- -`broker.url` | The full url to the platform broker. This is used by the platform and Node-RED instances to connect to the broker. For example: `mqtt://localhost:1883`. -`broker.public_url` | If set, this is the url provided to Devices to connect to the broker with. When running in a Docker or K8S environment, this url should be the externally addressable url the broker is provided on. This could be via WebSockets, for example: `ws://example.com:1884` - ## AI Configuration Option | Description diff --git a/docs/install/kubernetes/README.md b/docs/install/kubernetes/README.md index ec68498e35..3f84b65293 100644 --- a/docs/install/kubernetes/README.md +++ b/docs/install/kubernetes/README.md @@ -92,7 +92,7 @@ Before you begin, ensure you have the following: - [Digital Ocean](digital-ocean.md) - MicroK8s 5. **Ingress Controller:** [The Traefik](https://doc.traefik.io/traefik/) installed on the cluster. -6. **EMQX Operator:** This is required to install the required MQTT broker when the Team Broker features are enabled. Instructions for installing the operator can be found [here](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) +6. **EMQX Operator:** This is required to install the platform's MQTT broker when the broker is enabled. The broker provides device and instance communication, the Team Broker, and FlowFuse Expert. Instructions for installing the operator can be found [here](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) For a production-ready environment, we also recommend: * **Database:** Prepare dedicated database on a external database server (see [FAQ](#how-to-use-external-database-server%3F) for more details) diff --git a/docs/upgrade/README.md b/docs/upgrade/README.md index 97decaec8e..952d2dac55 100644 --- a/docs/upgrade/README.md +++ b/docs/upgrade/README.md @@ -28,6 +28,20 @@ Details of how to upgrade can be found for each deployment model: To upgrade the version of Node-RED your Instances run (for example, moving to Node-RED 5.0), see [Upgrading the Node-RED version](./nodered-version.md). +### Upgrading to 2.32 + +#### Kubernetes: default MQTT broker is now EMQX + +From Helm chart v2.78.0, the chart deploys [EMQX](https://www.emqx.io/) as the platform +MQTT broker, replacing Mosquitto. Existing installations are migrated automatically when +upgrading the chart. If the broker is enabled, the +[EMQX Operator](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html) +must be installed on the cluster before upgrading. + +Mosquitto remains supported at a legacy level for existing installations, but the +broker-based platform features (Team Broker, FlowFuse Expert, real-time UI updates) +require EMQX. See [MQTT Broker configuration](../install/configuration.md#mqtt-broker-configuration). + ### Upgrading to 2.6.0 #### Required AWS EKS configuration change diff --git a/docs/user/expert/index.md b/docs/user/expert/index.md index e3978e8e79..6c7e97f8cd 100644 --- a/docs/user/expert/index.md +++ b/docs/user/expert/index.md @@ -8,6 +8,8 @@ FlowFuse Expert is the AI built into FlowFuse and the Node-RED editor. It is not **FlowFuse Expert is automatically installed and available in all hosted and remote instances running within or connected to FlowFuse**, no manual installation or configuration required. For self-hosted Enterprise customers, FlowFuse Expert can be enabled on request. [Contact us](https://flowfuse.com/contact-us/) to get it set up on your infrastructure. +> **Note:** On self-hosted installations, FlowFuse Expert requires an Enterprise license and the platform's EMQX-based MQTT broker with the Team Broker feature enabled (see [MQTT Broker configuration](/docs/install/configuration.md)). Expert communicates through a bridge between your platform broker and FlowFuse's central Expert service, which is set up as part of enabling Expert. Installations running without EMQX, for example legacy Mosquitto-based installs, cannot enable Expert. + ## Managing AI Features **Team owners** can enable or disable all AI features for their team from the team settings page. When disabled, the Expert chat panel with all AI feature will get removed for that team. Running instances need to be restarted for the change to take full effect. diff --git a/docs/user/teambroker.md b/docs/user/teambroker.md index a45ae47c2d..f9eb1be92a 100644 --- a/docs/user/teambroker.md +++ b/docs/user/teambroker.md @@ -8,6 +8,22 @@ When FlowFuse is deployed with an Enterprise license from v2.11.0 onwards comes This is a single shared MQTT broker, but each team has their own separate topic space and the ability to provision credentials for clients. +## What the Team Broker is + +The Team Broker is a multi-tenant MQTT broker service built into the FlowFuse platform: +one broker instance, managed by the platform, where every team gets its own fully +isolated topic space and can provision client credentials in a self-service way. It +removes the need to install and operate a separate broker to move MQTT data between +devices, Node-RED instances and other clients. + +Under the hood the Team Broker is provided by [EMQX](https://www.emqx.io/), and the +platform integrates with EMQX-specific capabilities for client authentication, per-team +topic isolation and bridging. The Team Broker cannot be backed by a different broker +(see [MQTT Broker configuration](/docs/install/configuration.md)). If your company +already operates its own MQTT broker, that broker can still be connected to FlowFuse +as an external broker to browse its topic hierarchy alongside the Team Broker, and +Node-RED instances can connect to it directly as a regular MQTT client. + ## Foreword FlowFuse offers zero config MQTT integration with the Team Broker via the [FlowFuse MQTT Nodes](/docs/user/mqtt-nodes/) that greatly simplifies the whole process by removing the need for manual configuration. From cbce4c8f86c8105c39c3c2f5e53c43b3fff14e99 Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Mon, 6 Jul 2026 23:29:43 +0200 Subject: [PATCH 2/4] docs: address broker review feedback Restore the fuller broker.url/broker.public_url descriptions, correct the Kubernetes upgrade note (chart v2.78.0 shipped with 2.31.2 and the migration to EMQX is not optional), remove the broker implementation detail from the user-facing Team Broker page, fix the Helm default wording (the broker is not enabled automatically on Kubernetes), and use consistent anchored links. --- docs/install/configuration.md | 17 ++++++++++------- docs/upgrade/README.md | 18 +++++++++--------- docs/user/expert/index.md | 2 +- docs/user/teambroker.md | 21 ++++++++------------- 4 files changed, 28 insertions(+), 30 deletions(-) diff --git a/docs/install/configuration.md b/docs/install/configuration.md index 40063e65ca..f3d0dc124e 100644 --- a/docs/install/configuration.md +++ b/docs/install/configuration.md @@ -117,17 +117,20 @@ Option | Description The platform uses an MQTT broker to provide real-time messaging between devices, Node-RED instances and the platform. The broker shipped with the platform's -Docker Compose and Kubernetes installations is [EMQX](https://www.emqx.io/). It is -deployed and configured automatically by those installers. +Docker Compose and Kubernetes installations is [EMQX](https://www.emqx.io/): the +Docker Compose installation includes it by default, and the Helm chart deploys it +when the broker is enabled (`forge.broker.enabled`), which requires the +[EMQX Operator](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) +to be installed on the cluster. -By default, the platform runs without an MQTT broker. This restricts what features -are available: +Running without a broker restricts what features are available: - Without a broker: Project Nodes, Device Actions and Remote Device Editing are unavailable. - The following features additionally require the platform broker to be EMQX, as they rely on EMQX-specific capabilities (its authentication hooks, per-team topic namespacing and management API): the [Team Broker](/docs/user/teambroker.md), - [FlowFuse Expert](/docs/user/expert/index.md) and real-time updates in the platform UI. + [FlowFuse Expert](/docs/user/expert/) and live device log and performance views + in the platform UI. [Mosquitto](https://mosquitto.org/) is supported at a legacy level for existing installations: core platform messaging works, but the EMQX-dependent features listed @@ -138,8 +141,8 @@ If a broker has been setup in the platform, the following configuration is requi Option | Description --------------|------------ -`broker.url` | The url for the platform to access the broker. For example: `mqtt://localhost:4800`. -`broker.public_url` | The url used by devices to connect to the broker, if different to `broker.url`. For example, this may require devices to use WebSockets instead: `ws://localhost:4881`. +`broker.url` | The full url to the platform broker. This is used by the platform and Node-RED instances to connect to the broker. For example: `mqtt://localhost:4800`. +`broker.public_url` | The url used by devices to connect to the broker, if different to `broker.url`. When running in a Docker or Kubernetes environment, this should be the externally addressable url of the broker, and may require devices to use WebSockets instead. For example: `ws://example.com:4881`. ## Email configuration diff --git a/docs/upgrade/README.md b/docs/upgrade/README.md index 952d2dac55..7cfa87e092 100644 --- a/docs/upgrade/README.md +++ b/docs/upgrade/README.md @@ -28,19 +28,19 @@ Details of how to upgrade can be found for each deployment model: To upgrade the version of Node-RED your Instances run (for example, moving to Node-RED 5.0), see [Upgrading the Node-RED version](./nodered-version.md). -### Upgrading to 2.32 +### Upgrading to 2.31.2 -#### Kubernetes: default MQTT broker is now EMQX +#### Kubernetes: MQTT broker is now EMQX -From Helm chart v2.78.0, the chart deploys [EMQX](https://www.emqx.io/) as the platform -MQTT broker, replacing Mosquitto. Existing installations are migrated automatically when -upgrading the chart. If the broker is enabled, the +From Helm chart v2.78.0 (FlowFuse 2.31.2), the chart deploys [EMQX](https://www.emqx.io/) +as the platform MQTT broker, replacing Mosquitto. The migration happens automatically as +part of upgrading the chart; it is not possible to stay on Mosquitto when using the Helm +chart. If the broker is enabled, the [EMQX Operator](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html) -must be installed on the cluster before upgrading. +must be installed on the cluster before upgrading, otherwise the upgrade will fail. -Mosquitto remains supported at a legacy level for existing installations, but the -broker-based platform features (Team Broker, FlowFuse Expert, real-time UI updates) -require EMQX. See [MQTT Broker configuration](../install/configuration.md#mqtt-broker-configuration). +See [MQTT Broker configuration](../install/configuration.md#mqtt-broker-configuration) +for which platform features depend on the broker. ### Upgrading to 2.6.0 diff --git a/docs/user/expert/index.md b/docs/user/expert/index.md index 6c7e97f8cd..7e188490da 100644 --- a/docs/user/expert/index.md +++ b/docs/user/expert/index.md @@ -8,7 +8,7 @@ FlowFuse Expert is the AI built into FlowFuse and the Node-RED editor. It is not **FlowFuse Expert is automatically installed and available in all hosted and remote instances running within or connected to FlowFuse**, no manual installation or configuration required. For self-hosted Enterprise customers, FlowFuse Expert can be enabled on request. [Contact us](https://flowfuse.com/contact-us/) to get it set up on your infrastructure. -> **Note:** On self-hosted installations, FlowFuse Expert requires an Enterprise license and the platform's EMQX-based MQTT broker with the Team Broker feature enabled (see [MQTT Broker configuration](/docs/install/configuration.md)). Expert communicates through a bridge between your platform broker and FlowFuse's central Expert service, which is set up as part of enabling Expert. Installations running without EMQX, for example legacy Mosquitto-based installs, cannot enable Expert. +> **Note:** On self-hosted installations, FlowFuse Expert requires an Enterprise license and the platform's EMQX-based MQTT broker with the Team Broker capability enabled in the platform configuration (see [MQTT Broker configuration](/docs/install/configuration.md#mqtt-broker-configuration)). Expert communicates through a bridge between your platform broker and FlowFuse's central Expert service, which is set up as part of enabling Expert. Installations running without EMQX, for example legacy Mosquitto-based installs, cannot enable Expert. ## Managing AI Features diff --git a/docs/user/teambroker.md b/docs/user/teambroker.md index f9eb1be92a..30358aa45e 100644 --- a/docs/user/teambroker.md +++ b/docs/user/teambroker.md @@ -10,19 +10,14 @@ This is a single shared MQTT broker, but each team has their own separate topic ## What the Team Broker is -The Team Broker is a multi-tenant MQTT broker service built into the FlowFuse platform: -one broker instance, managed by the platform, where every team gets its own fully -isolated topic space and can provision client credentials in a self-service way. It -removes the need to install and operate a separate broker to move MQTT data between -devices, Node-RED instances and other clients. - -Under the hood the Team Broker is provided by [EMQX](https://www.emqx.io/), and the -platform integrates with EMQX-specific capabilities for client authentication, per-team -topic isolation and bridging. The Team Broker cannot be backed by a different broker -(see [MQTT Broker configuration](/docs/install/configuration.md)). If your company -already operates its own MQTT broker, that broker can still be connected to FlowFuse -as an external broker to browse its topic hierarchy alongside the Team Broker, and -Node-RED instances can connect to it directly as a regular MQTT client. +The Team Broker removes the need to install and operate a separate MQTT broker to move +data between devices, Node-RED instances and other clients: the broker is provided and +managed by the platform itself. It is not replaceable with a customer-supplied broker +(self-hosted details in [MQTT Broker configuration](/docs/install/configuration.md#mqtt-broker-configuration)). + +If your company already operates its own MQTT broker, that broker can still be connected +to FlowFuse as an external broker to browse its topic hierarchy alongside the Team +Broker, and Node-RED instances can connect to it directly as a regular MQTT client. ## Foreword FlowFuse offers zero config MQTT integration with the Team Broker via the [FlowFuse MQTT Nodes](/docs/user/mqtt-nodes/) that greatly simplifies the whole process by removing the need for manual configuration. From 8253eed5b8a1b65e6b7b10edf33add280a7efb8e Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Mon, 6 Jul 2026 23:33:35 +0200 Subject: [PATCH 3/4] docs: keep broker options table at its original location Restore the original MQTT Broker configuration section and its option descriptions in place, and remove the newer duplicated section instead, so the existing configuration reference stays where it was. --- docs/install/configuration.md | 61 +++++++++++++++++------------------ 1 file changed, 30 insertions(+), 31 deletions(-) diff --git a/docs/install/configuration.md b/docs/install/configuration.md index f3d0dc124e..56dd912816 100644 --- a/docs/install/configuration.md +++ b/docs/install/configuration.md @@ -113,37 +113,6 @@ Option | Description `driver.options.customHostname.ingressClass` | The name of the Ingress Class that should be used for the custom hostname. Default: not set `driver.options.customHostname.certManagerIssuer` | The name of the CertManager ClusterIssuer to provision HTTPS certificates for custom hostnames. Default: not set -## MQTT Broker configuration - -The platform uses an MQTT broker to provide real-time messaging between devices, -Node-RED instances and the platform. The broker shipped with the platform's -Docker Compose and Kubernetes installations is [EMQX](https://www.emqx.io/): the -Docker Compose installation includes it by default, and the Helm chart deploys it -when the broker is enabled (`forge.broker.enabled`), which requires the -[EMQX Operator](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) -to be installed on the cluster. - -Running without a broker restricts what features are available: - -- Without a broker: Project Nodes, Device Actions and Remote Device Editing are unavailable. -- The following features additionally require the platform broker to be EMQX, as they - rely on EMQX-specific capabilities (its authentication hooks, per-team topic - namespacing and management API): the [Team Broker](/docs/user/teambroker.md), - [FlowFuse Expert](/docs/user/expert/) and live device log and performance views - in the platform UI. - -[Mosquitto](https://mosquitto.org/) is supported at a legacy level for existing -installations: core platform messaging works, but the EMQX-dependent features listed -above are unavailable. Replacing the platform broker with a different customer-supplied -broker is not supported. - -If a broker has been setup in the platform, the following configuration is required: - -Option | Description ---------------|------------ -`broker.url` | The full url to the platform broker. This is used by the platform and Node-RED instances to connect to the broker. For example: `mqtt://localhost:4800`. -`broker.public_url` | The url used by devices to connect to the broker, if different to `broker.url`. When running in a Docker or Kubernetes environment, this should be the externally addressable url of the broker, and may require devices to use WebSockets instead. For example: `ws://example.com:4881`. - ## Email configuration By default, email is disabled. This restricts some features in the platform around @@ -235,6 +204,36 @@ Option | Description `support.frontend.hubspot.trackingcode` | The numerical identifier within your [HubSpot Tracking Code](https://knowledge.hubspot.com/conversations/chat-widget-is-not-appearing-on-your-pages). Default: `null` +## MQTT Broker configuration + +The platform uses an MQTT broker to provide real-time messaging between devices, +Node-RED instances and the platform. The broker shipped with the platform's +Docker Compose and Kubernetes installations is [EMQX](https://www.emqx.io/): the +Docker Compose installation includes it by default, and the Helm chart deploys it +when the broker is enabled (`forge.broker.enabled`), which requires the +[EMQX Operator](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) +to be installed on the cluster. + +This is currently an *optional* component - the platform will work without the +broker, but some features will not be available: + +- Without a broker: Project Nodes, Device Actions and Remote Device Editing are unavailable. +- The following features additionally require the platform broker to be EMQX, as they + rely on EMQX-specific capabilities (its authentication hooks, per-team topic + namespacing and management API): the [Team Broker](/docs/user/teambroker.md), + [FlowFuse Expert](/docs/user/expert/) and live device log and performance views + in the platform UI. + +[Mosquitto](https://mosquitto.org/) is supported at a legacy level for existing +installations that manage their own broker: core platform messaging works, but the +EMQX-dependent features listed above are unavailable. Replacing the platform broker +with a different customer-supplied broker is not supported. + +Option | Description +---------------|-------------- +`broker.url` | The full url to the platform broker. This is used by the platform and Node-RED instances to connect to the broker. For example: `mqtt://localhost:1883`. +`broker.public_url` | If set, this is the url provided to Devices to connect to the broker with. When running in a Docker or K8S environment, this url should be the externally addressable url the broker is provided on. This could be via WebSockets, for example: `ws://example.com:1884` + ## AI Configuration Option | Description From 5f9c8a6980805640b44bc415c6609c02160fc70f Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Mon, 6 Jul 2026 23:36:14 +0200 Subject: [PATCH 4/4] docs: trim implementation detail from broker docs Keep the user-facing Team Broker page to what users need, shorten the Expert self-hosted note to the requirement itself, and drop internal EMQX capability details from the configuration reference. --- docs/install/configuration.md | 8 +++----- docs/install/kubernetes/README.md | 2 +- docs/user/expert/index.md | 2 +- docs/user/teambroker.md | 13 ++----------- 4 files changed, 7 insertions(+), 18 deletions(-) diff --git a/docs/install/configuration.md b/docs/install/configuration.md index 56dd912816..d5a1420238 100644 --- a/docs/install/configuration.md +++ b/docs/install/configuration.md @@ -218,11 +218,9 @@ This is currently an *optional* component - the platform will work without the broker, but some features will not be available: - Without a broker: Project Nodes, Device Actions and Remote Device Editing are unavailable. -- The following features additionally require the platform broker to be EMQX, as they - rely on EMQX-specific capabilities (its authentication hooks, per-team topic - namespacing and management API): the [Team Broker](/docs/user/teambroker.md), - [FlowFuse Expert](/docs/user/expert/) and live device log and performance views - in the platform UI. +- The following features additionally require the platform broker to be EMQX: + the [Team Broker](/docs/user/teambroker.md), [FlowFuse Expert](/docs/user/expert/) + and live device log and performance views in the platform UI. [Mosquitto](https://mosquitto.org/) is supported at a legacy level for existing installations that manage their own broker: core platform messaging works, but the diff --git a/docs/install/kubernetes/README.md b/docs/install/kubernetes/README.md index 3f84b65293..51c4425841 100644 --- a/docs/install/kubernetes/README.md +++ b/docs/install/kubernetes/README.md @@ -92,7 +92,7 @@ Before you begin, ensure you have the following: - [Digital Ocean](digital-ocean.md) - MicroK8s 5. **Ingress Controller:** [The Traefik](https://doc.traefik.io/traefik/) installed on the cluster. -6. **EMQX Operator:** This is required to install the platform's MQTT broker when the broker is enabled. The broker provides device and instance communication, the Team Broker, and FlowFuse Expert. Instructions for installing the operator can be found [here](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) +6. **EMQX Operator:** This is required to install the platform's MQTT broker when the broker is enabled. Instructions for installing the operator can be found [here](https://docs.emqx.com/en/emqx-operator/latest/getting-started/getting-started.html#install-emqx-operator) For a production-ready environment, we also recommend: * **Database:** Prepare dedicated database on a external database server (see [FAQ](#how-to-use-external-database-server%3F) for more details) diff --git a/docs/user/expert/index.md b/docs/user/expert/index.md index 7e188490da..6ea0c59045 100644 --- a/docs/user/expert/index.md +++ b/docs/user/expert/index.md @@ -8,7 +8,7 @@ FlowFuse Expert is the AI built into FlowFuse and the Node-RED editor. It is not **FlowFuse Expert is automatically installed and available in all hosted and remote instances running within or connected to FlowFuse**, no manual installation or configuration required. For self-hosted Enterprise customers, FlowFuse Expert can be enabled on request. [Contact us](https://flowfuse.com/contact-us/) to get it set up on your infrastructure. -> **Note:** On self-hosted installations, FlowFuse Expert requires an Enterprise license and the platform's EMQX-based MQTT broker with the Team Broker capability enabled in the platform configuration (see [MQTT Broker configuration](/docs/install/configuration.md#mqtt-broker-configuration)). Expert communicates through a bridge between your platform broker and FlowFuse's central Expert service, which is set up as part of enabling Expert. Installations running without EMQX, for example legacy Mosquitto-based installs, cannot enable Expert. +> **Note:** On self-hosted installations, FlowFuse Expert requires an Enterprise license and the platform's EMQX-based MQTT broker with the Team Broker capability enabled in the platform configuration (see [MQTT Broker configuration](/docs/install/configuration.md#mqtt-broker-configuration)); installations running without EMQX cannot enable Expert. ## Managing AI Features diff --git a/docs/user/teambroker.md b/docs/user/teambroker.md index 30358aa45e..1978ee149d 100644 --- a/docs/user/teambroker.md +++ b/docs/user/teambroker.md @@ -6,18 +6,9 @@ navTitle: Team Broker When FlowFuse is deployed with an Enterprise license from v2.11.0 onwards comes with the option to enable a MQTT broker for each Team. -This is a single shared MQTT broker, but each team has their own separate topic space and the ability to provision credentials for clients. +This is a single shared MQTT broker, but each team has their own separate topic space and the ability to provision credentials for clients. It removes the need to install and manage a broker of your own. -## What the Team Broker is - -The Team Broker removes the need to install and operate a separate MQTT broker to move -data between devices, Node-RED instances and other clients: the broker is provided and -managed by the platform itself. It is not replaceable with a customer-supplied broker -(self-hosted details in [MQTT Broker configuration](/docs/install/configuration.md#mqtt-broker-configuration)). - -If your company already operates its own MQTT broker, that broker can still be connected -to FlowFuse as an external broker to browse its topic hierarchy alongside the Team -Broker, and Node-RED instances can connect to it directly as a regular MQTT client. +If your company already operates its own MQTT broker, that broker can also be connected to FlowFuse as an external broker to browse its topic hierarchy alongside the Team Broker. ## Foreword FlowFuse offers zero config MQTT integration with the Team Broker via the [FlowFuse MQTT Nodes](/docs/user/mqtt-nodes/) that greatly simplifies the whole process by removing the need for manual configuration.