Direct answer
For the SimpliSafe Base Station (Gen 3), power, network, storage, hub/controller and provider service should be stable. First, record current version, progress and exact indicator.
What this covers
- SimpliSafe Base Station (Gen 3) (the serial number is on the label on the underside of the Base Station)
- SimpliSafe Gen 3 system component; sensors reach the Base Station over SimpliSafe's own sub-GHz radio rather than Wi-Fi, so a router problem and a sensor problem are separate investigations. Monitoring plan, cellular backup and camera generation vary.
- The specific fault this record addresses: firmware update is stuck or failed
What it does not cover
- ×The same symptom on a different SimpliSafe 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
- the serial number is on the label on the underside of the Base Station. SimpliSafe Gen 3 system component; sensors reach the Base Station over SimpliSafe's own sub-GHz radio rather than Wi-Fi, so a router problem and a sensor problem are separate investigations. Monitoring plan, cellular backup and camera generation vary.
- What it is
- The hub every SimpliSafe sensor reports to. When a sensor or camera detects something it signals the Base Station, which sounds the siren and raises the notification. Nothing about an individual sensor is worth investigating until the Base Station is confirmed working, because a Base Station fault presents as every device failing at once.
- Power
- Plugs into a standard AC outlet using the included AC adaptor with a 6-foot cord, and carries 4 NiMH rechargeable AA 1.2V batteries as backup. SimpliSafe states the backup keeps the system covered for 24 hours through a power outage or a cut landline.
- Siren
- A 100 dB siren built into the Base Station itself.
- Size
- 4 x 8.25 x 4 inches — large enough that placement is a real decision. It has to be within radio range of every sensor, which is why a basement or a cupboard is usually the wrong place for it.
- System capacity
- SimpliSafe states the Gen 3 system supports up to 100 products. Thick-walled areas such as garages and basements are named by SimpliSafe as the places that can present a range challenge.
- Generation
- This is the Gen 3 system. A system bought in 2017 or earlier is the Original SimpliSafe, which is a different platform with different articles — checking which one you have before following any procedure prevents most wasted effort.
- 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.
- 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.
- Wi-Fi
- Joins on 2.4 GHz. A phone on 5 GHz cannot hand credentials to it reliably during setup, and a router that steers clients between bands under one network name will produce intermittent joins that look like a hardware fault.
- Radio
- A manufacturer-specific sub-GHz radio to the base station rather than Wi-Fi. It travels further through structure than Wi-Fi does and is unaffected by router changes — which means a Wi-Fi problem and a sensor problem are genuinely separate investigations here.
- Backup path
- Carries a cellular backup path for alarm signalling. Backup carries signalling, not bandwidth — so the system can report itself online and monitored while everything that needs broadband fails, and can stay in that state for weeks unnoticed.
- Symptom boundary
- This record covers SimpliSafe Base Station (Gen 3) when it firmware update is stuck or failed. A different symptom on the same hardware, or this symptom on a different SimpliSafe 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. SimpliSafe Support publishes this as "How to Check the Firmware Version of SimpliSafe Devices". SimpliSafe's own article for reading the installed firmware version across system devices. What that article does not carry is the model boundary — it is written for a product line, and the serial number is on the label on the underside of the Base Station 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
How long does the Base Station keep working in a power cut?+
SimpliSafe states the backup battery covers 24 hours, using 4 NiMH rechargeable AA 1.2V cells. That covers a power outage or a cut landline. It does not extend indefinitely, so an outage longer than a day leaves the system unpowered.
How loud is the Base Station siren?+
SimpliSafe lists 100 dB for the Base Station's own siren. The separate Extra Siren reaches up to 105 dB, which is the reason to add one — that and putting sound somewhere the Base Station is not.
Where should the Base Station go?+
Somewhere central and open. It has to stay in radio range of every sensor, and SimpliSafe specifically names garages and basements — thick walls — as the areas that can present a challenge. A cupboard or a basement corner is the most common placement mistake.
How many devices can one Base Station handle?+
SimpliSafe states the Gen 3 system supports up to 100 products. Very few homes approach that, so a device that will not pair is almost never a capacity problem.
Do I have the Gen 3 system or the Original?+
A system bought in 2017 or earlier is the Original SimpliSafe, which is a different platform with different procedures. Confirming which one you have before following anything is worth the thirty seconds, because Original instructions applied to a Gen 3 system fail in confusing ways.
Everything went offline at once. What does that mean?+
Look at the Base Station first. Every sensor reports through it, so a Base Station fault takes the whole system out simultaneously — which reads like a catastrophic account failure and is usually one unplugged hub or a tripped outlet.
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 SimpliSafe model?+
No. It is scoped to the serial number is on the label on the underside of the Base Station. SimpliSafe Gen 3 system component; sensors reach the Base Station over SimpliSafe's own sub-GHz radio rather than Wi-Fi, so a router problem and a sensor problem are separate investigations. Monitoring plan, cellular backup and camera generation vary.
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.