HA Local Ecosystem Access
Home Assistant edge hub · Mesh / Wi-Fi / cameras unified
Why Home Assistant
Local-first & privacy-ready | Cross-brand unify | Strong extensible ecosystem | MXCHIP hardware & integration
Edge local automation
Run Home Assistant via Docker on a Linux host — local rules and automations without always-on cloud
Heterogeneous devices, one control plane
Bring BLE Mesh, third-party Wi-Fi, and RTSP cameras into one control plane — fewer apps, less fragmentation
Extensible open-source ecosystem
HA as the hub, with Xiaodu and other voice assistants; Matter remains an optional access path
Alexa
Google
MatterLocal-first · Privacy-ready
Following Home Assistant's local-control, privacy-first stance — with MXCHIP edge hardware so brand whole-home solutions rely less on always-on public cloud.
Local processing first
Device state and automations stay on the edge; local linkage keeps running if the public network drops
Cloud only when needed
No forced always-on public cloud; add MXCHIP Cloud or a business platform only when needed
Brand data under control
For brands and integrators: keep core data on the customer edge and reduce cloud dependency
HA capability layer
For brands and integrators: bring Home Assistant integrations, automations, and dashboards onto MXCHIP modules, gateways, and edge vision hardware.
Broad integration
→Unify MXCHIP Mesh, heterogeneous Wi-Fi IoT devices, and RTSP cameras on one control plane
Powerful automation
→Trigger · Condition · Action: lighting scenes, security alerts, vacancy energy-saving, and more
Ops-ready dashboard
→Dashboards for device and scene status — for delivery acceptance and day-to-day ops
Extensible
→Community Blueprints and sidecars supported; HA Assist optional, Xiaodu interconnection preferred
Typical automation scenes
Automation examples rewritten as MXCHIP-deliverable scenes so customers can align requirements quickly.
DeepStream + YOLO 视觉联动
摄像头 RTSP 进边端，ROI / Zone 内人员检测后事件交给 Home Assistant，再联动 IoT。完整五步管线与案例见独立应用页。
LEARN MOREEdge architecture reference
Hub stack: Linux → Nvidia Jetson (GPU) → Local AI Model (DeepStream+YOLO) → Home Assistant. BLE Mesh gateway, heterogeneous Wi-Fi, RTSP cameras, and voice assistants (secondary) connect around it.
Smart home · edge architecture
BLE Mesh devices
Light
Switch
ThermostatBLE Mesh gateway
MXCHIP smart gateway
MXCHIP smart control panelIP cameras (RTSP)
Bullet camera
Dome camera
Indoor cameraAI边缘计算单元
Home Assistant
Local smart home hub platform
Local AI Model
DeepStream+YOLO
SEDGE-NJ10
GPU compute
Linux OS
for ARM
AI video analytics
YOLO
Object detection
Vehicle recognition
Behavior analysis
Alert notify
Third-party devices (Wi-Fi)
Door lock
Ambient sensing
Presence sensingVoice assistants / speakers
Xiaodu
Alexa
GoogleSecondary to HA narrative · not a hub replacement
连线色对齐产品全景：蓝=Mesh/通用 · 橙=Wi-Fi · 绿=RTSP。Mesh 子设备 → 蓝牙 Mesh 网关 → AI边缘计算单元（HA + Local AI Model + SEDGE）；摄像头 / Wi-Fi / 语音助手接入中枢。
Edge deployment path
Aligned with Home Assistant Container: Linux + Docker recommended; MXCHIP delivers hardware selection and integration — not a replacement for the open-source project.
Recommended: Linux + Docker
Deploy Home Assistant as a container on the edge host — clear ops path, aligned with MXCHIP delivery
Connect MXCHIP hardware
蓝牙 Mesh 网关 / 模组、AI边缘计算单元（SEDGE）进入同一 HA 控制面
Optional: HA OS
Customers may self-host Home Assistant OS; MXCHIP focuses on hardware selection and bring-up
MXCHIP delivery
Hardware selection · integration · advisor support; public docs without login
Concept cheat sheet
Help business and delivery teams align on Home Assistant basics (not a developer tutorial).
Ingest and interconnect
Same as the cloud-edge-device panorama: modules / gateways at the edge, HA + local models for automation, cloud business platforms only as needed.
BLE Mesh→
MXCHIP Mesh gateway manages lights / switches / thermostats into HA local automation
Heterogeneous Wi-Fi→
Third-party locks, environment and occupancy sensors join the same HA control plane
Edge vision→
IP cameras enter the edge via RTSP; Local AI Model (DeepStream+YOLO) runs on-device detection and can trigger HA automations
Voice assistant interconnect→
Xiaodu and other voice paths stay secondary to the HA narrative — not a replacement for the local automation hub
Ecosystem partners
Home Assistant and Xiaodu featured; other platforms shown as secondary "etc." to avoid multi-brand speaker parity.
Home Assistant
PrimaryEdge hub · open ecosystem
Xiaodu speaker
Recommended speakerVoice assistant interconnect
etc.·Tmall Genie · HarmonyOS Connect · JD IoT · Alexa · Google · HomeKit
Optional · not primary
Matter Access
Matter is an optional certification / access path — not co-primary with HA. Use the access flow when cross-brand standard access is required.
Learn about Matter Access →开启 HA 本地生态接入对接
Tell us your device form-factor and edge setup — an advisor will assess the HA path one-on-one.
Public docs without login · Matter Access on a dedicated page
