Zigbee vs Matter vs WiFi Smart Home Protocol Infographic

Tech architecture infographic titled "Zigbee vs Matter vs WiFi — Smart Home Protocol Comparison" using HOW-IT-WORKS archetype adapted to a house floor plan with devices. Show a clean top-down smart home floor plan with labeled rooms and connected smart devices as BOXES arranged inside the house: Smart Bulb, Motion Sensor, Thermostat, Smart Lock, Security Camera, Smart Plug, Voice Assistant Hub, Border Router, WiFi Router, Smartphone App, Home Controller, Cloud Service. Each box must include a simple generic tech icon, the device/service name, and a one-line English role description. Use grouped protocol overlays and clearly separated connection paths with ARROWS: Zigbee mesh links between low-power devices and hub/border router; Matter links across Thread / WiFi / Ethernet compatible devices through a controller and border router; WiFi links directly from devices to WiFi router and local network/cloud. Add short arrow labels in English such as "Zigbee mesh packet", "Thread message", "Matter command", "HTTPS API", "WiFi TCP/IP", "Device status", "Firmware update", "Local automation". Include protocol comparison callouts as side-by-side labeled panels: "Zigbee", "Matter", "WiFi" with concise technical properties in English: network type, range pattern, power usage, internet dependency, interoperability, latency tendency, and common device types. Make the flow technically accurate: Zigbee uses IEEE 802.15.4 mesh to a coordinator/hub, Matter runs at the application layer over Thread / WiFi / Ethernet with local controller communication, WiFi devices connect by IP directly to router and often to cloud over HTTPS. Show numbered stages as a 1-7 legend in English explaining a typical smart home action lifecycle: 1. User taps Smartphone App to send a command. 2. Home Controller determines whether the target device uses Zigbee, Matter, or WiFi. 3. For Zigbee, command goes via Hub/Coordinator over IEEE 802.15.4 mesh. 4. For Matter, command goes from Controller through Border Router over Thread or directly over WiFi/Ethernet. 5. For WiFi, device receives IP command from local network or cloud service via HTTPS/TCP. 6. Device executes action and returns state update or acknowledgment. 7. App and automation dashboard display updated status and trigger local routines. Add visual comparison badges near paths: "Low Power", "Mesh Network", "IP-Native", "Cloud-Optional", "High Bandwidth", "Battery Friendly" where appropriate. Visual style: tech editorial, cool tech blue palette, subtle cyan highlights, deep navy outlines, soft ice-blue background, precise vector lines, gentle glow accents for active paths, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. No brand-specific devices or logos; use generic smart speaker, router, phone, cloud, and sensor icons only. All text rendered cleanly in English, no spelling errors, no gibberish characters, 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.