# SONOFF Bridge Max (Bridge-M)

SONOFF Bridge Max is a practical migration hub when its compatibility matrix already covers the Zigbee, Bluetooth, eWeLink, or Home Assistant devices that need basic control in a Matter app. It is less convincing as a speculative universal bridge because it still needs another Matter controller and does not carry every source feature across.

Canonical page: https://matterhome.io/devices/sonoff-bridge-max
Markdown page: https://matterhome.io/devices/sonoff-bridge-max.md
Author: Matterhome Editorial Team
Author profile: https://matterhome.io/authors/matterhome-editorial-team
Editorial lead: JC Martinez
Editor profile: https://matterhome.io/authors/jc-martinez

## Device Facts

- Brand: SONOFF
- Model: Bridge Max (Bridge-M)
- Product type: Matter Bridge and Zigbee Gateway
- Category: Matter controllers
- Connection: Matter bridge
- Matter status: SONOFF sells Bridge-M with an active Matter 1.4 bridge path for supported Zigbee, BTHome, eWeLink-Remote, eWeLink-account, and Home Assistant devices; it needs a separate Matter controller on the same LAN and is not a Thread border router.
- Launch date: 2026-06-23
- Thread border router required: No
- Brand hub required: No
- Typical price range: $59.90 / about EUR60 / GBP54.62
- Markets: North America, Europe, United Kingdom
- Review status: Compatibility guide
- Product image: https://assets.matterhome.io/content/devices/sonoff-bridge-max/product.bc795bf1032a3cef5a25/source.webp
- Product image alt text: White SONOFF Bridge Max hub shown at an angle with its raised center panel and model mark
- Product image source: https://cdn.shopify.com/s/files/1/0742/9963/8001/files/BridgeMax-main.avif?v=1782184319

## Ecosystem Support

- Apple Home: Supported
- Google Home: Supported
- Alexa: Supported
- SmartThings: Supported
- Home Assistant: Supported

## Best For

- SONOFF Zigbee homes replacing a ZBBridge Pro while keeping existing devices, scenes, and security settings
- Mixed device collections whose exact models and required functions appear in SONOFF's Bridge Max matrix
- Buyers who want an Ethernet-connected local bridge setup with optional eWeLink management

## Skip If

- The planned child devices or required controls are absent from SONOFF's compatibility matrix
- The home needs a Matter controller, Thread border router, or brand-neutral automation controller rather than a bridge
- Direct control from the local web console is part of the requirement
- The device collection already works well through a focused Aqara, Hue, or Tapo bridge

## Setup Notes

- Connect Bridge-M to 5 V, 1 A USB-C power and use Ethernet for the clearest documented local setup path.
- Open bridgem.local or the bridge's IP address to configure the local web console, or add it through eWeLink when Wi-Fi, scene sharing, or app-managed security features are needed.
- Check every planned child device and required function in SONOFF's Bridge Max compatibility matrix before moving it from an existing hub.
- Keep a compatible Matter controller on the same LAN, then enable Bridge-M pairing and add the bridge from the receiving ecosystem.

## Known Limitations

- The CSA record certifies Ethernet as the Matter transport, while SONOFF separately documents operation over 2.4 and 5 GHz Wi-Fi through eWeLink.
- SONOFF's local web path can sync supported devices but not eWeLink scenes; scene sharing is an eWeLink app feature.
- Bridge Replacement migrates only from ZBBridge Pro model ZBBridge-P, not from ZBBridge-U or iHost.
- Matterhome has not tested child-device migration, feature exposure, local web behavior, MQTT, Zigbee range, or ecosystem parity.

## Pros

- Bridges supported Zigbee, BTHome, eWeLink-Remote, eWeLink-account, and Home Assistant devices into Matter platforms
- Provides a local web setup path over Ethernet for supported device sources without requiring the eWeLink app
- Connects by Ethernet or 2.4 and 5 GHz Wi-Fi
- Supports up to 128 Zigbee devices and includes a 90 dB security speaker

## Cons

- Still needs a separate Matter controller and does not provide Thread border-router service
- Child-device and feature exposure depends on SONOFF's live compatibility matrix
- The local web console configures bridging but cannot directly control devices
- Scene sharing and Wi-Fi setup require the eWeLink path

## Sources

- https://sonoff.tech/products/sonoff-bridge-max-smart-home-bridge-bridge-m
- https://sonoff.tech/en-us/products/sonoff-bridge-max-smart-home-bridge-bridge-m
- https://sonoff.tech/en-de/products/sonoff-bridge-max-smart-home-bridge-bridge-m
- https://sonoff.tech/en-uk/products/sonoff-bridge-max-smart-home-bridge-bridge-m
- https://sonoff.tech/products/sonoff-bridge-max-smart-home-bridge-bridge-m.json
- https://help.sonoff.tech/docs/BridgeM
- https://bridge.sonoff.tech/device-function-reference-table/
- https://csa-iot.org/csa_product/bridge-max/
- https://cdn.shopify.com/s/files/1/0742/9963/8001/files/BridgeMax-main.avif?v=1782184319

