feat: Default Expert central broker when Team Broker is enabled - #991
Merged
Conversation
When the Team Broker is enabled the Expert chat uses the MQTT bridge, which requires expert.centralBroker.server. Default it to expert-broker.flowfuse.com:8883 in that case so it does not have to be set by hand, matching the docker-compose template. An explicit forge.expert.broker.address/port still overrides the default, and setting an address without the Team Broker enabled still fails with the existing guidance.
andypalmi
changed the title
hardillb
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
When the Team Broker is enabled, the Expert chat uses the MQTT bridge, which needs
expert.centralBroker.server. Today the chart only emits that key ifforge.expert.broker.addressis set, so operators have to configure it by hand even though the value is effectively alwaysexpert-broker.flowfuse.com:8883.This defaults
centralBroker.servertoexpert-broker.flowfuse.com:8883whenever Expert and the Team Broker are both enabled, matching the docker-compose template. Team Broker enabled is exactly the case where the frontend selects MQTT chat and needs the bridge, and the chart already auto-wires theteamBroker.apicredentials in that case, so this completes the picture.Keeping it overridable rather than hardcoded is ease of development and future proofing: the address is
expert-broker.flowfuse.comfor every hosted deployment today, but could differ later if we allow the central broker to live in a user's own deployment.Cases
centralBroker.server: expert-broker.flowfuse.com:8883(the new default)forge.expert.broker.address/portset -> still respected as an overrideforge.broker.teamBroker.enabled=trueRelated
Follow-up from a self-hosted support case where the central broker had to be configured manually. Companion PRs: FlowFuse/docker-compose#360, FlowFuse/website#5485.