Direct answer
For the SimpliSafe Motion Sensor (Gen 2), time zone, placement, calibration, stale cloud state and sensor hardware should be separated. First, compare local device value with app history and a reference.
What this covers
- SimpliSafe Motion Sensor (Gen 2) (Gen 2 — the serial number is inside the battery compartment)
- 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: shows the wrong time, state or sensor reading
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 app is showing a cached value, not a current one
What separates it The reading is plausible but stale, and it refreshes when the app is reopened or pulled down. The timestamp beside the value is the giveaway and is routinely ignored.
How to confirm Read the timestamp on the value itself. A correct sensor and a stale display is the most common version of this complaint.
- 2
The home's time zone rather than the device's clock
What separates it Everything is offset by a whole number of hours, including event history and schedules. The home has its own time zone setting that defaults to wherever it was created.
How to confirm Check the home or hub's time zone rather than the phone's. A whole-hour offset is essentially always this.
- 3
The device has lost its clock and not resynchronised
What separates it Timestamps are wrong by an arbitrary amount rather than a whole number of hours, often after a power cut. A device that boots before the network is available can start with no valid time.
How to confirm Restart it once the network is confirmed up and check whether timestamps correct themselves.
- 4
A battery sensor is reporting on a duty cycle
What separates it The value is correct but old, and updates at intervals rather than continuously. Reporting frequently is expensive, so battery sensors do not.
How to confirm Compare several consecutive readings and their timestamps. Regular intervals are a designed behaviour rather than a fault.
- 5
The sensor itself has drifted or failed
What separates it The reading is implausible, changes erratically, or does not respond to a real change in conditions at all.
How to confirm Reach this only after the others are excluded. A sensor that fails to move when conditions genuinely change is different from one that reads a real microclimate.
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 timestamp shown beside the value, not just the value. A correct sensor with a stale display is the most common form of this complaint.
- The size and direction of the error: a whole number of hours, a small stable offset, or an erratic difference. Each points somewhere different.
- The home or hub's time zone setting, read there rather than on the phone.
- Whether the problem began after a power cut, a network outage or a move.
- Several consecutive readings with their timestamps, which shows whether reporting is on an interval.
Read the timestamp before the value
ReversibleA stale display of a correct reading is the most common version of this complaint, and it is settled in one look. Pull to refresh and see whether the value changes before investigating the sensor at all.
Classify the size of the error
ReversibleA whole number of hours is a time zone. A small stable offset is placement or self-heating. An erratic or implausible difference is the sensor. These three share no steps, and the classification costs nothing.
Check the home's time zone, not the phone's
ReversibleThe home has its own time zone and location, defaulting to wherever it was created. A whole-hour offset across readings, history and schedules is essentially always this, and the phone's own clock being correct proves nothing about it.
Restart once, after confirming the network is up
ReversibleA device that boots before the network is available can start with no valid time and never resynchronise. Timestamps wrong by an arbitrary amount after a power cut are this, and one restart in the right order fixes it.
Take several consecutive readings before judging
ReversibleA battery sensor reports on an interval because reporting is expensive. Regular gaps between correct values are designed behaviour; erratic values between correct ones are not.
Confirm the reading responds to a real change
ReversibleChange the conditions deliberately and watch. A sensor that does not move when conditions genuinely change has failed; one that moves correctly but reads a consistent offset has not.
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
- Gen 2 — the serial number is inside the battery compartment. 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.
- Range and coverage
- SimpliSafe states the Gen 2 sensor has a range of 35 ft and a 90° field of view, intended to cover an entire room from one location. Beyond 35 ft is outside specification and no sensitivity setting extends it.
- Mounting height
- SimpliSafe specifies mounting in a corner, 6 ft from the floor. It states a shelf is acceptable only if it is still 6 ft from the floor, sitting flat and with a clear view of the room. Height error is the most consequential installation mistake on this sensor.
- Pet discrimination
- SimpliSafe states the Gen 2 sensor is engineered to tell the difference between people and pets up to 60 lbs, using a more advanced PIR sensor and detection algorithm than the Gen 1. An animal heavier than 60 lbs is outside what that discrimination is specified for.
- Sensitivity
- Two modes — Standard and Pet — adjustable in the SimpliSafe app. This is a mode switch rather than a continuous slider, so the tuning options here are narrower and more predictable than on a camera.
- Generation
- Gen 1 and Gen 2 are genuinely different hardware: SimpliSafe attributes the 35 ft range, the 90° field of view, the 60 lb pet discrimination and the app-adjustable sensitivity to the Gen 2 specifically. Procedures and expectations do not transfer between them.
- 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.
- 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.
- Symptom boundary
- This record covers SimpliSafe Motion Sensor (Gen 2) when it shows the wrong time, state or sensor reading. 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 reading does not respond to a deliberate, real change in conditions, which is a failed sensor rather than a configuration problem.
- !The device is being relied on as the sole medical, fire, freeze or security guarantee. No consumer sensor is specified for that, whatever it currently reads.
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 "Testing the Motion Sensor Gen 2". SimpliSafe's own Motion Sensor test procedure. What that article does not carry is the model boundary — it is written for a product line, and Gen 2 — the serial number is inside the battery compartment 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 far does the Motion Sensor Gen 2 reach?+
SimpliSafe specifies 35 ft with a 90° field of view, designed to cover a whole room from one corner. A subject beyond 35 ft is outside specification, and that is the answer to most 'it misses people at the far end' reports — sensitivity does not extend range.
How high should I mount it?+
SimpliSafe specifies a corner, 6 ft from the floor. A shelf is acceptable only if it is still 6 ft up, flat, and with a clear view of the room. Height is the single most consequential thing about installing this sensor, because the detection zones fan outward from it.
Will my dog set it off?+
SimpliSafe states the Gen 2 distinguishes people from pets up to 60 lbs, using a more advanced PIR sensor and algorithm than the Gen 1. Above 60 lbs that discrimination is outside what it is specified for — and mounting height still matters, because it determines whether the animal is below the lowest zone.
How do I change the sensitivity?+
In the SimpliSafe app, between Standard Mode and Pet Mode. It is a two-position mode rather than a continuous slider, so there is no partial adjustment to hunt for — which also means placement and height carry more of the load here than on a camera.
How is the Gen 2 different from the Gen 1?+
SimpliSafe attributes to the Gen 2 specifically: a 35 ft range, a 90° field of view, people-versus-pet discrimination up to 60 lbs, and app-adjustable sensitivity. They are genuinely different hardware, so a figure or a procedure from one does not transfer to the other.
The reading looks wrong but the device seems fine.+
Read the timestamp beside the value before anything else. A stale display of a perfectly correct reading is the most common version of this complaint, and pulling to refresh settles it in one look.
Everything is out by exactly an hour.+
That is the home's time zone, not the device's clock. The home has its own time zone and location setting that defaults to wherever it was created, and the phone's clock being correct tells you nothing about it. Whole-hour offsets are essentially always this.
Timestamps went wrong after a power cut.+
A device that boots before the network is available can start with no valid time and never resynchronise. The distinguishing feature is that the error is an arbitrary amount rather than a whole number of hours. One restart, after the network is confirmed up, normally fixes it.
The value only updates every so often.+
That is a duty cycle, not a fault. Reporting continuously is expensive, so battery sensors report at intervals. Several consecutive readings with their timestamps will show a regular gap — which is designed behaviour rather than something to fix.
How do I tell a bad sensor from bad placement?+
Change the conditions deliberately. A badly placed sensor reads a real microclimate and moves correctly when conditions change. A failed sensor does not move at all, or moves erratically. That single test separates them where comparing numbers does not.
Can I rely on this for a freezer or a medication store?+
No. No consumer sensor is specified as a sole guarantee for medical, fire, freeze or security purposes — the reporting is duty-cycled, the alerting is best-effort, and nothing tells you when it has stopped. Anything that matters needs a layer designed to fail loudly.
Does this answer apply to every SimpliSafe model?+
No. It is scoped to Gen 2 — the serial number is inside the battery compartment. 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 wrong reading or time?+
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 wrong reading, time. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not use consumer sensors as the sole medical, fire, freeze or security guarantee.
Answer for the exact device and software version shown above.