Building a Unified Nervous System
A proper Home Automation setup doesn’t rely on cloud providers. In the Nexus, everything IoT operates strictly locally.
Home Assistant & ioBroker
The intelligence layer currently utilizes Home Assistant. It provides the primary dashboard, handles complex automations, and unifies standard protocols. It’s the most powerful controller on the market for aggregating diverse ecosystems.
However, I also maintain ioBroker. Why both? In the DACH (Germany, Austria, Switzerland) region, ioBroker has historically exceptional adapter support for European hardware (like KNX, some specialized solar protocols, or specific heating controllers) that sometimes supersedes generic integrations. While I’m consolidating, ioBroker remains for certain specialized integrations.
Zigbee2MQTT & Mosquito MQTT-Broker
Vendor hubs (Philips Hue, IKEA Tradfri) are a security and compatibility nightmare. Instead, I use a universal Zigbee coordinator stick communicating directly with Zigbee2MQTT.
This completely eliminates cloud-dependency for bulbs, sensors, and switches. The hardware reports via a standardized format to the Eclipse Mosquitto MQTT Broker, which Home Assistant instantly ingests. This decoupled architecture means my database (HA) and my hardware controller (Z2M) operate independently, vastly increasing stability.
Custom Energy Dashboards
As part of the monitoring layer, I wrote custom software explicitly for mapping and charting solar virtualization. While things like Grafana are incredibly potent, a bespoke dashboard allows for specifically tailored user interfaces for non-technical household members to monitor energy consumption at a glance.