Bridge Max is for the awkward middle of a smart home: the devices still work, but their Zigbee, Bluetooth, eWeLink, or Home Assistant path keeps them outside the app the household actually uses. SONOFF's `Bridge-M` can expose supported devices to Apple Home, Google Home, Alexa, SmartThings, or Home Assistant through Matter, with Ethernet and a local web console available for setup.

That does not make it a universal Matter hub. Bridge-M needs a separate Matter controller on the same network, it is not a Thread border router, and the receiving app gets only the device types and functions SONOFF exposes. Matterhome has not tested the bridge, migration flow, or child-device behavior. The recommendation depends on the exact compatibility matrix, not the list of radios on the box.

## Choose the source devices before the bridge

Bridge-M can take inputs from five distinct places. It can pair Zigbee devices, discover BTHome and eWeLink-Remote accessories, import supported devices from an eWeLink account, and receive entities from Home Assistant. SONOFF rates it for up to 128 Zigbee devices and 128 other bridged devices under its lab conditions.

Those categories are only the start of the decision. A motion sensor may expose occupancy but not every vendor setting. A switch may arrive as a simple on-off endpoint without its power history or special button actions. SONOFF maintains a device and function matrix for Bridge Max, so check both the exact model and the control needed in the destination app before buying the hub or moving a room of accessories.

Existing ZBBridge Pro owners have the cleanest upgrade case. SONOFF's Bridge Replacement flow can move Zigbee devices, scenes, and security settings from model `ZBBridge-P` without pairing everything again. The same migration is not documented for Zigbee Bridge Ultra (`ZBBridge-U`) or iHost, so owners of those hubs should assume a manual rebuild unless SONOFF adds another supported route.

## Ethernet keeps the local path clearest

Bridge Max is an 82 x 82 x 28 mm indoor hub powered by 5 V, 1 A over USB-C. Its RJ45 port supports 10/100 Mbps Ethernet. SONOFF also documents 2.4 and 5 GHz Wi-Fi 6, but Wi-Fi setup goes through eWeLink. The CSA certificate for hardware 1.2 and firmware 1.7.1 lists Ethernet as the Matter transport, which makes a wired connection the least ambiguous starting point.

With Ethernet connected, open `bridgem.local` or the assigned IP address and set a local password. The web console can add supported Zigbee, BTHome, eWeLink-Remote, and Home Assistant sources, then sync them to a Matter platform without an app or cloud account. Importing devices from an eWeLink account still requires signing in.

The word console can be misleading. SONOFF says the local web interface configures the bridge but does not directly control its devices. Daily control belongs in the receiving Matter app or eWeLink. The web path also cannot sync eWeLink scenes, so a buyer who wants those scenes, Wi-Fi placement, security logs, or the fuller alarm controls should expect to keep the app.

## Matter receives endpoints, not the source app

Before commissioning, put Bridge-M and the target Matter controller on the same LAN. Enable pairing from the web console or eWeLink, then add the bridge in Apple Home, Google Home, Alexa, SmartThings, or Home Assistant. Start with one representative device from each category and verify its states, commands, and automation triggers before sharing the rest.

Home Assistant creates a choice that deserves planning. Bridge-M can publish its Zigbee children to Home Assistant over MQTT. It can also take Home Assistant entities and expose them onward to other Matter fabrics. Decide which system owns each device and avoid feeding the same entity back through a circular bridge path. A duplicated light or sensor is harder to diagnose than an omitted one.

The built-in 90 dB speaker, local security modes, three months of security logs, Zigbee channel controls, and Turbo mode remain Bridge-M features. Matter can carry supported child endpoints into another ecosystem. It does not reproduce SONOFF's management interface or guarantee equal feature depth in every controller.

## Buy it when the existing list already fits

SONOFF published the current store listing on June 23, 2026. The same SKU, `6979033600461`, is available through its United States, German, and United Kingdom storefronts at roughly $60, EUR60, or GBP55. That is a reasonable price when Bridge-M replaces a ZBBridge Pro, adds Ethernet, or prevents a known collection of supported devices from being replaced.

A focused bridge is often the better answer when one brand dominates. [Aqara Hub M200](/devices/aqara-hub-m200) adds a Matter controller and Thread border router for an Aqara-centered home. [Philips Hue Bridge and Bridge Pro](/devices/philips-hue-bridge-and-bridge-pro) keep Hue lighting features with Hue. [Tapo H110](/devices/tapo-h110-smart-ir-iot-hub) is the narrower Tapo sensor and infrared route.

Buy Bridge Max when the source list, destination controls, and network placement are already known. Skip it when the purchase is really an attempt to make an undocumented Zigbee device portable, replace a Matter controller, or add Thread coverage. Those are different jobs, and another bridge will not solve them by collecting more protocol names.