Symptoms
Raw motion events arrive, but lights only switch on after sunset.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Raw motion events arrive, but lights only switch on after sunset.
- Comparison to run: Compare raw events, lux threshold and automation time conditions in daylight.
- Pass condition: Harmless test action runs on intended daytime motion with no false nighttime triggers.
Why It Happens
A raw event is not the same thing as an automation action. Timing, state mapping, hub subscriptions and the physical device must be checked separately.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Brightness condition excludes daytime — investigate this first only if the local state or controlled comparison supports it.
- Automation bound to old sensor entity — a second layer that may survive a simple restart and requires a targeted check.
- Motion cooldown prevents repeat trigger — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Do not change security alarm actions while debugging a lighting rule. A smart-home event can be detected correctly by a sensor but then delayed or misread by the hub, bridge, cloud integration or automation rule. Separate raw sensor state from the action triggered by that state. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare raw events, lux threshold and automation time conditions in daylight. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare raw events, lux threshold and automation time conditions in daylight. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Check rule conditions rather than moving the sensor first. | This can expose or rule out brightness condition excludes daytime without changing several settings together. |
| Inspect the deeper layer | Inspect raw lux values and entity identifiers during the missed event. | Use the evidence to separate automation bound to old sensor entity from motion cooldown prevents repeat trigger; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether automation bound to old sensor entity is consistent with the evidence. If not, investigate motion cooldown prevents repeat trigger rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Raw motion events arrive, but lights only switch on after sunset. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare raw events, lux threshold and automation time conditions in daylight. Do not erase logs or reset the device yet. Check rule conditions rather than moving the sensor first. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Set a test automation with harmless notification instead of lights. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. Harmless test action runs on intended daytime motion with no false nighttime triggers. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider brightness condition excludes daytime, automation bound to old sensor entity and motion cooldown prevents repeat trigger separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare raw events, lux threshold and automation time conditions in daylight. Inspect raw lux values and entity identifiers during the missed event. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Review automation trace logs for skipped conditions and timezones. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. Harmless test action runs on intended daytime motion with no false nighttime triggers. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating brightness condition excludes daytime as certain before running the comparison: Compare raw events, lux threshold and automation time conditions in daylight.
- Trying several changes at once, such as modifying automation bound to old sensor entity and motion cooldown prevents repeat trigger simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Do not change security alarm actions while debugging a lighting rule.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Harmless test action runs on intended daytime motion with no false nighttime triggers.
- Repeat the original failing action under equivalent conditions: Raw motion events arrive, but lights only switch on after sunset.
- Run the control again: Compare raw events, lux threshold and automation time conditions in daylight.
- Check the positive pass condition: Harmless test action runs on intended daytime motion with no false nighttime triggers.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Inspect raw lux values and entity identifiers during the missed event. Review automation trace logs for skipped conditions and timezones.
Give vendor support sanitized event times, hub model, raw-state transitions and firmware details; treat safety and access-control devices as safety equipment, not debugging toys.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare raw events, lux threshold and automation time conditions in daylight.
- Preserve the corrected behavior: Harmless test action runs on intended daytime motion with no false nighttime triggers.
- Preserve hub backups and automation screenshots; test critical automations after hub, battery or time-zone changes.
- Review configuration or hardware changes that could reintroduce brightness condition excludes daytime.
Frequently Asked Questions
Does this symptom prove brightness condition excludes daytime?
No. Start with the controlled comparison: Compare raw events, lux threshold and automation time conditions in daylight. Only treat brightness condition excludes daytime as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Inspect raw lux values and entity identifiers during the missed event. That helps determine whether automation bound to old sensor entity or motion cooldown prevents repeat trigger fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Harmless test action runs on intended daytime motion with no false nighttime triggers. Keep a record of the working state for future troubleshooting.