A standalone home automation stack that runs directly on embedded devices such as the Lidl/Silvercrest SGWZ 1 A1 Zigbee gateway (HG06339). Features include:
- A local web dashboard
- Device control
- Lua automation scripts with device events, timers and schedules
- Sensor history
- Browser Push and FCM Notifications
- An Android companion app for Matter setup and push alerts
- Zigbee and Matter-over-Thread support
- HTTP integrations for external devices: Shelly Gen 1 and Fritz!Box (as presence sensor)
Control lights and scenes, view temperature and humidity history, and receive alerts when a window stays open. See usage.
Dashboard shown with demo data.
Warning
This is a proof of concept / prototype, not production-ready software.
This entire project has been vibe coded. I have not meaningfully reviewed the code; my involvement has mainly been high-level architectural decisions.
The same applies to the documentation: it has not been thoroughly reviewed and may contain errors or omissions.
Special thanks to Paul Banks for the Lidl gateway root-access work that made this project possible.
Even though it currently runs on the stock firmware, this project would not
have been possible without
rtl8196e-gateway, maintained by
jnilo1, and the work of its contributors.
Thank you to the maintainers and contributors of the major upstream projects used here: Ziggurat, rs-matter, OpenThread, Mbed TLS, Lua, and nanopb, as well as their respective communities and all other upstream contributors.
This project is not affiliated with Lidl, Silvercrest or Tuya.
See the documentation index for setup, usage, deployment, recovery and developer guides. Configure your development machine with the shared host settings. Check supported devices for available features and compatibility limits.
The tested hardware is the Silvercrest SGWZ 1 A1 (HG06339) with an RTL8196E CPU, EFR32MG1B232 radio and factory Linux. Other embedded devices might work, but are not tested. First installation requires opening the case, a 3.3 V USB-to-UART adapter, root access, Ethernet and a Linux computer. Using Ziggurat and Matter requires changing the radio firmware.
- Check your hardware and follow the installation guide to obtain root access and make backups. For an existing Zigbee network, use the migration guide.
- Choose your setup and use a binary release and its SSH installer, or build from source. Binary bundles support MicroHAD-only with compatible stock EZSP firmware or the separately prepared Ziggurat/Matter stack. Follow the installation guide for root access, backups and radio prerequisites. Fresh-checkout dynamic builds also need the stock-library bootstrap.
- Open
http://<gateway-ip>/, pair a device, and check its readings or controls.
Components:
| Component | Purpose |
|---|---|
| MicroHAD | C++03 daemon, Web UI and REST API; owns the common device model, controls, history, alerts and integrations with external HTTP devices. |
| Ziggurat (optional) | Rust Zigbee stack and Spinel multiplexer; connects MicroHAD and Thread to the shared radio and is the sole owner of the radio UART. |
| mthread-matter (optional) | Rust Matter controller using rs-matter and userspace OpenThread; owns commissioning, fabrics, sessions, subscriptions and Thread state. |
| Firmware (optional, needed for Ziggurat and mthread-matter) | Rebuildable two-instance HDLC radio firmware, packaging and radio maintenance tools. |
| paired_start.sh | Starts, monitors and recovers MicroHAD, Ziggurat and mthread-matter as separate processes. The default configuration enables both optional services with ZIGGURAT=1 MATTER=1. |
The diagram shows application data paths in the default paired stack. The dotted supervisor link represents process management.
flowchart TB
browser["Dashboard browser"]
httpDevices["External http devices"]
subgraph gateway["Gateway · factory MIPS Linux"]
supervisor["paired_start.sh<br/>Supervisor"]
subgraph services["Three supervised services"]
native["MicroHAD <br/> C++03<br/>Web UI / REST API<br/>Common device model"]
matter["mthread-matter <br/> Rust<br/>Matter controller<br/>OpenThread IPv6 / UDP"]
ziggurat["Ziggurat <br/> Rust<br/>Zigbee stack<br/>Spinel multiplexer"]
native <-->|"Matter IPC · Unix socket"| matter
native <-->|"Ziggurat API · COBS / Unix socket"| ziggurat
matter <-->|"Thread Spinel · HDLC / Unix socket"| ziggurat
end
radio["EFR32MG1B232 radio<br/>Two-instance HDLC RCP firmware"]
supervisor -.-> services
ziggurat <-->|"UART · HDLC / Spinel"| radio
end
zigbeeDevices["Zigbee devices"]
matterDevices["Matter-over-Thread accessories"]
browser <-->|"HTTP / HTTPS"| native
native <-->|"HTTP(S) APIs / polling"| httpDevices
radio <-->|"IEEE 802.15.4 · Zigbee"| zigbeeDevices
radio <-->|"IEEE 802.15.4 · Thread<br/>Matter CASE / IPv6 / UDP"| matterDevices
classDef service fill:#e8f0fe,stroke:#476a9e,color:#172b4d
classDef hardware fill:#fff3dc,stroke:#a97928,color:#513b15
classDef endpoint fill:#f1f5f9,stroke:#64748b,color:#1e293b
classDef manager fill:#f3e8ff,stroke:#8655a3,color:#462661
class native,matter,ziggurat service
class radio hardware
class browser,httpDevices,zigbeeDevices,matterDevices endpoint
class supervisor manager
style gateway fill:#f8fafc,stroke:#94a3b8,color:#1e293b
style services fill:#ffffff,stroke:#94a3b8,color:#1e293b
| Link | Default socket | Protocol |
|---|---|---|
| MicroHAD ↔ Ziggurat | /tmp/ziggurat/native.sock |
COBS-framed Ziggurat API v2 |
| MicroHAD ↔ Matter service | /tmp/microhad-matter.sock |
Length-prefixed protobuf IPC v3 |
| OpenThread ↔ Ziggurat | /tmp/ziggurat/thread.sock |
HDLC-encoded Spinel; client IID 0 is mapped to radio IID 2 |
Zigbee and Thread share the radio through a patched Ziggurat. OpenThread runs inside
mthread-matter and provides IPv6/UDP without requiring Linux IPv6 or TUN.
The companion Android app uses the phone’s Bluetooth connection to commission Matter devices onto the gateway’s Thread network. Alternatively, Matter devices can be commissioned from the Web UI using Chrome on Android.
sequenceDiagram
participant accessory as Matter accessory
participant phone as MicroHAD Companion
participant native as MicroHAD
participant matter as mthread-matter
Note over accessory,matter: BLE commissioning · bidirectional packet relay
matter->>native: Outgoing BTP packet (Matter IPC)
native->>phone: WebSocket relay message
phone->>accessory: BLE GATT write
accessory->>phone: BLE GATT indication
phone->>native: WebSocket relay message
native->>matter: Incoming BTP packet (Matter IPC)
Note over accessory,matter: After provisioning: CASE control and reports use the Thread path above
See build setup for prerequisites and build instructions.
# Build MicroHAD for the host and run tests
make -C microhad host test
# Build MicroHAD for the gateway
make -C microhad mips
# Build the web dashboard
make -C microhad webui
# Build Ziggurat with shared Zigbee/Thread radio support
ZIGGURAT_MULTIPAN=1 bash ziggurat/scripts/build.sh
# Build the Matter daemon for the gateway
bash micro-thread-matter-daemon/scripts/build.sh mips service
# Build the radio access and bootloader maintenance helper
bash firmware/scripts/build-maintenance.shTo build without RSDK, first run python3 scripts/build-toolchain.py, then
select TOOLCHAIN=crosstool-ng for the target commands above (for example,
make -C microhad TOOLCHAIN=crosstool-ng mips). Crosstool-NG artifacts use separate
build/crosstool-ng/ directories. See toolchain selection
for commands, source credits and compatibility limits.
Root scripts/, config/ and patches/ contain shared build infrastructure,
compatibility patches and cross-service validation.
See the installation guide to prepare the gateway.
Use ./deploy.sh to upload the software, then activate and restart it as
described in the guide.
See native usage, Matter runtime, and recovery tooling.
Original project code and documentation are licensed under the MIT License, Copyright (c) 2026 MicroHAD contributors. Third-party code, assets and upstream-derived modifications retain their respective licenses; the root license does not relicense them. See third-party software and release obligations.