Home Assistant: Difference between revisions

Revision as of 22:25, 6 August 2026

Home Assistant is an open source home automation server. It has integrations for a wide variety of devices, and allows you to create custom dashboards for viewing sensor information and controlling your devices. If you want to access your Home Assistant instance from anywhere, but cannot port forward due to CGNAT, making your instance publicly accessible via 44Net is one solution. Even if your home internet isn't behind CGNAT, it likely has a dynamic IP, which would require you to set up dynamic DNS for your instance to maintain consistent external access. A 44Net IP lets your instance be publicly accessible at a fixed IPv4 address for free.

Step 1: Set up your tunnel

Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a single device tunnel. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on bare metal, the recommended configuration is to put it on a routed subnet.

For fresh installations using a single device tunnel, if you want Home Assistant to also be available on the LAN, configure WireGuard as a split tunnel by setting AllowedIPs to 44.0.0.0/9, 44.128.0.0/10.

@@ Line 1: / Line 1: @@
 Home Assistant is an open source home automation server. It has integrations for a wide variety of devices, and allows you to create custom dashboards for viewing sensor information and controlling your devices. If you want to access your Home Assistant instance from anywhere, but cannot port forward due to {{Term|CGNAT}}, making your instance publicly accessible via 44Net is one solution. Even if your home internet isn't behind CGNAT, it likely has a dynamic IP, which would require you to set up dynamic DNS for your instance to maintain consistent external access. A 44Net IP lets your instance be publicly accessible at a fixed IPv4 address for free.
-Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. It's not designed to be directly facing the internet, as it has poor device firewall configuration options. Using the shell to edit the <code>iptables</code> or <code>nftables</code> config is technically possible, but it's not officially supported and risks breaking the Docker <code>iptables</code> configuration that apps running inside Home Assistant use. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, or already have it running as a VM or Docker container, the easiest option is running it as a docker container on a device with a single device tunnel. If you have a dedicated physical Home Assistant appliance, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet | routed subnet]].
+== Step 1: Set up your tunnel ==
+Home Assistant OS is designed to operate less like a general purpose computing device and more like an appliance. There is no package manager with which to install higher level firewall tools, and the Home Assistant WireGuard application is unmaintained as of 2026. If you're setting up a fresh Home Assistant installation for the express purpose of exposing it to 44Net, the easiest option is running it as a docker container on a device with a [[44Net_Connect/Single Device Tunnel | single device tunnel]]. If you have a dedicated Home Assistant appliance, such as a Home Assistant Green or a Raspberry Pi running Home Assistant OS on {{Term|bare metal}}, the recommended configuration is to put it on a [[44Net_Connect/Routed Subnet | routed subnet]].
+For fresh installations using a single device tunnel, if you want Home Assistant to also be available on the LAN, configure WireGuard as a {{Term|split tunnel}} by setting <code>AllowedIPs</code> to <code>44.0.0.0/9, 44.128.0.0/10</code>.