Philips is still selling the second-generation Hue Bridge alongside the newer v3, and the naming pattern is unhelpful. Both are square, both work with the Hue app, and both talk to your lights. The differences that matter live under the label. If you are staring at the two boxes trying to decide which to buy, or you own a v2 and want to know whether the v3 is worth the upgrade, this guide covers what is actually different in day-to-day use, when the upgrade earns its price, and when it does not.
What is actually different between v2 and v3
The v2 (model 3241312018A, launched 2015) uses a Freescale Kinetis processor with 16 MB of RAM and supports Zigbee 3.0 after a 2018 firmware update. Its practical device ceiling is 50 lights and 12 accessories, and it maxes out its scene table at about 200 scenes across all rooms. HomeKit is supported. The Ethernet port is 100 Mbps.
The v3 (model BSB003, launched 2023) moves to a newer Zigbee radio with better range under interference, doubles the RAM to 32 MB, raises the device ceiling to the same 50/12 on paper but stays stable much closer to that ceiling in practice, and adds Bluetooth for the app’s fast-setup flow. HomeKit is supported. Ethernet is still 100 Mbps.
The one hardware difference nobody talks about: the v3 has a small metal heatspreader glued to the SoC. Owners of dozens of v2 units running near the ceiling report warm-to-the-touch behavior after 18 months of continuous operation, and the v3 stays noticeably cooler under the same load.
When the upgrade is worth it
The v3 is meaningfully better in three situations. If you run more than 35 devices on a single bridge and see occasional dropped commands, the v3’s larger memory ceiling gives back headroom the v2 has already spent. If your bridge is in a location with Wi-Fi interference on the 2.4 GHz band (near a router or a microwave), the v3’s radio holds a cleaner signal at range. If you plan to add Zigbee sensors that report frequently (motion sensors set to five-second intervals, temperature sensors reporting every minute), the v3’s higher packet-processing headroom prevents the “sensor updates arrive but scenes lag” pattern that shows up on a saturated v2.
Outside those three cases, a healthy v2 with fewer than 30 devices will run indefinitely without you noticing the difference. Do not spend the $60 to $80 on an upgrade you will not feel.
The migration itself
Philips ships a migration tool in the Hue app that handles the mechanical part. It does not move everything cleanly. Plan for this:
- Take screenshots of every room’s light list, every scene per room (with the color values), and every routine, including trigger times and target rooms. The migration preserves scene names but occasionally resets color values to defaults.
- Have both bridges powered on and connected to the same network. The new bridge must be a fresh install with no lights paired.
- In the Hue app: Settings, Hue Bridges, tap your old bridge, scroll to “Migrate Hue Bridge,” and follow the prompt to press the button on the new bridge.
- Wait about ten minutes. Do not unplug either bridge during this window.
- Once the migration completes, verify every room has its lights and every scene has the correct color. Rebuild any scenes that reset.
- Re-pair HomeKit: the new bridge needs a new HomeKit code and every automation that references a Hue accessory needs the new accessory ID.
- Unlink the old bridge from Alexa and Google Home, then link the new one.
Comparison at a glance
| Feature | Hue Bridge v2 (2015) | Hue Bridge v3 (2023) |
|---|---|---|
| Model number | 3241312018A | BSB003 |
| RAM | 16 MB | 32 MB |
| Zigbee | 3.0 (after 2018 firmware) | 3.0 with newer radio |
| Practical device ceiling | ~30 for stable operation | ~45 for stable operation |
| HomeKit | Yes | Yes |
| Bluetooth | No | Yes (setup only) |
| Thermal headroom | Runs warm at capacity | Runs cooler at capacity |
| Retail price (July 2026) | Around $60 | Around $80 |
What breaks after the migration and how to fix it
Three things usually break within the first 24 hours. First, third-party integrations that used the bridge’s HTTPS API will need their tokens re-issued. If you use Home Assistant or Hubitat with the Hue integration, the new bridge presents a new certificate and the old token is invalid. Re-authorize inside each integration’s config.
Second, Nest Hub and Echo Show displays that showed the Hue rooms as cards may temporarily show them as offline. Rebooting the display resolves it within a few minutes as the Google Home or Alexa cloud re-syncs the new bridge address.
Third, if you had schedules that fired at a specific time before dawn, verify that the new bridge picked up your correct time zone. The migration tool does not always copy the location, and the default is UTC. Set it explicitly under Settings, Location.
Frequently asked questions
Can I run the old v2 as a second bridge on the same network? Yes. Each bridge is a separate account in the Hue app and can operate independently. Some owners use the second bridge for outdoor lights so a firmware issue on one bridge does not affect the other.
Does the v3 support Matter? The v3 exposes bridged Hue accessories as Matter devices to compatible controllers as of the 2024 firmware. The v2 does not.
Will my Zigbee sensors from the v2 still work after migration? Yes, but they need to be re-paired individually. The migration tool moves lights only, not third-party Zigbee accessories.
Is there a v3 Pro or a v4 coming? Philips has not announced one as of mid-2026, and the v3 was refreshed with a firmware feature update in early 2026 that suggests it is the current long-term platform.
Will my third-party Zigbee devices from other brands work through either bridge? Yes, if they are Zigbee 3.0 compliant and support the Zigbee Home Automation profile. Innr bulbs, IKEA Trådfri accessories, and Sengled bulbs pair to either bridge, though Philips periodically restricts non-Hue devices via firmware. If Hue Essentials is your target app, third-party integration is more permissive there.
Does the v3 draw more power than the v2? Marginally. The v3 idles at about 2.5 W versus the v2’s 2.1 W. Over a year of continuous operation, that is roughly 3.5 kWh, or under a dollar of electricity at typical residential rates. Not a factor in the buying decision.
Can I keep my v2 as a Zigbee mesh extender? No. Hue Bridges do not federate their Zigbee networks. A v2 running independently is just a second Hue Bridge with its own network; it does not extend the v3’s mesh.
