Direct answer
For the Hue Bridge v2, power, network, storage, hub/controller and provider service should be stable. First, record current version, progress and exact indicator.
What this covers
- Hue Bridge v2 (BSB002)
- Hue Bridge v2; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
- The specific fault this record addresses: firmware update is stuck or failed
What it does not cover
- ×The same symptom on a different Philips Hue product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The progress indicator is stalled, not the update
What separates it The bar sits at a percentage for a long time while the device is otherwise normal. Verification and writing produce no visible progress and can take far longer than the download did.
How to confirm Leave it alone for substantially longer than seems reasonable before acting. Almost every genuinely bricked device on this symptom was interrupted by someone who did not wait.
- 2
Signal is adequate for control but not for a sustained transfer
What separates it The device works normally, and updates fail at varying percentages. Control traffic is tiny and intermittent; an update is a large sustained transfer and needs a link that control traffic never tests.
How to confirm Move the device close to the router or hub for the update. Failures at varying percentages point at the link; failures at the same percentage point at the package or storage.
- 3
The hub is the thing that needs updating first
What separates it Accessory updates fail while the hub reports an available update of its own. Version dependencies run in one direction and accessories cannot outrun their controller.
How to confirm Update the controller first, let it settle, then retry the accessory.
- 4
The provider is staging the rollout
What separates it The device reports itself up to date on a version that is not the newest, and nothing forces it forward. Staged rollouts are normal and deliberate.
How to confirm Compare the installed version against the provider's published current version and whether it is fully released. Waiting is the correct action.
- 5
The device updated successfully and something else broke
What separates it The update completed and a feature stopped. That is a regression rather than a failed update, and rolling back is usually not available.
How to confirm Compare the behaviour against the release notes and report it. Repeated re-updating will not change a shipped regression.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- The version installed now and the version being offered, both written down before anything is attempted.
- The exact percentage or stage at which it stops, across several attempts. The same point every time and a varying point mean different things.
- How long it has actually been sitting, measured rather than estimated — verification and writing produce no visible progress.
- The signal strength the device reports for itself at its current position.
- The controller's own version and whether it has an update pending.
Wait considerably longer than feels reasonable
ReversibleVerification and writing show no progress and can take far longer than the download. This is the one symptom on which impatience causes the damage — nearly every unrecoverable device on this fault was interrupted by someone who decided it had hung.
Record the current version and the offered version
ReversibleWithout both numbers you cannot tell a failed update from a staged rollout from a completed update that changed something. Write them down before the first attempt, not after the third.
Move it close to the router or hub for the attempt
ReversibleAn update is a large sustained transfer, and a link perfectly adequate for control traffic can be inadequate for it. Failures at varying percentages are this; failures at the same percentage are not.
Update the controller before the accessory
ReversibleVersion dependencies run one way. An accessory cannot move ahead of the hub that manages it, and retrying the accessory while the hub is behind will fail indefinitely with no useful message.
Retry through the official app only
ReversibleNever an unofficial package, a downgrade, or a file from anywhere but the manufacturer. A mismatched or modified image is the one thing that turns a recoverable failure into an unrecoverable one.
Confirm the version and every core function afterwards
ReversibleAn update that reports success and leaves a feature broken is a regression, not a completed job. Check the version number and exercise the things you actually use before considering it done.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- BSB002. Hue Bridge v2; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
- Capacity
- Philips states the Bridge supports up to 50 lights and 12 accessories. Those are two separate limits, and the accessory limit is the lower and the one people reach first — a switch or sensor that will not pair on a large system is worth checking against the 12-accessory figure before anything else.
- Network
- Connects to the router by Ethernet cable, not Wi-Fi. That is the single most useful fact about this device for troubleshooting: Wi-Fi problems cannot affect the Bridge's own connection, and a Wi-Fi fix will never help it. What can affect it is the cable, the router port and the router's client list.
- Radio to accessories
- Zigbee to every light and accessory. Accessories have no independent path to anything — they reach the Bridge over Zigbee and nothing else — so a Bridge fault presents as every light and switch failing at once, and no accessory-level check means anything until the Bridge is confirmed working.
- Power
- A supplied mains adapter, 120 V in the US, with standby power consumption stated as 0.1 W. There is no battery, so the Bridge stops with the power and returns with it, and everything commissioned to it stops too.
- Mesh behaviour
- Mains-powered Zigbee devices — the lights — repeat the mesh. Battery accessories such as dimmer switches and motion sensors do not. That is why adding another battery accessory never improves range, and adding a mains-powered light often does.
- Philips Hue's own specification
- Philips publishes the Bridge's specification at philips-hue.com/en-us/p/hue-bridge/046677458478, and its support section for the system at philips-hue.com/en-us/support/product/philips-hue-system/100005.
- Power path
- Mains adapter into a standard outlet. Switched outlets and outlets on a circuit that trips are the two failure modes that present as device faults. Use the supplied adapter — third-party adapters that supply the right voltage at the wrong current are a common cause of intermittent restarts.
- Radio
- Zigbee mesh through a bridge. The accessory has no independent internet path, so a bridge fault presents as every accessory failing at once. Mains-powered Zigbee devices repeat the mesh; battery ones do not, which is why adding a battery accessory never improves range.
- Radio
- Wired Ethernet available. A wired path removes signal strength, band steering and Wi-Fi credentials from the investigation entirely, and is worth using during diagnosis even if the device will end up wireless.
- Symptom boundary
- This record covers Philips Hue Hue Bridge v2 when it firmware update is stuck or failed. A different symptom on the same hardware, or this symptom on a different Philips Hue product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The device has been unresponsive since an interrupted update. Do not keep power-cycling it — that can compound a partial write. This is a support case.
- !The update completed and a documented feature no longer works. Rollback is generally unavailable and repeated re-updating will not change a shipped regression.
- !An update is failing on a device that is part of a life-safety or security function and has left it in a degraded state.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Philips Hue Support publishes this as "Release notes". Philips Hue's own published release notes, which name what each firmware version changed — the way to tell a failed update from a shipped behaviour change. What that article does not carry is the model boundary — it is written for a product line, and BSB002 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
Does the Hue Bridge connect over Wi-Fi?+
No — it connects to your router by Ethernet cable. This is the most useful thing to know when troubleshooting it: a Wi-Fi problem cannot affect the Bridge's own connection, and no amount of Wi-Fi work will help. Check the cable, the router port and the router's client list instead.
How many devices can the Hue Bridge handle?+
Philips states up to 50 lights and 12 accessories. Those are separate limits, and the 12-accessory limit is the lower one — so a switch or sensor that refuses to pair on a large system is worth counting against that figure before assuming the accessory is faulty.
All my Hue lights stopped working at once.+
Check the Bridge first. Every light and accessory reaches it over Zigbee and has no independent path to anything else, so a Bridge fault takes the whole system out simultaneously. It also has no battery, so a power cut does the same thing.
Will adding another dimmer switch improve my Hue range?+
No. Mains-powered Zigbee devices — the lights — repeat the mesh; battery accessories such as switches and sensors do not. Adding a battery accessory adds a leaf to the network, not a relay. Adding a mains-powered light in the gap is what extends range.
How much power does the Bridge use?+
Philips states standby power consumption of 0.1 W, from a supplied mains adapter (120 V in the US). Its own consumption is negligible; what matters is that it has no battery, so anything depending on it stops during a power cut.
The update has been at the same percentage for a long time. Should I restart it?+
Almost certainly not. Verification and writing produce no visible progress and routinely take much longer than the download. This is the symptom where intervening causes the damage — nearly every unrecoverable device on this fault was interrupted by someone who concluded it had hung.
How long is too long?+
Longer than you think, and the honest answer depends on the device — but the asymmetry is what matters. Waiting an extra hour costs an hour. Interrupting a write costs the device. Given that trade, wait.
The update keeps failing at a different percentage each time.+
A varying failure point is the network. An update is a large sustained transfer, and a link that is fine for control traffic can be inadequate for it. Move the device close to the router for the attempt. A failure at the same percentage every time would point at the package or at storage instead.
My device says it is up to date but there is a newer version.+
Staged rollouts are normal and deliberate — the provider releases in waves. The device is behaving correctly, waiting is the right action, and there is generally no supported way to force it forward.
The accessory update fails and the hub has an update pending.+
Update the hub first and let it settle. Version dependencies run in one direction, an accessory cannot move ahead of its controller, and retrying the accessory in that state will fail indefinitely with no message that explains why.
Can I install firmware from somewhere else?+
No. A mismatched or modified image is the single most reliable way to turn a recoverable failure into an unrecoverable one, and it voids any support path you had. Official app only.
The update finished and now a feature is missing.+
That is a regression rather than a failed update, and repeating the update will not undo it. Compare against the release notes and report it — rollback is generally not available on this class of hardware.
The device has been dead since the update.+
Stop power-cycling it. Repeated interruptions can compound a partial write, and each attempt reduces what a support team can recover. Record the version it was on and the stage it stopped at, and open a case.
Should I update at all if everything works?+
Yes, for security fixes in particular — but do it when you can leave it alone, on power, near the router, and not when you are about to need the device. The update itself is low risk; being interrupted is the risk.
Does this answer apply to every Philips Hue model?+
No. It is scoped to BSB002. Hue Bridge v2; the hub every Zigbee accessory reports through, and the only component in a Hue system with its own network connection.
What should I record before troubleshooting firmware or update?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing firmware, update. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Never interrupt critical-device firmware or use unofficial files.
Answer for the exact device and software version shown above.