Direct answer
For the Hue dimmer switch v2, power, network, storage, hub/controller and provider service should be stable. First, record current version, progress and exact indicator.
What this covers
- Hue dimmer switch v2 (RWL022)
- Hue dimmer switch v2; a battery-powered Zigbee control with no network connection of its own — it talks only to the Bridge.
- 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
The device sleeps before the update completes
What separates it Updates fail repeatedly on a battery device and succeed when it is charging. Sleep is a power-saving behaviour that does not know an update is in progress.
How to confirm Charge to full and keep it powered throughout. Several platforms will not begin an update below a charge threshold at all.
- 3
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.
- 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 battery level at the start of each attempt, and whether the device was on power throughout.
- The signal strength the device reports for itself at its current position.
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.
Put the device on power and leave it there
ReversibleA battery device may sleep partway through, and several platforms will not begin an update below a charge threshold at all. Charging throughout removes the whole class of failure rather than testing it.
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.
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
- RWL022. Hue dimmer switch v2; a battery-powered Zigbee control with no network connection of its own — it talks only to the Bridge.
- Battery
- One CR2032 coin cell, included, rated for a minimum 2-year life and 50,000 button clicks — a switch that has become slow or unresponsive after roughly two years is a battery question before anything else.
- Works without a Bridge too
- Unlike the Bridge itself, this switch can connect directly over Bluetooth to up to 10 lights with no Hue Bridge at all. With a Bridge, it controls up to 50 lights and up to two rooms, zones, or the whole system — so "does this need a Bridge" depends on how many lights and how much control is wanted.
- Radio
- Zigbee (IEEE 802.15.4) to a Bridge-based system, with Bluetooth as the alternative bridge-less path described above. It has no network connection of its own beyond that.
- Mounting
- Wall-mountable with a plate, or used freestanding/portable with a magnetic back and adhesive backing — it's designed to be moved around as a handheld remote as well as fixed to a wall.
- Controls
- Two configurable buttons plus dedicated brightness up/down controls; pressing the main Hue button cycles through four preset light recipes (Read, Relax, Energize, Concentrate) when not customized in the app.
- Power path
- Internal or removable battery. Every capability that costs current — night vision, higher stream quality, longer recordings, frequent events — is paid for in runtime, so a change in behaviour after a settings change is usually a power consequence rather than a fault. Cold weather reduces usable capacity sharply.
- Symptom boundary
- This record covers Philips Hue Hue dimmer switch 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 RWL022 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
Do I need a Hue Bridge for this dimmer switch?+
No — it can connect directly over Bluetooth to up to 10 lights without any Bridge. A Bridge is only needed to control more lights (up to 50), assign it to specific rooms/zones, or customize the scenes it triggers.
The switch feels slow or takes two presses to respond.+
Check the CR2032 battery first — it's rated for a minimum of 2 years and 50,000 clicks, and a switch nearing that age commonly shows exactly this symptom before it fails outright.
Can I use this as a handheld remote instead of mounting it?+
Yes — it has a magnetic back and adhesive backing designed for both wall mounting and freestanding/portable use as a handheld remote.
What do the four unlabeled scenes do by default?+
Without customization in the app, pressing the Hue button cycles through four preset light recipes: Read, Relax, Energize and Concentrate. Pairing it to a Bridge is what lets those be replaced with your own scenes.
How is this different from the Hue Motion Sensor?+
Both are battery-powered Zigbee accessories with no network connection of their own, but the dimmer switch has no motion or light detection — it only responds to button presses. The Motion Sensor detects movement and ambient light instead.
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.
It will not start the update at all.+
Check the charge level and whether it is on power. Several platforms refuse to begin below a threshold, and a battery device that sleeps partway through will fail repeatedly until it is charging throughout.
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.
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 RWL022. Hue dimmer switch v2; a battery-powered Zigbee control with no network connection of its own — it talks only to the Bridge.
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.