Brilliant Motion Detection Not Triggering Automations? How to Fix
- Motion automations were disabled
- Quiet hours suppress motion actions
- Sensor sensitivity set too low
Problem Description
If Brilliant motion detection stops triggering automations, lights and scenes may no longer respond to occupancy events. This usually comes from disabled motion behavior, schedule constraints, stale automation logic, or sensor sensitivity settings.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. If Brilliant motion detection stops triggering automations, lights and scenes may no longer respond to occupancy events. This usually comes from disabled motion behavior, schedule constraints, stale automation logic, or sensor sensitivity s.. The pattern people actually report is Room lights no longer auto-turn on, Motion events missing from activity logs, and Automation works only at certain hours
The most common real-world triggers are Motion automations were disabled, Quiet hours suppress motion actions, and Sensor sensitivity set too low. The fix is most reliable when the sequence is followed exactly: Check room motion settings, then Review schedules and quiet hours, then Increase sensor sensitivity. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- Room lights no longer auto-turn on
- Motion events missing from activity logs
- Automation works only at certain hours
- Manual control still works normally
- Multiple rooms fail after app edits
- Sensor appears active but no actions run
Recognize these? Here's what usually causes it.
Common Causes
- Motion automations were disabled
- Quiet hours suppress motion actions
- Sensor sensitivity set too low
- Automation condition conflicts exist
- Recent firmware changed sensor defaults
- Panel room assignment became incorrect
Most fixes happen in the first 3 steps.
Avoid stacking multiple overlapping motion automations for one room. Conflicts can suppress triggers and create inconsistent behavior.
Tools & Requirements
Step-by-Step Solution
Check room motion settings
Open room configuration on the panel and verify motion-triggered behavior is enabled for that room. In many cases, users disable motion during testing and forget to restore it. Confirm target lights or scenes are linked to the expected room sensor.
Review schedules and quiet hours
Inspect time constraints that can block automations during evenings, sleep mode, or custom quiet windows. Motion sensor health may be fine while schedule rules suppress action. Temporarily widen allowed hours and retest detection behavior immediately.
Increase sensor sensitivity
Raise motion sensitivity one step and test from normal approach distance. Very low sensitivity can miss slow movement or side-angle motion, especially in larger rooms. Keep pets and known false trigger sources in mind when tuning thresholds.
Simplify and retest automation logic
Disable extra conditions like occupancy dependencies or multi-device prerequisites, then test a basic motion to light rule. Complex logic chains can fail silently. Once baseline works, reintroduce advanced conditions one at a time to find the conflict point.
Save fresh configuration and monitor
After adjustments, re-save room and automation settings from panel and app. Trigger several motion passes over five minutes. Confirm consistent action firing and activity log entries before concluding the issue is resolved across that room.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
Document your working motion sensitivity and schedule settings so future edits can be rolled back quickly.
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- Motion automations were disabled
- Quiet hours suppress motion actions
- Sensor sensitivity set too low
- Automation condition conflicts exist
- Recent firmware changed sensor defaults
Before you go — try one of these (they fix most cases).
Need More Help? Brilliant Smart Home Support
Note: The contact information below connects you directly to Brilliant Smart Home's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.