Automation and integrations

All integrations are optional, off by default and supervised: a broker or server outage never blocks routing, the Service Gateway or the Web UI.

The ESP32 publishes to an MQTT broker used by Home Assistant Discovery, and sends ntfy notifications to a phone. — MQTT/Home Assistant and ntfy paths.

MQTT and Home Assistant

Two different jobs: the gateway's MQTT integration exposes its own controls and status to Home Assistant; LAN → Tailnet forwarding lets an ordinary LAN device reach a remote MQTT broker. You can use either independently. Connect MQTT devices across two homes.

Retained availability and state with Last Will; bounded snapshot size.
Discovery entities: Service Gateway rule switches and destination-test buttons, Wake-on-LAN and recovery buttons, Service watch, profile and status sensors.
Strict command payloads; rule commands include the rule's binding token.

Guides: MQTT, Home Assistant.

ntfy

Outage and system-event alerts, Service watch changes, and replay-protected info, Wake-on-LAN and recovery commands. Local logs are never uploaded; private details stay hidden unless you enable them. Guide: ntfy.

SNMP

Read-only SNMP v1/v2c with an operational subtree for monitoring systems. Unencrypted: restrict UDP 161 with the firewall and use a private community.

Security

Remote commands are as trusted as their transport. Prefer TLS, private topics and per-client broker ACLs; keep command features off unless you need them.