Multi-Protocol Bridge: Solving the Fragmentation Problem
Most smart homes accumulate devices across multiple protocols: WiFi cameras, Zigbee switches, Z-Wave sensors, Modbus solar inverters, and RS-485 energy meters — each with its own app, unable to trigger automations across protocol boundaries. Home Assistant serves as the Universal Gateway that unifies everything.
Protocol Stack
Zigbee via Sonoff USB Dongle Plus + Zigbee2MQTT (700 THB), Z-Wave via RaZberry 7 GPIO hat (2,500 THB), WiFi devices via native ESPHome/Matter integration, Modbus RTU via Waveshare RS-485 USB adapter (400 THB), and Modbus TCP via Ethernet — all exposed to Home Assistant as standard entities.
Zigbee2MQTT vs HA Native Zigbee
Zigbee2MQTT is preferred over the built-in ZHA integration because it supports significantly more devices, exposes raw attributes, and updates faster. MQTT autodiscovery brings all Zigbee devices into Home Assistant automatically.
Modbus Solar Integration
Solar inverters (Solaredge, Fronius, SMA) expose generation and grid data via Modbus holding registers. Home Assistant Modbus integration reads solar power, grid import, grid export, and battery state into sensors updated every 30 seconds.
Energy Sankey Diagram
The ha-sankey-chart HACS custom card renders real-time energy flow: solar → home, solar → EV, solar → grid export, grid → home — a single glance shows the energy balance for today and whether the home is net-positive.
Cross-Protocol Automation Examples
With all protocols unified: Z-Wave door lock open → Zigbee lights on + security disarmed + WiFi camera checks; solar export drops to zero (night) → Modbus inverter mode shift + EV charging schedule adjusted; poor air quality + occupancy → Zigbee purifier switch on + ERV Modbus fan boost.