How to Monitor Starlink With Home Assistant: A Practical Local Setup Guide

Starlink users often discover a problem only after a work call, camera alert or download has already failed. Home Assistant can give you an earlier warning by reading Starlink's local status and turning it into a simple dashboard or notification.

This guide uses Home Assistant's built-in Starlink integration. It is designed for monitoring and diagnosis, not for changing advanced network settings. You do not need to expose your Starlink terminal to the public internet.

What this setup can tell you

The integration can provide:

• Connected: whether Starlink currently reports an internet connection.
• Ping and Ping drop rate: useful for spotting rising latency or packet loss.
• Downlink and uplink throughput: the current traffic rate through the terminal.
• Download and upload totals: cumulative traffic counters.
• Power and energy: the last measured power and accumulated energy use, when your hardware exposes them.
• Obstructed: whether the terminal currently reports an obstruction.
• Heating: whether the terminal is heating, such as while dealing with cold or snow.
• Slow ethernet: whether the Ethernet link is below its expected maximum.
• Thermal throttle: whether Starlink has reduced performance to manage heat.
• Last restart and an optional restart button.

Entity names vary by Home Assistant installation, so use the names shown in your own device page when building a dashboard or automation.

Before you add it

1. Make sure Home Assistant and the Starlink network are on the same local network, or that your router has a deliberate route between them.
2. Update Home Assistant during a normal maintenance window if it is several releases behind.
3. Decide what you want to detect first. A good starting point is a short internet outage, repeated packet loss, and an obstruction.
4. Keep the Starlink app available. Home Assistant is a monitoring layer; the Starlink app remains the place to review the service account, hardware status and official support options.

Do not create a port-forwarding rule for the Starlink terminal just to make this integration work. Remote access should be provided through your normal secure Home Assistant method, not by publishing the terminal's local API.

Add the Starlink integration

1. Open Home Assistant.
2. Go to Settings > Devices & services.
3. Select Add integration.
4. Search for Starlink.
5. Follow the on-screen setup steps.
6. Open the new Starlink device and confirm that the Connected, Ping and Ping drop rate entities have values.

The integration uses local polling. In a normal Starlink Router setup, discovery may work without extra network changes.

If you use bypass mode or a third-party router

Bypass mode changes the path between Home Assistant and the Starlink terminal. Home Assistant's documentation warns that the local API must still be reachable through a route; otherwise the integration will not work.

Check these items in order:

1. Confirm that Home Assistant has normal internet access through the third-party router.
2. Confirm that the third-party router is not blocking traffic to the Starlink terminal's local management network.
3. Add a narrow route to the terminal's local API network only if your router requires it. Use the Starlink and router documentation for the correct gateway and interface for your model.
4. Avoid broad, automatic routes that could create a loop or expose the terminal to other networks.
5. Reload the integration and check whether the device entities become available.

If the integration works in the standard router layout but stops working after bypass mode, the missing route is a more likely cause than a faulty dish.

Build a useful dashboard

Start with a small view that answers three questions:

• Is Starlink connected?
• Is the link becoming unreliable?
• Is the terminal reporting a physical or thermal problem?

Add these entities to a dashboard:

1. Connected as a prominent status badge.
2. Ping and Ping drop rate as history graphs.
3. Obstructed, Heating and Thermal throttle as diagnostic indicators.
4. Downlink throughput and Uplink throughput when you want to see whether a slowdown is caused by traffic on your own network.
5. Power or Energy if you run Starlink from a battery or want to understand its electrical cost.

Give the graphs enough history to be useful. A single bad reading is rarely a reason to change hardware. Look for a repeated pattern: packet loss during a specific time of day, obstructions during a particular weather event, or a link that becomes slow whenever the Ethernet indicator reports a reduced link speed.

Add one outage alert

A simple first automation is to notify you only when Connected has stayed off for several minutes. That prevents a brief satellite handoff or Wi-Fi hiccup from becoming an unnecessary alarm.

You can create this in the Home Assistant automation editor:

1. Create a new automation with a State trigger.
2. Select the Starlink Connected binary sensor.
3. Set the new state to Off.
4. Add a duration of 5 minutes.
5. Add your preferred notification action.
6. Include a message that says the outage has lasted at least five minutes.
7. Save the automation and test the notification using Home Assistant's action test control.

The five-minute period is a practical starting point, not a Starlink rule. Shorten or lengthen it based on how often your connection has brief interruptions.

For YAML users, the shape is:

Replace the example entity ID and notification service with the names used in your installation. If your device exposes Connected as a sensor rather than a binary sensor, select the entity from the automation editor instead of copying the example unchanged.

Turn alerts into diagnosis

Once the basic alert works, add context rather than many separate alarms:

• If Connected is off but your router and Home Assistant are still reachable, the issue may be upstream of your local Wi-Fi.
• If Connected stays on but Ping drop rate rises, compare the timing with obstructions, weather and heavy local uploads.
• If Obstructed is on repeatedly, inspect the sky view and mounting position before changing router settings.
• If Thermal throttle is on, check ventilation and heat around the equipment.
• If Slow ethernet is on, check the cable, negotiated link speed and the port on the third-party router or switch.
• If Home Assistant itself cannot reach the device after a network redesign, check routing and firewall rules before resetting Starlink.

This separation keeps you from treating every symptom as a speed problem. The same “slow internet” complaint can come from packet loss, a physical obstruction, a congested local network, a bad Ethernet link or an unavailable terminal API.

Test the finished setup

After adding the device and alert:

1. Confirm that normal Connected, Ping and diagnostic values update.
2. Open the Starlink app and compare its current status with Home Assistant.
3. Review the graphs after a day or two, rather than judging from one reading.
4. Test the notification action without deliberately interrupting service.
5. If you change routers, enable bypass mode or move Home Assistant to another network, re-check the integration before assuming the monitoring is still working.

The best result is a quiet dashboard that gives you evidence when something changes. It should help you decide whether to wait, inspect the dish, check local networking or contact Starlink support.

Sources and attribution

• Home Assistant Starlink integration documentation - integration setup, local polling, available entities and the bypass-mode routing requirement.
• Starlink - official service and support destination.