I start with one light or sensor, one simple automation, and a recovery plan. I add community extensions only when the standard integrations cannot do the job.
Before I start
- A dedicated 64-bit x86 computer with UEFI, or an officially documented VM platform.
- An installation target you may erase, wired Ethernet, and initial Internet access.
- One supported smart-home device and its credentials; a place to keep backup recovery details.
Step by step
Choose Home Assistant OS
For this beginner path, I use Home Assistant OS on dedicated x86 hardware. It manages the underlying system and supports apps. Container installations have different responsibilities; do not mix their instructions with this path.
Prepare and write the boot disk
Follow the official x86 instructions: enable UEFI, configure the required boot settings, and write the official HAOS image to the intended disk. This overwrites that disk, so verify the target first.
Boot and complete onboarding
Connect Ethernet, boot, and allow initial components to download. Open http://homeassistant.local:8123 or http://<IP>:8123. Create the owner account, set home location and time zone, and use a DHCP reservation for a stable address.
Home Assistant: x86 installation · Home Assistant: onboarding
Add one integration
In Settings > Devices & services, add the device’s supported integration. Use the vendor’s documented setup when discovery does not find it. Assign a friendly name and a room so the dashboard remains understandable.
Create a small automation
In Settings > Automations & scenes, select Create automation. Add a Time trigger for 18:00, then a Light: Turn on action targeting the test light. Name it “Test light at 18:00” and save. I avoid heating, locks, and alarms for my first experiment.
Test trigger and action separately
Use the action test to check the device, then exercise the actual trigger. Inspect automation traces to see conditions and actions. I confirm the result physically rather than trusting the UI state alone.
Configure backups and recovery
Open Settings > System > Backups. Configure the supported backup schedule and destination, keep a copy outside this device, and store the backup emergency/recovery details securely. I document a restore using a spare instance.
Add safe remote access
I prefer an authenticated VPN or Home Assistant’s supported remote-access service. I do not forward port 8123 directly from the router. Enable strong account protection and review updates after taking a backup.
How I check the result
0 of 4 checks completed
Checklist progress stays in this browser. I use it to track checks, not to certify a deployment or compliance.
If something does not work
Cannot reach the UI
Use the DHCP lease IP with port 8123; check that first boot has Internet access.
Device not discovered
Check its integration requirements and network segmentation.
Automation works only when run manually
Inspect the real trigger, conditions, time zone, and trace.
My working templates
I compare an actual recovery with the recovery-time and recovery-point objectives.
Download CSV ↓Official sources I checked
I checked these sources on 13 October 2026. Product screens and legal requirements change; I verify the relevant source before a production rollout or legal decision.