Zigbee gateway controller for the ConBee II USB dongle — an excellent device compatible with most Zigbee vendors including Philips Hue, IKEA Tradfri, Aqara, Sonoff, and more.
| File | Description |
|---|---|
pv.yaml |
PersistentVolume + PersistentVolumeClaim (NFS-backed, 20M) |
svc.yaml |
LoadBalancer service — ports 80 (HTTP) and 443 (HTTPS) |
deployment.yaml |
deCONZ with ConBee II USB device passthrough |
1. Plug in the ConBee II USB dongle and verify the device path on your Pi:
ls /dev/ttyACM*
# typically /dev/ttyACM0 or /dev/ttyACM1If your device appears on ttyACM0 instead of ttyACM1, update both references in deployment.yaml:
- name: DECONZ_DEVICE
value: /dev/ttyACM0and:
- name: dev-ttyacm1
hostPath:
path: /dev/ttyACM02. Edit pv.yaml — set your NFS server IP and export path:
nfs:
server: 192.168.1.15
path: /home/pi/nfs/k8sdata/deconzkubectl apply -f pv.yaml
kubectl apply -f svc.yaml
kubectl apply -f deployment.yaml
kubectl rollout status deploy/deconz# Pod running?
kubectl get pods -l app=deconz
# External IP assigned by MetalLB?
kubectl get svc deconz
# deCONZ UI reachable?
# Navigate to http://<EXTERNAL-IP> in your browserHome Assistant will auto-discover the deCONZ gateway on your network and prompt you to integrate it automatically via the Integrations page. No manual configuration needed.
hostNetwork: true— required for Home Assistant auto-discovery to work across the LANprivileged: true— required for USB device passthrough to the ConBee II dongle- Port
5900— VNC access to the deCONZ visual network map (optional, LAN only) - Typo fixed in original
svc.yaml— port name wasssh(443), corrected tohttps - Volume name normalised from
dev-ama1todev-ttyacm1for clarity
