"Starlink Outage No Schedule" - The Starlink connection is deemed disconnected after "Searching" notifications, even when the duration is brief

Background:

  • B20X synergized with multiple cellular connections (via a Transit Duo and an HD2 Dome) and one (synergized) Starlink connection.
    (The synergy component is probably irrelevant).

  • “Ignore Obstruction Outages” is enabled on the B20X.

Observation:

  • The obstruction notifications are handled appropriately (the link is not considered disconnected unless the real health-checks kick in).

  • However, the similarly brief notifications that the dish is looking for a satellite (reported in the event log as “Starlink Outage No Schedule”, recorded internally at Starlink as “Searching”) cause an immediate disconnect. This is not as frequent as the “obstructed” events, but they usually go together (all “searching” events are associated with an “obstructed” event in my sample history). In my sample the searching duration is shorter than the obstructed duration.

Modification suggestion:
Either

  • Treat the “searching” notification similarly to the “obstructed” notifications (i.e.ignore them at the connection level, and let the health checks take care of things if the duration is too long).

or

  • Provide for an (additional) more generic option in handling of Starlink connections, allowing the generic health-check mechanism to be the means by which the router considers the Starlink disconnected or live.

or both options.