How to Connect a Smart Home Hub to Starlink Without Losing Local Control

A smart-home hub such as Home Assistant, Hubitat or another local controller can work well on Starlink. The important part is to separate three jobs: keeping the hub and smart devices reachable on your home network, letting selected services use the internet, and choosing a safe way to manage the system when you are away.

This guide uses a model-agnostic setup. Starlink router menus, third-party routers and smart-home hubs vary, so follow the current instructions for your exact hardware when a menu or pairing step differs.

The safest default is one main router, one DHCP service and a trusted home network. Do not expose a hub's administration page to the public internet just to make remote access work.

The short answer

1. Decide which router provides Wi-Fi, routing and DHCP.
2. Connect the hub to the main household network, preferably by Ethernet.
3. Keep the hub and the devices it must discover on the same local network.
4. Give the hub a DHCP reservation on the router that owns DHCP.
5. Test local automations with the internet temporarily unavailable.
6. Use the hub maker's secure relay or a reputable mesh VPN for remote access instead of casually opening ports.

A DHCP reservation creates a predictable private address. It does not create a public or static internet address. For background, see How to Set Up a Starlink DHCP Reservation for Stable Local IPs.

Before you start

Have these ready:

• Your Starlink kit and the current Starlink app
• The smart-home hub and its latest available firmware
• An Ethernet cable, Ethernet Adapter or a reliable Wi-Fi connection
• A phone or computer that can join your main Starlink network
• A list of the devices the hub should control
• A backup or export of the hub configuration if the hub supports it

Write down which device is connected to the dish and which device provides the household IP addresses. Also note whether your hub will use Ethernet or Wi-Fi.

Do not do the first setup during a critical automation, remote meeting or backup. Keep physical access to the hub and router in case a pairing step temporarily disconnects them.

1. Choose one main router

The simplest design is for one device to own the local network.

Starlink router as the main router

Keep the Starlink router in its normal routing mode when you only need ordinary Wi-Fi and local device control. Connect the hub to the Starlink router, its Ethernet Adapter, or a switch connected to that LAN.

If you add a mesh system or extra access point, use access-point or bridge mode when available. The Starlink router can then continue to provide DHCP and the firewall.

Your own router as the main router

Use your own router as the main router only when you have a reason to manage routing, VLANs, advanced firewall rules or more detailed smart-home controls. If your hardware supports bypass mode, prepare the replacement router first, then change modes and confirm that it provides DHCP and Wi-Fi.

After the change, connect one phone or computer and check that it receives an address from the intended router. Test the hub locally before reconnecting every smart device.

Avoid leaving two routers in full router mode unless you have deliberately designed the two networks. Double NAT and separate subnets can prevent device discovery even when both networks have internet access. For a closer look at that decision, see Starlink Double NAT: How to Diagnose It and Pick the Right Fix.

2. Put the hub on the trusted home network

For initial setup, connect your phone or computer to the main household Wi-Fi, not a guest network.

Then:

1. Power the hub and wait for its normal startup sequence.
2. Connect it by Ethernet where possible. A wired link avoids Wi-Fi interference and makes local discovery more predictable.
3. If the hub requires Wi-Fi, join the main household network and follow its pairing flow.
4. Create a unique administrator password and enable multi-factor authentication if the hub offers it.
5. Install the hub's current updates, then restart it once before adding a large number of devices.
6. Confirm that the hub's dashboard opens from another device on the same home network.

A guest network may intentionally block device-to-device communication. That is useful for visitors and some isolated IoT devices, but it is usually the wrong place for a hub that needs to discover lights, sensors, speakers or switches.

If the hub or a smart device supports only 2.4 GHz, use the pairing method documented by the manufacturer. Some routers can handle both bands automatically; others may need the bands separated temporarily during setup. Do not change several network settings at once, and restore the preferred arrangement only after one device has completed pairing.

3. Add devices in small groups

Start with one device of each important type, such as a light, sensor or plug.

For each device:

1. Reset it only when the manufacturer's instructions call for a reset.
2. Add it through the hub's normal integration or discovery process.
3. Give it a clear name and location.
4. Test both the device's state and the hub's response.
5. Record whether the integration is local, cloud-based or dependent on a vendor account.

If the hub cannot discover a device, check the basics first:

