How to Set Up Hue Lights Without Bridge Architecture Guide

Tech architecture infographic titled "Home Assistant Architecture" using archetype HOW-IT-WORKS adapted as a device timeline for a smart home setup. Show a left-to-right timeline of labeled boxes connected by directional arrows, explaining how a generic home assistant system controls smart lights without a bridge. Include these components as clean vector boxes with icons, English names, and one-line English role descriptions: 1) Mobile App — "User control interface for setup, scenes, and automation"; 2) Home Assistant Server — "Local automation hub that orchestrates devices and rules"; 3) Wi-Fi Router — "Local network path for device discovery and IP traffic"; 4) Zigbee USB Dongle or Direct Radio Adapter — "Local radio coordinator for direct device pairing"; 5) Smart Light Bulbs — "Endpoint lights that receive on/off, brightness, and color commands"; 6) Automation Engine — "Executes schedules, triggers, and room logic"; 7) Optional Cloud Service — "Remote access and notifications, not required for local control". Use arrows with short English labels such as: "HTTPS login", "REST API call", "WebSocket state update", "mDNS discovery", "DHCP IP address", "Zigbee pairing", "On/Off command", "Brightness payload", "State report", "Automation trigger", "Push notification". Make the flow technically accurate for a bridge-less setup: app connects over HTTPS or local web UI to Home Assistant Server, server discovers devices on local network or via direct radio adapter, direct pairing to bulbs happens through Zigbee coordinator when supported, control commands and state updates stay local, optional cloud path only for remote access. Add small callouts for realistic setup concepts: "No dedicated bridge required", "Local-first control", "Direct pairing", "LAN automation", "Optional remote access". Include a numbered legend 1-7 in English walking through the lifecycle: 1. User opens the mobile app or local dashboard. 2. Home Assistant authenticates the session and loads device states. 3. The server discovers compatible lights on the local network or through the radio adapter. 4. Bulbs are paired directly to the coordinator instead of a separate bridge. 5. Control commands are sent as local network or Zigbee messages. 6. Devices return state updates for brightness, color, and availability. 7. Automations run locally, with cloud services used only when remote access is enabled. Visual style: tech editorial, warm beige and navy palette, soft muted accents, clean line icons, subtle shadows, tidy spacing, calm premium smart-home mood, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Avoid any real smart home brand logos; use only generic smart speaker, phone, server, router, dongle, bulb, and cloud icons. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real smart home brand logos (no Google Home / Alexa / HomePod). Generic icons.