# \[APP\]\[Pro\] Starlink Monitor

**URL:** <https://community.homey.app/t/app-pro-starlink-monitor/160477>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [October 7, 2026, 10:29am UTC](https://community.homey.app/t/app-pro-starlink-monitor/160477 "2026-10-07T10:29:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![HenriDO](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrido/32/84845_2.png) [@HenriDO](https://community.homey.app/u/HenriDO)\
**Post date:** [October 7, 2026, 10:29am UTC](https://community.homey.app/t/app-pro-starlink-monitor/160477/1 "2026-10-07T10:29:35Z")

</div>

Starlink Monitor

> **[Starlink Monitor | Homey](https://homey.app/en-us/app/com.rapinology.starlink/Starlink-Monitor/)**
>
> Keep an eye on the sky above your dish.

A dish that works is invisible. A dish that half works is maddening: the call drops for four seconds, the stream stalls, and by the time you go and look everything is fine again. Starlink Monitor keeps the record you never manage to keep yourself, and it keeps it on your own network, with no account and no key.

It talks to the dish directly, the same way the dish’s own diagnostics page does. Nothing goes to the cloud, nothing is sent anywhere, and it keeps working while the internet does not, which is rather the point.

### What the dish reports

| Capability | What it tells you |
| --- | --- |
| **Dish state** | Where it is in its own cycle, or what is stopping it |
| **Download speed** and **Upload speed** | In Mb/s, as the dish measures them |
| **Latency** | In ms |
| **Packet loss** | In per cent |
| **Sky obstruction** | How much of its view is blocked, in per cent |
| **Satellites in view** | How many it can see right now |
| **Alignment error** | How far off its ideal aim it sits, in degrees |
| **Azimuth** and **Elevation** | Where it actually points |
| **Uptime** | How long it has been running without a restart |
| **Power** | What it draws, so it shows up in Homey Energy |
| **Misaligned** and **Obstructed** | Alarms |

The alignment figures are the ones worth dwelling on. The dish knows where it would like to point and where it is actually pointing, and it never tells you the difference. The app puts the two side by side, so the question “would moving it help, and by how much” finally has an answer instead of an opinion.

### The outage log

The dish keeps its recent outages with a cause and a duration for each, and then keeps them to itself. The app reads that log and puts it on a tile: obstructed, no downlink, searching, booting, and the rest. A connection that merely feels unreliable becomes something you can look at, count, and argue with.

### Widgets

Seven, so you can build the dashboard you actually want rather than the one that was built for you.

- **Dish alignment** , a compass with the aim error at its centre
- **Throughput** , down and up
- **Latency**
- **Satellites**
- **Latency, fifteen minutes** , as a curve
- **Throughput, fifteen minutes** , as a curve
- **Outage log** , the last 5, 10 or 30 outages with their causes

Every widget takes a background: Night, Slate or Plum.

### Flow cards

Five triggers and three conditions. No actions: the app reads the dish, it never commands it.

Triggers:

- The alignment error rises above a threshold you set on the card
- The latency rises above a threshold you set on the card
- Sky obstruction rises above a threshold you set on the card
- The download speed drops below a threshold you set on the card
- The dish state changes

Conditions:

- The dish is, or is not, ready
- The dish is, or is not, misaligned
- The alignment error is, or is not, above a threshold

Thresholds live on the Flow card rather than on the device, so the same dish can feed a gentle warning and a loud one without the two fighting over a single setting.

### Settings

| Setting | Default |
| --- | --- |
| **Dish address** | 192.168.100.1 |
| **Refresh interval** | 60 seconds |
| **Misalignment threshold** | 10 degrees |

### If Homey cannot reach the dish

Worth reading before you report a bug, because this one catches people and it is not the app’s doing.

The dish answers on **192.168.100.1** , which is its own little network, separate from your home one. Your router reaches it because it talks to the dish directly. Homey has to be told how, and on some routers it simply is not: the request goes out of the wrong door and comes back as unreachable.

If pairing fails with the dish unreachable while your router’s own Starlink page works perfectly, that is what has happened. A static route to 192.168.100.0/24 pointing at your Starlink router fixes it. The app’s settings page explains the case in full, and it is written for people who do not spend their evenings in a router interface.

On a single router with one internet connection this almost never comes up. On a setup with two connections and load balancing it comes up every time, which is how I found it.

### No account, no key

Nothing to sign into, nothing to paste. The dish has no authentication of its own and answers anything on the local network, so the app simply asks it. Your position, your speeds and your outages stay on your Homey.

### Languages

English, French, German, Spanish, Italian, Dutch.

### Reporting a problem

Post here with your Homey firmware version, the app version, your dish generation, and whether your router is the Starlink one or your own. If pairing is what fails, say whether your router’s Starlink page works from the same network, because that single detail separates a routing problem from an app problem.

**I have tested this on Starlink Mini; please inform me if you encounter any problem with another dish.**

Feedback and testers welcome.

Have fun 😉

---

<div class="post-metadata">

**Author:** ![Jogi\_Bear](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jogi_bear/32/34384_2.png) [@Jogi\_Bear](https://community.homey.app/u/Jogi_Bear)\
**Post date:** [October 8, 2026, 11:56am UTC](https://community.homey.app/t/app-pro-starlink-monitor/160477/2 "2026-10-08T11:56:43Z")

</div>

Hi Henri,

I have a Standard Dish (V4 / Gen 3) and your Starlink Monitor works perfect on my Homey Pro (Early 2019).

Thank you for your work.

I did not need a static route.

Via MQTT Hub i made it also available to Home Assistant.

 ![Starlink Monitor](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/1/0183c29e2ad70f26c454086276978399571e0f84.jpeg)

---

<div class="post-metadata">

**Author:** ![HenriDO](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henrido/32/84845_2.png) [@HenriDO](https://community.homey.app/u/HenriDO)\
**Post date:** [October 26, 2026, 2:13pm UTC](https://community.homey.app/t/app-pro-starlink-monitor/160477/3 "2026-10-26T14:13:45Z")

</div>

Starlink Monitor 1.1.0 is out. Until now the app knew what the dish was doing; it now remembers what the dish went through.

 ![widgets](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/c/7c0749573e011207322d07ce1b6211702ecf028e.jpeg)

**Three more widgets** , ten in all:

- **Sky obstructions** , the sky seen from above, with the obstructions your dish has mapped. The trees finally get a picture.
- **Availability** , uptime over 24 hours, 7 and 30 days, with the number of outages and their main causes.
- **Throughput and latency trends** , over the last 24 hours or 7 days.

The app keeps its own outage log, so the 7 and 30 day figures survive a restart. An unreachable dish is not counted as an outage: Homey can lose its route to the dish while your internet is perfectly fine, and I did not want the app blaming Starlink for something your router did.

**Backgrounds** : five instead of three. Night is now Deep blue, and Forest and Sand join Slate and Plum.

**Capabilities** : **Availability, 24 h** , **Dish alert** and **Active alerts**. The alerts are the dish’s own, thermal throttling, stuck motors, slow Ethernet and sixteen others, which it used to keep to itself.

 ![planche](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/4/a4a225b4db5b57601d246fb6cb9575ad8c8cbe56.jpeg)

**New Flow cards**

- When: _An outage started_, _An outage of at least [x] s ended_, _The 24 h availability drops below [x] %_, _The dish raised an alert_, _A dish alert cleared_
- And: _The alert [x] is active_

Newer dishes that only give their serial number in their status can be added again; pairing no longer calls them unreachable.

If a figure looks different from what the Starlink app shows, tell me here, with your dish generation.

More about the app, every widget and Flow card included: [Starlink Monitor for Homey — Rapinology](https://rapinology.com/en/homey/starlink/)

Have fun 😉
