Redirección de puertos para Home Assistant
Puertos a abrir
¿Por qué es necesaria la redirección de puertos?
Most Home Assistant users access the dashboard from inside the LAN. Forwarding 8123 lets the mobile app and Google/Alexa integrations reach the instance from outside — but the Home Assistant Companion App now ships a remote-access "Nabu Casa" service that's safer.
Paso a paso por marca
TP-Link
- Assign a static IP / DHCP reservation to the Home Assistant host
- Virtual Servers → forward 8123 TCP to that host
- Set HA to use HTTPS via the duckdns + nginx-proxy-manager add-ons before exposing
Netgear
- Forward 8123 to HA host. Better: forward 443 to your nginx-proxy-manager / Caddy add-on that terminates TLS, then proxies internally to 8123.
ASUS
- Use the built-in DDNS + AiProtection. Forward 8123 only if you cannot use Nabu Casa cloud.
- Add HA to ASUS' Game Boost / QoS rules to keep responsiveness
Aviso de seguridad
Never expose 8123 without TLS, a strong password, and trusted_proxies hardening in HA configuration.yaml. Nabu Casa cloud ($6.5/mo) handles all of this for you and avoids touching your router.