By Jeremy Koski · September 17, 2026
Lighting is the most common starting point for home automation because the results are immediate and the hardware is inexpensive. Home Assistant gives you local control over your lights without depending on a cloud service, so your automations keep working even if your internet connection drops. This guide walks through the decisions and configurations needed to build a lighting automation system in Home Assistant.
You need a Home Assistant installation, at least one controllable light, and a way for Home Assistant to communicate with that light. If you have not installed Home Assistant yet, our guide on setting up Home Assistant on a Raspberry Pi in 2026 covers the hardware and installation steps. Once Home Assistant is running, the next step is adding your lights as entities. Most integrations auto-discover devices on your network, but Zigbee and Z-Wave devices require a USB coordinator stick plugged into your Home Assistant server. You can explore available smart home integrations on our services page to see what platforms we support.
The protocol your lights use determines how they communicate with Home Assistant. Zigbee is the most popular choice for lighting because bulbs, switches, and sensors from different manufacturers all work on the same mesh network. You need a Zigbee coordinator, such as a SkyConnect or Sonoff dongle, to bridge Zigbee devices to Home Assistant. Z-Wave operates on a different frequency and is less common for bulbs but widely used for in-wall switches. Z-Wave also requires a USB coordinator. WiFi lights connect directly to your router, which means no coordinator is needed, but each bulb adds load to your WiFi network and depends on a cloud service unless it supports Matter or a local API. For most homes, Zigbee offers the best balance of device variety, local control, and mesh reliability.
This is the first real decision. Smart bulbs let you control color and brightness on a per-bulb basis, but they require the physical wall switch to stay on at all times. If someone flips the switch off, the bulb loses power and cannot respond to automations. Smart switches replace the wall switch and control whatever bulbs are in the fixture, even standard non-smart bulbs. This means the switch always has power and the lights can be controlled by both the physical switch and the automation system. Smart switches are the better choice for whole-home automation because they solve the power-loss problem and work with any bulb. Smart bulbs make sense in lamps and fixtures where you want color control or individual bulb dimming and where the switch is unlikely to be turned off manually.
Motion sensors are the backbone of practical lighting automation. A basic motion automation turns lights on when motion is detected and off after a period of no motion. In Home Assistant, you create this using the automation editor by selecting the motion sensor as the trigger and the light as the action. The key configuration choices are the delay before turning off and whether to ignore the automation during daytime. Most motion sensors report battery level and can also report temperature, which makes them useful beyond lighting. For areas like hallways and bathrooms, a 2-minute off delay works well. For rooms where you sit still for long periods, like an office, consider a longer delay or add a second condition such as a lux sensor so the light only turns on when the room is dark enough to need it.
Time-based automations are useful for lights that should follow a daily schedule. A common setup turns on exterior lights at sunset and off at sunrise. Home Assistant has a built-in sun integration that provides sunset and sunrise triggers based on your location, so you do not need to hardcode times. You can also create time-based automations for interior lights, such as dimming bedroom lights at 10 PM or turning on a hallway light at 6 AM on weekdays. The time of day trigger in the automation editor lets you specify exact times, or you can use the numeric state of a sun elevation sensor for more precise control based on actual daylight conditions rather than the clock.
Scenes and groups let you control multiple lights as a single unit. A group combines lights so you can turn them all on or off with one command, but each light retains its individual state. A scene captures a specific state for multiple lights, including brightness and color, and applies them all at once. For example, a movie night scene might set the living room lights to 20 percent warm white and turn off the kitchen lights. Scenes are created in the Home Assistant scenes editor by selecting the lights you want to include and setting their target states. Groups can be created through the UI in the helpers section. Both scenes and groups can be triggered by automations, voice commands, or dashboard buttons.
Home Assistant integrates with Amazon Alexa and Google Assistant for voice control. To enable Alexa, install the Home Assistant Alexa integration through the Nabu Casa cloud subscription or use the Alexa Home Assistant skill with a manual setup. Google Assistant requires the Google Assistant integration, also available through Nabu Casa or a manual configuration. Once configured, you can expose any light, group, or scene to the voice assistant and control it by name. For fully local voice control, Home Assistant supports Wyoming Protocol with wake word detection, though this requires a microphone and more setup effort. Name your entities clearly so the assistant can match spoken commands to the right devices.
If your lights report power consumption, Home Assistant tracks energy usage through the built-in energy dashboard. Smart switches with energy monitoring, such as those from Shelly or Aeotec, report wattage in real time. Smart bulbs generally do not report power, so if energy tracking matters, smart switches are the better choice. The energy dashboard aggregates power data and shows daily, weekly, and monthly consumption. For broader home monitoring including water leak detection, see our guide on how to choose a water leak sensor.
The most common problem is lights not responding to automations. If the light works manually in the UI but not through an automation, check the automation trace to see which condition or trigger failed. If the light does not respond at all, verify that the device is still connected to its coordinator or WiFi network. Zigbee devices can drop off the mesh if they are too far from the coordinator. Adding a mains-powered Zigbee device between the coordinator and the problematic bulb extends the mesh. For WiFi lights that stopped responding, a factory reset and re-pairing is often the fix. If automations produce unexpected results, check for conflicting automations controlling the same light.
Start with a single room. Choose a smart switch over a smart bulb for fixed fixtures, use Zigbee with a USB coordinator for local control, and begin with a motion sensor automation before adding time-based rules. Once the first room works reliably, expand room by room. Avoid buying a large batch of devices before validating that the first setup works. If you need help, you can book a service appointment and we will set up the coordinator, pair the devices, and build the automations for you.
For more practical technology guides, check out our post on how to set up Home Assistant on a Raspberry Pi in 2026.