• Both devices are on the same local network or on networks that are intentionally allowed to communicate.
• The device is not connected to a guest SSID with client isolation.
• The phone used for pairing is on the same network as the device.
• The device is close enough to the router for its initial setup.
• The device supports the Wi-Fi band and security settings being offered.
• Any Bluetooth, local-network or location permission required by the setup app is enabled.

Do not factory-reset every device because one pairing attempt failed. Test one change at a time so you know which change helped.

4. Give the hub a stable local address

Open the client list on the router that actually provides DHCP. Identify the hub by its current address and MAC address, then create an IP reservation, DHCP reservation or static lease.

After saving it:

1. Restart the hub or renew its network lease.
2. Confirm that it receives the reserved private address.
3. Open the hub dashboard from a second local device.
4. Run one automation and check its event or activity log.
5. Update any local bookmark or integration that used the old address.

Reserve the address on the routing device, not on an access point that merely passes traffic through. Avoid typing a random manual address into the hub unless its documentation explains the correct subnet, gateway, DNS and address range.

A local address such as 192.168.x.x or 10.x.x.x is not a public address. The reservation will not bypass Starlink CGNAT or make the hub reachable from outside your home.

5. Keep important automations local

A good test is to separate local control from cloud features.

With the hub and smart devices still powered:

1. Disconnect the Starlink internet connection or temporarily unplug the dish/router WAN path.
2. Keep your phone or laptop connected to the same local Wi-Fi.
3. Trigger a local automation, such as turning on a light from the hub dashboard.
4. Check whether a sensor update reaches the hub.
5. Restore the internet connection and confirm that cloud integrations reconnect.

Local automations may continue during an internet outage if the hub and devices do not need a vendor cloud service for that action. Cloud-only devices, voice assistants, remote notifications and integrations that depend on an outside account may stop until Starlink returns.

Check the hub's time zone and clock after the test. Scheduled automations can behave unexpectedly if a hub loses time synchronisation during a long outage or after a power cycle.

6. Set up remote access safely

Do not begin with port forwarding. Starlink connections may use carrier-grade NAT, and a working local hub does not prove that inbound internet connections are possible. Even where a public address is available, an exposed administration page increases risk.

Safer options usually include:

• The hub maker's authenticated remote-access service, with a strong password and multi-factor authentication
• A reputable mesh VPN that connects only your approved devices
• An outbound tunnel designed for the specific service, with access controls and current software

Set up remote access only after local control works. Then test it from a phone using mobile data, not from the same Starlink Wi-Fi. Do not publish the hub's administrator port, disable its firewall, or reuse the Wi-Fi password as the hub password.

For the difference between public IP, static IP and CGNAT, see Does Starlink Provide a Static IP? Public IP, CGNAT and Safe Alternatives.

7. Plan for power cuts and restarts

A hub that controls heating, lighting or security is only as dependable as its power path.

• Put the hub, router and any essential bridge on the same suitable UPS when practical.
• Check that the hub is configured to restart automatically after power returns.
• Allow the Starlink router time to reconnect before diagnosing the hub.
• Keep a physical switch or manual control for important lights, locks and heating.
• Save a current hub backup somewhere that is not only stored on the hub.
• Record the normal recovery order for the dish, router, hub and key devices.

Do not overload a UPS or improvise a power connection. Use the equipment's documented power supplies and treat electrical work as a job for a qualified professional.

Quick validation checklist

Your smart-home hub setup is in good shape when:

• The hub dashboard opens from two devices on the trusted local network.
• The hub has a stable private address from the correct DHCP server.
• At least one important automation works with the internet temporarily unavailable.
• Device discovery works without placing the hub on a guest network.
• Cloud-dependent features fail clearly and reconnect after Starlink returns.
• Remote access works only through an intentional, authenticated method.
• You can restore the hub from a backup after a reset or hardware replacement.

What not to do

• Put the hub on a guest network and expect local discovery to work.
• Run DHCP on both the Starlink router and a second router on the same LAN.
• Open the hub's administration page to the internet as a first troubleshooting step.
• Assume a DHCP reservation is a public or static IP.
• Pair every device at once before testing one complete path.
• Change bypass mode, Wi-Fi bands, DNS and firewall settings in one large experiment.

The reliable pattern is straightforward: one clear network owner, a trusted local connection, a reserved private address, local-first automations and deliberate remote access.