Behind the Light Automation: Understanding Triggers, Conditions, and Actions in Home Assistant

Previous article: Building a Smart Light Automation with C4002 mmWave Radar and ESPHome in Home Assistant

1. Introduction

In the previous two articles, I shared how I built a smart desk lighting system.But building automations is only part of the journey. To design flexible, reliable smart home systems, it’s important to understand the underlying automation model.

This article focuses on event-driven architecture,  a layered system model and the three fundamental elements of Home Assistant automations. By mastering this, you’ll be able to create smarter, more scalable automations for any smart home project.

2. Architecture of the Light Automation System

A presence-based smart lighting system is essentially a distributed intelligent system, composed of multiple layers working together: Reality Layer, Perception Layer, Communication Layer, Decision Layer, and Execution Layer.

The system works by converting physical changes into digital states, processing them through automation logic, and finally executing actions in the physical environment.

Layered Architecture:
- Reality Layer: Represents the physical world. For example, when a person enters the room, the environment changes first.
- Perception Layer: The presence is detected by the C4002 mmWave radar sensor. This physical signal is converted into a “presence” status and uploaded to Home Assistant via the ESP32 perception node.
- Communication Layer: Handles the transmission of data through the Wi-Fi network (or MQTT).
- Decision Layer: Listens for state changes, triggers automation rules, and generates control commands. These commands are sent to the execution layer.
- Execution Layer: Composed of the ESP32-C6 and relay, it receives commands to control the lighting.

The entire process forms a complete behavioral loop: physical changes lead to data changes, data changes trigger logical evaluation, and logical decisions drive physical actions.

With this layered architecture, each layer is responsible only for its specific role—the perception layer collects data, the communication layer transmits data, the decision layer performs logical evaluation, and the execution layer carries out actions. This clear separation of responsibilities results in a system that is both well-structured and highly scalable, reflecting how real smart home systems operate.

3. Implementation Logic of the Auto Lighting System

Let’s analyze the system workflow starting from real-world behavior.

As illustrated in the diagram, the system operates as a distributed, event-driven architecture. The perception layer converts physical changes into digital states, the communication layer transmits data via Wi-Fi and MQTT, the decision layer evaluates automation logic within Home Assistant, and the execution layer controls the relay to turn the light on or off according to the generated commands.

The entire process forms a complete closed loop: physical changes → data changes → logical evaluation → action execution → physical environment changes. This is the fundamental operating model of a smart home system

4. Principles of Automation Rules

At the core of this system are automation rules, which are based on the event-driven model:
- Event-Driven Model: The system does not constantly poll all device states. Instead, it reacts when an event occurs.
- Example: When a sensor state changes (e.g., “no presence → presence”), this generates an event, triggering the automation process.

Each automation rule typically consists of three key elements: Trigger, Condition, and Action. The trigger starts the automation, the condition determines whether it should proceed, and the action performs the final task. In simple terms, the logic can be summarized as: when an event occurs (Trigger), and the specified conditions are met (Condition), the system executes the corresponding operation (Action).

Trigger: A trigger defines the event that starts the automation. It is the starting point of any automation; without a trigger, the rule will not run. For example, a presence sensor state changing from “no one” to “someone,” or from “someone” to “no one.”

Condition: A condition further filters the execution logic after the trigger has fired. For example, you might set the automation to run only at night or only if the light is currently off.
 

Action: The action is the final operation performed by the automation rule. When the trigger is activated and all conditions are met, the system executes the corresponding action, such as turning a relay on or off.

5. AI Self-Learning Expansion

If you want to deepen your understanding of automation rules or further expand your presence-based smart lighting system, the following prompts can be used with large AI models for self-learning and exploration.

This series consists of three articles on Home Assistant Smart Lighting Automation System. Each article focuses on a different aspect to give you a complete understanding of Lighting Automation System:
- Project Showcase And Experience: From PIR to mmWave: My Smart Lighting Automation in Home Assistant
- Hands-On Tutorial: Building a Smart Light Automation with C4002 mmWave Radar and ESPHome in Home Assistant

- Home Assistant Automation Explained: Behind the Light Automation: Understanding Triggers, Conditions, and Actions in Home Assistant