Configure Background RX Mode on Bond Bridge Pro

Amit Shem-Tov

Updated July 17, 2026 17:47

Overview

Background RX Mode controls which compatible RF signals a Bond Bridge Pro continuously listens for. It is required for products that send unsolicited commands or status messages to the Bridge, including:

Breeze Pro
Bond Sidekick
Mate Pro
Supported third-party RF keypads
Vertilux bidirectional motors

A Bond Bridge Pro can use only one Background RX Mode at a time. Selecting one mode disables background reception for products that require a different mode.

Background RX Mode is not available in the Bond Home app. It must be configured through the Bridge Pro’s local web interface.

Available Background RX Modes

Bond Sidekick and Breeze Pro — BondSync

Use this mode for:

Bond Sidekick keypads
Mate Pro
Breeze Pro
Other supported BondSync devices

Note: BondSync products cannot use background reception while the Bridge is configured for Vertilux bidirectional motors or a third-party RF keypad mode.

Third-Party RF Keypads

Use this mode for supported third-party RF keypads, including compatible Lutron Pico configurations.

Selecting this mode may prevent Breeze Pro, Sidekick, Mate Pro, and Vertilux bidirectional reception from operating on the same Bridge.

Vertilux Bidirectional Motors

Use this mode for Vertilux motors that require bidirectional communication.

Vertilux Relion technical note

Vertilux Relion motors map to the RMS158 device profile. Adding an RMS158 device automatically places the Bond Bridge Pro into BGRX mode 2, which is the Vertilux bidirectional receiver mode.

While the Bridge remains in this mode, it cannot listen for BondSync transmissions from Breeze Pro, Bond Sidekick, or Mate Pro.

Deleting the Vertilux device does not necessarily return the Bridge to BondSync mode. The Background RX Mode may need to be changed manually through the Bridge’s local web interface.

Important: Use separate Bridge Pros when Vertilux bidirectional motors and BondSync products are required at the same installation.

Before You Begin

Confirm that:

The Bond Bridge Pro is powered on and connected to the local network.
Your phone, tablet, or computer is connected to the same network as the Bridge.
You can access the router or network-management interface to find the Bridge Pro’s local IP address.
You know which products at the installation require Background RX reception.

Changing this setting may interrupt existing Sidekick, Breeze Pro, keypad, Mate Pro, or Vertilux functionality.

Access the Bridge Pro Local Interface

Find the local IP address assigned to the Bond Bridge Pro.
The address may be available through the router, network controller, or another network-management interface.
Open a web browser.
Enter the Bridge Pro’s IP address followed by:
/bridge
Example:
http://10.0.32.33/bridge
The Bridge Pro configuration page should open.

Your browser may display a Not secure warning because the page is hosted locally by the Bridge rather than through a public HTTPS website.

Change Background RX Mode

Locate Background RX Mode on the Bridge Pro configuration page.
Select the mode required for the installation:
- Bond Sidekick and Breeze Pro (BondSync)
- Third-Party RF Keypads
- Vertilux bidirectional motors
Select Save.
Allow the Bridge a moment to apply the setting.
Return to the Bond Home app and test the affected product.

Depending on the product and its previous configuration, you may need to repeat its pairing or learning procedure after changing the mode.

Example: Breeze Pro Will Not Connect

When attempting to add Breeze Pro, the Bridge may successfully open its learning window but continue to show:

No learned transmissions
No newly discovered device
Repeated unsuccessful learning attempts

If the Bridge is configured for Vertilux bidirectional motors, this behavior is expected. Breeze Pro requires Bond Sidekick and Breeze Pro (BondSync) mode.

To resolve the issue:

Change Background RX Mode to Bond Sidekick and Breeze Pro (BondSync).
Select Save.
Repeat the Breeze Pro pairing procedure.

If Vertilux bidirectional motors are also required, use a separate Bridge Pro.

Compatibility Examples

Installation requirement	Required Background RX Mode
Breeze Pro	Bond Sidekick and Breeze Pro (BondSync)
Bond Sidekick	Bond Sidekick and Breeze Pro (BondSync)
Mate Pro	Bond Sidekick and Breeze Pro (BondSync)
Vertilux bidirectional motors	Vertilux bidirectional motors
Supported Lutron Pico or third-party keypad	Third-Party RF Keypads
Breeze Pro and Vertilux at the same installation	Two separate Bridge Pros
Sidekick and Vertilux at the same installation	Two separate Bridge Pros when both require background reception

Troubleshooting

The Local Page Does Not Open

Confirm that:

The IP address is correct.
The device accessing the page is on the same network as the Bridge.
Client isolation, guest-network isolation, or VLAN rules are not blocking local communication.
The Bridge is currently online.

Try entering the full address, including http:// and /bridge.

Example:

http://10.0.32.33/bridge

The Correct Mode Is Selected, but the Product Still Will Not Connect

Try the following:

Select Save again.
Reboot the Bridge.
Keep the product close to the Bridge during pairing.
Confirm that the product has sufficient power.
Remove any incomplete device entry and repeat setup.
Verify that another device type has not changed the Background RX Mode.

Existing Products Stopped Responding After the Mode Was Changed

The affected products likely depend on the previously selected receiver mode.

Restore the previous Background RX Mode or move the conflicting product to another Bridge Pro.

Additional Settings on the Local Page

The local Bridge page may also include settings for:

Extra Delay
Bond Bridge Collision Avoidance Protocol (BBCAP)
Bridge reboot

These settings are separate from Background RX Mode and should not be changed unless directed by Bond Support or Engineering.

Escalation Information

When escalating a Background RX issue, include:

Bridge Pro serial number
Firmware version
Selected Background RX Mode
Device types configured on the Bridge
Product being paired
Screenshot of the local Bridge page
Relevant Dashboard or Palantir logs
Whether the issue continues after selecting the correct mode and rebooting the Bridge