Skip to content

Automations

Building Useful Arrival, Evening and Good Night Routines

Design three practical Aqara routines that coordinate lighting, curtains and security without making the home difficult to override.

6 min readBy Aqara Singapore
Resident using a warm bedroom with Aqara smart home devices

The best smart home routines remove small repeated tasks without making the home feel unpredictable. Arrival, Evening and Good Night are useful places to start because each has a clear purpose and can coordinate several rooms.

Build each routine in stages. Test the actions, add conditions and keep a physical way to change the result.

On this page
  1. Arrival should make entry easier
  2. Evening should change the lighting quality
  3. Good Night should confirm the home state
  4. Use modes to prevent routines from colliding
  5. Plan manual override and recovery
  6. Make every routine easy to override
  7. Build and test in this order

Arrival should make entry easier

An arrival routine can turn on the entrance and passage lights when the main door opens after dark. If the platform and household setup support reliable presence logic, it can distinguish a genuine arrival from someone opening the door while others remain at home.

Broad presence guesses are a weak foundation for security-critical actions: unlocking and disarming deserve deliberate controls and clear confirmation.

Separate detection from authentication. A door contact can prove that the door opened; phone presence may suggest who arrived; neither necessarily proves that an authorised person intends to unlock the home. Use the lock’s supported credentials or another explicit action for access control, then let the arrival routine handle low-risk comfort actions.

A practical sequence is: door opens after dark, entrance light turns on immediately, passage light turns on at a lower level, and an occupied-home mode prevents the routine from switching the whole home into an empty-to-occupied state when somebody was already inside.

Shop Aqara smart locks

Three routines can share devices without doing the same jobDefine the purpose and entry condition of each routine so that one does not unexpectedly undo another.
Door opens after dark
Arrival
Safe route lighting and useful entry state
Chosen at the end of day
Evening
Warmer light, lower output and privacy
Deliberate final command
Good Night
Shared areas off, checks and night route
Aqara video doorbell installed beside a home entrance
Entrance devices can provide useful arrival events and status, while unlocking and disarming should remain deliberate and clearly confirmed.

Evening should change the lighting quality

An Evening scene can close selected curtains, reduce brightness and shift adjustable lighting to a warmer colour temperature. This is more useful than simply turning on every light at sunset.

Keep work areas or the kitchen independent where brighter task lighting may still be needed. One scene can establish the base setting without forcing every circuit into the same state.

Use the scene to set explicit values rather than toggling. For example: close the living-room curtains, set the cove and joinery lights to 40 per cent, set tunable-white fittings to a warm setting, leave the kitchen task circuit unchanged and turn off decorative lighting in unoccupied rooms.

The trigger can remain manual because ‘evening’ is a household decision, not an astronomical event. Sunset may offer a suggestion or start a limited privacy action, while a scene button gives residents control when dinner, work and daylight do not follow the usual schedule.

Shop Aqara smart lighting

Warm concealed lighting illuminating a Singapore kitchen in the evening
An Evening scene should change lighting quality and privacy, not simply switch on every available circuit.

Good Night should confirm the home state

A Good Night scene can switch off shared-area lights, close curtains, reduce air-conditioning in selected rooms and arm supported security monitoring. It can also leave a low route light available for late-night movement.

Use a clear button or voice phrase and give the routine enough feedback that the household knows it ran. An essential action hidden in a schedule can fire while someone is still using the room.

Divide the routine into actions and checks. Actions set lights, curtains and supported cooling controls. Checks report doors or windows that remain open and devices that did not reach the requested state. A warning is safer than automatically locking or closing something when the system cannot understand the physical situation.

The night route should be a separate low-output behaviour driven by suitable occupancy sensing. It can light the bedroom-to-bathroom path without cancelling the Good Night state or turning on general ceiling lighting.

Shop smart curtains and blinds

Singapore bedroom with full-height motorised curtains
Good Night can close the bedroom curtains, settle shared lighting and report exceptions while keeping a clear manual override available.

Use modes to prevent routines from colliding

A small number of household modes—Home, Away, Evening and Sleep, for example—can give automations shared context. When Sleep is active, a passage sensor can select a night level instead of its daytime level. When Away is active, an opened door can create an alert rather than an ordinary arrival response.

A mode must have a reliable way to change and recover. A deliberate scene button is transparent. Geofencing can be useful but needs rules for several residents, flat phone batteries and permission changes. Do not let an uncertain location event silently arm security while someone remains at home.

Plan manual override and recovery

Manual control should take effect immediately. The automation also needs to know when it may resume. It might wait until the room becomes vacant, until the next scheduled period, or until a scene explicitly restores the normal state. Without a recovery rule, either the system fights the user or the automation remains disabled indefinitely.

Toggles make poor recovery logic: a toggle cannot tell whether the light was changed by the user, another automation or a power restoration. If Evening should restore the room, command the intended brightness and colour temperature.

An automation needs an exit pathNormal, manual override and recovery behaviour should all be planned before a routine is considered complete.
Normal
Routine runs
Expected conditions are met
Exception
Person overrides
Physical control wins immediately
Recovery
Next known state
Timer, scene or next event resumes logic

Make every routine easy to override

Record the expected result for normal use, manual override, repeated execution, one unavailable device and an internet outage. Then run those tests. The purpose is not to eliminate every exceptional situation; it is to ensure that the home remains understandable when one occurs.

  • Keep wall switches functional.
  • Use clear scene names and room names.
  • Add delays only where they solve a real timing problem.
  • Test guests, late arrivals and unusual schedules.
  • Review routines after the household has lived with them for a few weeks.

Build and test in this order

  • Create each device action as an explicit scene and verify the final states.
  • Put the scene on a physical control and use it for several days.
  • Add time, light, occupancy or household-mode conditions only where they remove a repeated decision.
  • Test one missing device and confirm the rest of the routine remains useful.
  • Document the override and the condition that allows automation to resume.

Build and test every routine in stages

Create the outcome

  • Set explicit device states rather than toggles
  • Put the routine on a clear physical or app control
  • Use it manually for several days

Add automation carefully

  • Add only conditions that resolve observed ambiguity
  • Test repeated triggers, unavailable devices and internet loss
  • Document the override and when automatic behaviour resumes

Security-critical actions should remain deliberate and confirmed; use routines mainly to coordinate comfort and status reporting.

Official references

Product and standards information was checked against these primary sources. The article above is original Aqara Singapore editorial content.

Start with one dependable routine

Turn a useful scene into a tested automation.

Compare practical scene and automation examples, then build the smallest version that solves a real repeated task.