Checking on an Empty Cabin Without Exposing Its Network

A small always-on box at the cabin, a Twingate Connector making outbound-only connections, and per-service Resources let you check a thermostat, camera, or water shutoff valve from anywhere — no port forwards, works behind Starlink or LTE CGNAT. Start with the Twingate quickstart.
The Insurance Information Institute puts water damage and freezing at roughly 23% of homeowners insurance claims. Vacation homes are especially exposed because nobody is there to hear the pipe crack at 2am on a Tuesday in February.
This post is about what to actually build at an unattended cabin so you get told when something is wrong — and then have a way to look, verify, and act without putting any of it on the public internet. It's a tutorial, but the shape of the problem (a remote site, intermittent connectivity, no hands on-site) is the same one enterprise IT teams solve at branch offices. The tools scale down cleanly.
What this setup does and doesn't do
Before anything else, be honest about division of labor. Remote access is not what saves the pipes. Local automation is what saves the pipes.
Automated and local: freeze detection, leak detection, auto-shutoff of the water main, push notifications.
Remote and human: confirming the reading, checking the camera, closing the valve manually if the auto-shutoff didn't fire, calling a neighbor to go turn the heat back on.
If the internet is down or Home Assistant can't reach a notification service, your freeze alert still has to fire locally and your shutoff valve still has to close locally. That means the valve has to be one Home Assistant controls directly, not through a vendor cloud (more on this below). Remote access is for what you do next.
The architecture
Here's the whole setup at a glance:
A small always-on box at the cabin (Raspberry Pi 5, Home Assistant Green, Intel NUC, whatever you have) running Home Assistant or your automation platform of choice.
Z-Wave or Zigbee sensors for temperature, leak detection, and door/window state.
A smart water shutoff on the main. If you want it to close with the internet down, use a Z-Wave or Zigbee motorized valve controlled by Home Assistant. Wi-Fi valves like Moen Flo and Phyn are controlled through the vendor's cloud and won't respond to local automations when the WAN is down.
A couple of IP cameras on a separate VLAN. Allow the Connector's host through your inter-VLAN firewall to the specific camera IPs and ports.
A UPS on the router and the automation box.
A Twingate Connector running on the same box (or a separate small device), making outbound-only connections to the Twingate Controller.
Twingate Resources defined per service — Home Assistant UI, camera streams, the router admin page — each with its own access policy.
Nothing listens for inbound connections from the internet. The cabin network has no port forwards, no exposed admin pages, no dynamic DNS pointing at your home. From the outside, the cabin looks like a laptop browsing the web.
Why outbound-only matters, especially on Starlink or LTE
Most cabins run on whatever connectivity is available, which usually means Starlink or an LTE/5G modem. Both put you behind carrier-grade NAT (CGNAT). On most residential Starlink plans and nearly all LTE plans, you don't get a routable public IPv4 address, so the port-forward model doesn't work. You can't open 443 to your Home Assistant instance because there's no public IP to open 443 on.
This is where Twingate's architecture fits the problem exactly. The Connector at the cabin makes outbound connections to the Twingate Controller — the same way your laptop makes an outbound connection to Google. Carrier NAT doesn't care. Firewalls don't care. Nothing on the cabin side needs inbound reachability, ever.
Prerequisites
A Twingate account. The free Starter plan covers up to 5 users, which is plenty for a cabin. Everyone you give access to, including a neighbor, counts toward that limit.
An always-on box at the cabin running Linux, Docker, or Home Assistant OS.
Home Assistant (or similar) already installed, with sensors and automations working on the local network.
An identity provider for sign-in. Google or Microsoft works fine for personal use.
A UPS. Seriously. More on this below.
Step 1: Create a Remote Network
In the Twingate admin console, create a new Remote Network for the cabin. Call it something you'll recognize six months from now — cabin-vt or lake-house, not remote-network-3.
A Remote Network in Twingate is just a logical grouping. It's where your Connector lives and where you'll attach Resources. One Remote Network per physical site is the clean pattern, and it maps well if you ever add a second property.
Step 2: Deploy the Connector
The Connector is a lightweight piece of software that runs behind the cabin's firewall and makes outbound TLS connections to the Controller. It's the thing that proxies your traffic to the local Resources when you're authorized.
If you're running Home Assistant OS, the easiest path is the Twingate add-on. If you're running Docker on a Pi or NUC, this is the one-liner, using tokens you'll generate in the admin console when you add the Connector:
Run the Twingate Connector in Docker with the access and refresh tokens from the admin console.
For production reliability, Twingate recommends two Connectors per Remote Network so one can restart or update without taking access down. At a cabin, you can get away with one if your other option is nothing, but a second Connector is a cheap upgrade. Two on the same box covers restarts and updates. Two on separate devices also covers a hardware failure. Each Connector needs its own token pair.
Step 3: Define Resources per service
A Resource in Twingate is a specific thing you want to reach — a hostname, an IP, a port range. You do not add "the whole cabin network." You add each service individually.
For a typical cabin setup, this might be:
192.168.1.10on port 8123 — the Home Assistant UI192.168.1.1on port 443 — the router admin page192.168.1.50on port 554 — RTSP stream from the front camera192.168.1.51on port 554 — RTSP stream from the mechanical room camera
Use IPs or a real internal DNS name (such as ha.cabin.home.arpa), not .local names. On macOS and iOS, .local names go to mDNS, so the Client may not match them.
Many cameras send video over UDP on other ports, even when control uses TCP 554. Set RTSP to TCP in your camera or player, or allow the needed UDP range on the Resource.
Each Resource gets its own access policy. You might give your spouse access to Home Assistant and the cameras, but keep the router admin page restricted to you. A neighbor you've asked to help in emergencies can get a time-limited policy on just the front door camera and nothing else.
This is the part that matters most for an unattended site: if someone's device is compromised, they don't get "the cabin network." They get the specific resources they were authorized for. There is no network to scan from a compromised laptop, because the Client never places the user on the cabin LAN. It only proxies the specific requests that match a Resource.
Step 4: Install the Client on the devices you'll check from
Install the Twingate Client on your phone and laptop. Sign in with your IdP. When you open 192.168.1.10:8123 in a browser, the Client matches it against your authorized Resources, and routes the connection through the Connector at the cabin. Nothing else on your laptop's traffic is affected — it's split-tunneled.
From the user side, it feels like you're on the cabin network. From the cabin's side, nothing changed. Nothing is listening. Nothing is exposed.
Step 5: Local alerting that works without you
Set up your automations so the critical stuff fires locally and pushes out:
Low-temperature alert: trigger at 45°F anywhere in the house. Send a push notification via the Home Assistant Companion app (uses Firebase/APNs, works over the cabin's outbound internet).
Leak sensors: on any wet reading, close the smart water valve and send a notification.
Freeze + no internet: if the alert can't push, the local automation still closes the water main (with a locally controlled Z-Wave or Zigbee valve). You find out when you next connect.
The notification is the tell me something is wrong. Remote access via Twingate is the let me go look and decide what to do about it. Keep those two jobs separate in your head.
The failure that actually matters: power and internet
Everything above assumes the box is on and the WAN link is up. The most common failure mode at a cabin is neither Home Assistant crashing nor Twingate going down — it's a 36-hour power outage in January that takes the router, the automation box, and the heat with it.
A UPS on the router and the automation box buys you the window where it matters most. A 600VA unit will typically run a Starlink dish, router, and Pi for 30 to 60 minutes. Check your model's runtime chart. If you want hours, size up to a 1500VA unit or a LiFePO4 power station. That's often enough to:
Push the "power lost" notification before the UPS dies
Ride through short grid blips without rebooting everything
Give you time to call a neighbor
For longer outages, the realistic answer is that you need somebody local. No amount of remote access substitutes for a human with a key. The setup's job is to tell you fast enough that calling that human is useful.
A few things worth doing on the local side:
Put the Starlink or LTE modem, router, and automation box on the UPS. Skip the cameras — they can wait.
Add a UPS battery sensor in Home Assistant so you get a "running on battery" alert immediately, not when the UPS dies.
If the cabin loses heat often enough that it's a known risk, consider a heat source that doesn't need grid power, such as a direct-vent propane wall heater with millivolt ignition — totally independent of your smart home stack. Belt and suspenders.
What you've built
A cabin that calls you when something's wrong and lets you verify, from your phone, what's actually happening — without a single port open to the internet, without a static IP, and without trusting any one device with access to everything. A sensor firing and a valve closing happen locally and keep happening whether the internet is up or down. Twingate is the layer that gives you eyes and hands when you're not there.
If you want to go further, the same pattern extends to multiple sites. A second Remote Network for your actual house, a third for a parent's place you help manage. Same Connectors, same policies, same Client.
Closing
For more on deploying Connectors and defining Resources, check the Twingate documentation. The Connector deployment guide and Resources overview are the two pages to start with.
New to Twingate? You can use Twingate for free for up to 5 users, request a personalized demo, or reach out to the team over on the Twingate subreddit.
Rapidly implement a modern Zero Trust network that is more secure and maintainable than VPNs.
Checking on an Empty Cabin Without Exposing Its Network

A small always-on box at the cabin, a Twingate Connector making outbound-only connections, and per-service Resources let you check a thermostat, camera, or water shutoff valve from anywhere — no port forwards, works behind Starlink or LTE CGNAT. Start with the Twingate quickstart.
The Insurance Information Institute puts water damage and freezing at roughly 23% of homeowners insurance claims. Vacation homes are especially exposed because nobody is there to hear the pipe crack at 2am on a Tuesday in February.
This post is about what to actually build at an unattended cabin so you get told when something is wrong — and then have a way to look, verify, and act without putting any of it on the public internet. It's a tutorial, but the shape of the problem (a remote site, intermittent connectivity, no hands on-site) is the same one enterprise IT teams solve at branch offices. The tools scale down cleanly.
What this setup does and doesn't do
Before anything else, be honest about division of labor. Remote access is not what saves the pipes. Local automation is what saves the pipes.
Automated and local: freeze detection, leak detection, auto-shutoff of the water main, push notifications.
Remote and human: confirming the reading, checking the camera, closing the valve manually if the auto-shutoff didn't fire, calling a neighbor to go turn the heat back on.
If the internet is down or Home Assistant can't reach a notification service, your freeze alert still has to fire locally and your shutoff valve still has to close locally. That means the valve has to be one Home Assistant controls directly, not through a vendor cloud (more on this below). Remote access is for what you do next.
The architecture
Here's the whole setup at a glance:
A small always-on box at the cabin (Raspberry Pi 5, Home Assistant Green, Intel NUC, whatever you have) running Home Assistant or your automation platform of choice.
Z-Wave or Zigbee sensors for temperature, leak detection, and door/window state.
A smart water shutoff on the main. If you want it to close with the internet down, use a Z-Wave or Zigbee motorized valve controlled by Home Assistant. Wi-Fi valves like Moen Flo and Phyn are controlled through the vendor's cloud and won't respond to local automations when the WAN is down.
A couple of IP cameras on a separate VLAN. Allow the Connector's host through your inter-VLAN firewall to the specific camera IPs and ports.
A UPS on the router and the automation box.
A Twingate Connector running on the same box (or a separate small device), making outbound-only connections to the Twingate Controller.
Twingate Resources defined per service — Home Assistant UI, camera streams, the router admin page — each with its own access policy.
Nothing listens for inbound connections from the internet. The cabin network has no port forwards, no exposed admin pages, no dynamic DNS pointing at your home. From the outside, the cabin looks like a laptop browsing the web.
Why outbound-only matters, especially on Starlink or LTE
Most cabins run on whatever connectivity is available, which usually means Starlink or an LTE/5G modem. Both put you behind carrier-grade NAT (CGNAT). On most residential Starlink plans and nearly all LTE plans, you don't get a routable public IPv4 address, so the port-forward model doesn't work. You can't open 443 to your Home Assistant instance because there's no public IP to open 443 on.
This is where Twingate's architecture fits the problem exactly. The Connector at the cabin makes outbound connections to the Twingate Controller — the same way your laptop makes an outbound connection to Google. Carrier NAT doesn't care. Firewalls don't care. Nothing on the cabin side needs inbound reachability, ever.
Prerequisites
A Twingate account. The free Starter plan covers up to 5 users, which is plenty for a cabin. Everyone you give access to, including a neighbor, counts toward that limit.
An always-on box at the cabin running Linux, Docker, or Home Assistant OS.
Home Assistant (or similar) already installed, with sensors and automations working on the local network.
An identity provider for sign-in. Google or Microsoft works fine for personal use.
A UPS. Seriously. More on this below.
Step 1: Create a Remote Network
In the Twingate admin console, create a new Remote Network for the cabin. Call it something you'll recognize six months from now — cabin-vt or lake-house, not remote-network-3.
A Remote Network in Twingate is just a logical grouping. It's where your Connector lives and where you'll attach Resources. One Remote Network per physical site is the clean pattern, and it maps well if you ever add a second property.
Step 2: Deploy the Connector
The Connector is a lightweight piece of software that runs behind the cabin's firewall and makes outbound TLS connections to the Controller. It's the thing that proxies your traffic to the local Resources when you're authorized.
If you're running Home Assistant OS, the easiest path is the Twingate add-on. If you're running Docker on a Pi or NUC, this is the one-liner, using tokens you'll generate in the admin console when you add the Connector:
Run the Twingate Connector in Docker with the access and refresh tokens from the admin console.
For production reliability, Twingate recommends two Connectors per Remote Network so one can restart or update without taking access down. At a cabin, you can get away with one if your other option is nothing, but a second Connector is a cheap upgrade. Two on the same box covers restarts and updates. Two on separate devices also covers a hardware failure. Each Connector needs its own token pair.
Step 3: Define Resources per service
A Resource in Twingate is a specific thing you want to reach — a hostname, an IP, a port range. You do not add "the whole cabin network." You add each service individually.
For a typical cabin setup, this might be:
192.168.1.10on port 8123 — the Home Assistant UI192.168.1.1on port 443 — the router admin page192.168.1.50on port 554 — RTSP stream from the front camera192.168.1.51on port 554 — RTSP stream from the mechanical room camera
Use IPs or a real internal DNS name (such as ha.cabin.home.arpa), not .local names. On macOS and iOS, .local names go to mDNS, so the Client may not match them.
Many cameras send video over UDP on other ports, even when control uses TCP 554. Set RTSP to TCP in your camera or player, or allow the needed UDP range on the Resource.
Each Resource gets its own access policy. You might give your spouse access to Home Assistant and the cameras, but keep the router admin page restricted to you. A neighbor you've asked to help in emergencies can get a time-limited policy on just the front door camera and nothing else.
This is the part that matters most for an unattended site: if someone's device is compromised, they don't get "the cabin network." They get the specific resources they were authorized for. There is no network to scan from a compromised laptop, because the Client never places the user on the cabin LAN. It only proxies the specific requests that match a Resource.
Step 4: Install the Client on the devices you'll check from
Install the Twingate Client on your phone and laptop. Sign in with your IdP. When you open 192.168.1.10:8123 in a browser, the Client matches it against your authorized Resources, and routes the connection through the Connector at the cabin. Nothing else on your laptop's traffic is affected — it's split-tunneled.
From the user side, it feels like you're on the cabin network. From the cabin's side, nothing changed. Nothing is listening. Nothing is exposed.
Step 5: Local alerting that works without you
Set up your automations so the critical stuff fires locally and pushes out:
Low-temperature alert: trigger at 45°F anywhere in the house. Send a push notification via the Home Assistant Companion app (uses Firebase/APNs, works over the cabin's outbound internet).
Leak sensors: on any wet reading, close the smart water valve and send a notification.
Freeze + no internet: if the alert can't push, the local automation still closes the water main (with a locally controlled Z-Wave or Zigbee valve). You find out when you next connect.
The notification is the tell me something is wrong. Remote access via Twingate is the let me go look and decide what to do about it. Keep those two jobs separate in your head.
The failure that actually matters: power and internet
Everything above assumes the box is on and the WAN link is up. The most common failure mode at a cabin is neither Home Assistant crashing nor Twingate going down — it's a 36-hour power outage in January that takes the router, the automation box, and the heat with it.
A UPS on the router and the automation box buys you the window where it matters most. A 600VA unit will typically run a Starlink dish, router, and Pi for 30 to 60 minutes. Check your model's runtime chart. If you want hours, size up to a 1500VA unit or a LiFePO4 power station. That's often enough to:
Push the "power lost" notification before the UPS dies
Ride through short grid blips without rebooting everything
Give you time to call a neighbor
For longer outages, the realistic answer is that you need somebody local. No amount of remote access substitutes for a human with a key. The setup's job is to tell you fast enough that calling that human is useful.
A few things worth doing on the local side:
Put the Starlink or LTE modem, router, and automation box on the UPS. Skip the cameras — they can wait.
Add a UPS battery sensor in Home Assistant so you get a "running on battery" alert immediately, not when the UPS dies.
If the cabin loses heat often enough that it's a known risk, consider a heat source that doesn't need grid power, such as a direct-vent propane wall heater with millivolt ignition — totally independent of your smart home stack. Belt and suspenders.
What you've built
A cabin that calls you when something's wrong and lets you verify, from your phone, what's actually happening — without a single port open to the internet, without a static IP, and without trusting any one device with access to everything. A sensor firing and a valve closing happen locally and keep happening whether the internet is up or down. Twingate is the layer that gives you eyes and hands when you're not there.
If you want to go further, the same pattern extends to multiple sites. A second Remote Network for your actual house, a third for a parent's place you help manage. Same Connectors, same policies, same Client.
Closing
For more on deploying Connectors and defining Resources, check the Twingate documentation. The Connector deployment guide and Resources overview are the two pages to start with.
New to Twingate? You can use Twingate for free for up to 5 users, request a personalized demo, or reach out to the team over on the Twingate subreddit.
Rapidly implement a modern Zero Trust network that is more secure and maintainable than VPNs.
Checking on an Empty Cabin Without Exposing Its Network

A small always-on box at the cabin, a Twingate Connector making outbound-only connections, and per-service Resources let you check a thermostat, camera, or water shutoff valve from anywhere — no port forwards, works behind Starlink or LTE CGNAT. Start with the Twingate quickstart.
The Insurance Information Institute puts water damage and freezing at roughly 23% of homeowners insurance claims. Vacation homes are especially exposed because nobody is there to hear the pipe crack at 2am on a Tuesday in February.
This post is about what to actually build at an unattended cabin so you get told when something is wrong — and then have a way to look, verify, and act without putting any of it on the public internet. It's a tutorial, but the shape of the problem (a remote site, intermittent connectivity, no hands on-site) is the same one enterprise IT teams solve at branch offices. The tools scale down cleanly.
What this setup does and doesn't do
Before anything else, be honest about division of labor. Remote access is not what saves the pipes. Local automation is what saves the pipes.
Automated and local: freeze detection, leak detection, auto-shutoff of the water main, push notifications.
Remote and human: confirming the reading, checking the camera, closing the valve manually if the auto-shutoff didn't fire, calling a neighbor to go turn the heat back on.
If the internet is down or Home Assistant can't reach a notification service, your freeze alert still has to fire locally and your shutoff valve still has to close locally. That means the valve has to be one Home Assistant controls directly, not through a vendor cloud (more on this below). Remote access is for what you do next.
The architecture
Here's the whole setup at a glance:
A small always-on box at the cabin (Raspberry Pi 5, Home Assistant Green, Intel NUC, whatever you have) running Home Assistant or your automation platform of choice.
Z-Wave or Zigbee sensors for temperature, leak detection, and door/window state.
A smart water shutoff on the main. If you want it to close with the internet down, use a Z-Wave or Zigbee motorized valve controlled by Home Assistant. Wi-Fi valves like Moen Flo and Phyn are controlled through the vendor's cloud and won't respond to local automations when the WAN is down.
A couple of IP cameras on a separate VLAN. Allow the Connector's host through your inter-VLAN firewall to the specific camera IPs and ports.
A UPS on the router and the automation box.
A Twingate Connector running on the same box (or a separate small device), making outbound-only connections to the Twingate Controller.
Twingate Resources defined per service — Home Assistant UI, camera streams, the router admin page — each with its own access policy.
Nothing listens for inbound connections from the internet. The cabin network has no port forwards, no exposed admin pages, no dynamic DNS pointing at your home. From the outside, the cabin looks like a laptop browsing the web.
Why outbound-only matters, especially on Starlink or LTE
Most cabins run on whatever connectivity is available, which usually means Starlink or an LTE/5G modem. Both put you behind carrier-grade NAT (CGNAT). On most residential Starlink plans and nearly all LTE plans, you don't get a routable public IPv4 address, so the port-forward model doesn't work. You can't open 443 to your Home Assistant instance because there's no public IP to open 443 on.
This is where Twingate's architecture fits the problem exactly. The Connector at the cabin makes outbound connections to the Twingate Controller — the same way your laptop makes an outbound connection to Google. Carrier NAT doesn't care. Firewalls don't care. Nothing on the cabin side needs inbound reachability, ever.
Prerequisites
A Twingate account. The free Starter plan covers up to 5 users, which is plenty for a cabin. Everyone you give access to, including a neighbor, counts toward that limit.
An always-on box at the cabin running Linux, Docker, or Home Assistant OS.
Home Assistant (or similar) already installed, with sensors and automations working on the local network.
An identity provider for sign-in. Google or Microsoft works fine for personal use.
A UPS. Seriously. More on this below.
Step 1: Create a Remote Network
In the Twingate admin console, create a new Remote Network for the cabin. Call it something you'll recognize six months from now — cabin-vt or lake-house, not remote-network-3.
A Remote Network in Twingate is just a logical grouping. It's where your Connector lives and where you'll attach Resources. One Remote Network per physical site is the clean pattern, and it maps well if you ever add a second property.
Step 2: Deploy the Connector
The Connector is a lightweight piece of software that runs behind the cabin's firewall and makes outbound TLS connections to the Controller. It's the thing that proxies your traffic to the local Resources when you're authorized.
If you're running Home Assistant OS, the easiest path is the Twingate add-on. If you're running Docker on a Pi or NUC, this is the one-liner, using tokens you'll generate in the admin console when you add the Connector:
Run the Twingate Connector in Docker with the access and refresh tokens from the admin console.
For production reliability, Twingate recommends two Connectors per Remote Network so one can restart or update without taking access down. At a cabin, you can get away with one if your other option is nothing, but a second Connector is a cheap upgrade. Two on the same box covers restarts and updates. Two on separate devices also covers a hardware failure. Each Connector needs its own token pair.
Step 3: Define Resources per service
A Resource in Twingate is a specific thing you want to reach — a hostname, an IP, a port range. You do not add "the whole cabin network." You add each service individually.
For a typical cabin setup, this might be:
192.168.1.10on port 8123 — the Home Assistant UI192.168.1.1on port 443 — the router admin page192.168.1.50on port 554 — RTSP stream from the front camera192.168.1.51on port 554 — RTSP stream from the mechanical room camera
Use IPs or a real internal DNS name (such as ha.cabin.home.arpa), not .local names. On macOS and iOS, .local names go to mDNS, so the Client may not match them.
Many cameras send video over UDP on other ports, even when control uses TCP 554. Set RTSP to TCP in your camera or player, or allow the needed UDP range on the Resource.
Each Resource gets its own access policy. You might give your spouse access to Home Assistant and the cameras, but keep the router admin page restricted to you. A neighbor you've asked to help in emergencies can get a time-limited policy on just the front door camera and nothing else.
This is the part that matters most for an unattended site: if someone's device is compromised, they don't get "the cabin network." They get the specific resources they were authorized for. There is no network to scan from a compromised laptop, because the Client never places the user on the cabin LAN. It only proxies the specific requests that match a Resource.
Step 4: Install the Client on the devices you'll check from
Install the Twingate Client on your phone and laptop. Sign in with your IdP. When you open 192.168.1.10:8123 in a browser, the Client matches it against your authorized Resources, and routes the connection through the Connector at the cabin. Nothing else on your laptop's traffic is affected — it's split-tunneled.
From the user side, it feels like you're on the cabin network. From the cabin's side, nothing changed. Nothing is listening. Nothing is exposed.
Step 5: Local alerting that works without you
Set up your automations so the critical stuff fires locally and pushes out:
Low-temperature alert: trigger at 45°F anywhere in the house. Send a push notification via the Home Assistant Companion app (uses Firebase/APNs, works over the cabin's outbound internet).
Leak sensors: on any wet reading, close the smart water valve and send a notification.
Freeze + no internet: if the alert can't push, the local automation still closes the water main (with a locally controlled Z-Wave or Zigbee valve). You find out when you next connect.
The notification is the tell me something is wrong. Remote access via Twingate is the let me go look and decide what to do about it. Keep those two jobs separate in your head.
The failure that actually matters: power and internet
Everything above assumes the box is on and the WAN link is up. The most common failure mode at a cabin is neither Home Assistant crashing nor Twingate going down — it's a 36-hour power outage in January that takes the router, the automation box, and the heat with it.
A UPS on the router and the automation box buys you the window where it matters most. A 600VA unit will typically run a Starlink dish, router, and Pi for 30 to 60 minutes. Check your model's runtime chart. If you want hours, size up to a 1500VA unit or a LiFePO4 power station. That's often enough to:
Push the "power lost" notification before the UPS dies
Ride through short grid blips without rebooting everything
Give you time to call a neighbor
For longer outages, the realistic answer is that you need somebody local. No amount of remote access substitutes for a human with a key. The setup's job is to tell you fast enough that calling that human is useful.
A few things worth doing on the local side:
Put the Starlink or LTE modem, router, and automation box on the UPS. Skip the cameras — they can wait.
Add a UPS battery sensor in Home Assistant so you get a "running on battery" alert immediately, not when the UPS dies.
If the cabin loses heat often enough that it's a known risk, consider a heat source that doesn't need grid power, such as a direct-vent propane wall heater with millivolt ignition — totally independent of your smart home stack. Belt and suspenders.
What you've built
A cabin that calls you when something's wrong and lets you verify, from your phone, what's actually happening — without a single port open to the internet, without a static IP, and without trusting any one device with access to everything. A sensor firing and a valve closing happen locally and keep happening whether the internet is up or down. Twingate is the layer that gives you eyes and hands when you're not there.
If you want to go further, the same pattern extends to multiple sites. A second Remote Network for your actual house, a third for a parent's place you help manage. Same Connectors, same policies, same Client.
Closing
For more on deploying Connectors and defining Resources, check the Twingate documentation. The Connector deployment guide and Resources overview are the two pages to start with.
New to Twingate? You can use Twingate for free for up to 5 users, request a personalized demo, or reach out to the team over on the Twingate subreddit.
Solutions
Solutions
The VPN replacement your workforce will love.
Solutions