AZiT
no way out WireGuard tunnel tunnel down direct, but no DNS guests: direct, but no DNS direct: PS5 and guests igc1 igc2 igc3 igc4 igc5 port 2 Internet VPN provider WireGuard, fails closed Firewall OpenBSD and pf, six ports Admin 192.168.1.0/24 laptop, wired Access point one cable, four networks Management untagged, AP only Trusted, VLAN 10 phones, laptop IoT, VLAN 20 isolated clients Guest, VLAN 30 internet only PS5 192.168.3.0/24 direct route Media 192.168.4.0/24 Kodi Servers 192.168.5.0/24 DeskPi Super6c six Raspberry Pi CM5, one switch Kubernetes: 3 control, 2 workers cp1 cp2 cp3 w1 w2 Flux, Traefik, TLS SIEM sixth board: UniFi controller Raspberry Pi 3B Home Assistant

Home Assistant is highlighted; its page is below.

Home Assistant

Home Assistant runs on a Raspberry Pi 3B, plugged into the Super6c's second Ethernet port in the server network. It may reach the IoT network to control devices; phones on the trusted Wi-Fi may reach its web interface.

Why it stays separate#

Home Assistant is the one thing that must work when the cluster is being rebuilt. Keeping it on its own small board means a cluster experiment never turns the lights off.

The Raspberry Pi 3B in a blue 3D-printed case with a fan
The Raspberry Pi 3B that runs Home Assistant, in its printed case.
A Sonoff Zigbee 3.0 USB Dongle Plus with its antenna attached
Its Zigbee stick, which talks to the lights and sensors directly.

See also: Policy