Starlink Integration Fails To Connect

[LordNex]

The problem

I have rectangular Starlink with the Ethernet adapter plugged into a fully manageable IPS/IDS Firewalla Gold Firewall. I’ve added the static route to be able to access the API and am able to do so by using the iOS app or by going to http://dishy.starlink.com which resolves to 192.168.100.1. Up until recently I’ve had the integration loaded and working. I’m not sure when but at some point the integration disapeared. Now when I try and add it back in I just get a “Failed to connect” message even though I can still access it via app or web interface

What version of Home Assistant Core has the issue?

2023.11.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Starlink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/starlink

Diagnostics information

System Information

version	core-2023.11.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.6
os_name	Linux
os_version	6.1.59
arch	x86_64
timezone	America/Chicago
config_dir	/config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.33.0 Stage | running Available Repositories | 1415 Downloaded Repositories | 115 HACS Data | ok

Home Assistant Cloud

logged_in | true -- | -- subscription_expiration | March 2, 2024 at 6:00 PM relayer_connected | true relayer_region | us-east-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | us-east-1-2.ui.nabu.casa certificate_status | ready can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 11.1 -- | -- update_channel | stable supervisor_version | supervisor-2023.11.3 agent_version | 1.6.0 docker_version | 24.0.6 disk_total | 786.7 GB disk_used | 107.8 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | AdGuard Home (4.8.17), AirCast (4.0.1), AirSonos (4.0.1), Duck DNS (1.15.0), ESPHome (2023.11.3), File editor (5.7.0), Frigate Proxy (1.3), MariaDB (2.6.1), Matrix (0.10.0), Z-Wave JS (0.4.1), Studio Code Server (5.14.2), Advanced SSH & Web Terminal (16.0.1), Traccar (0.22.0), Tor (4.3.0), chrony (2.6.2), TasmoAdmin (0.26.0), Spotify Connect (0.12.6), Node-RED (16.0.2), Samba share (12.1.0), Samba Backup (5.2.0), Exadel CompreFace (1.1.0), AppDaemon (0.15.2), Bookstack (1.10.1), Matter Server (4.10.2), go2rtc master hardware (master-hardware), EMQX (0.2.12), Terminal & SSH (9.8.1), Tailscale (0.13.1), Music Assistant BETA (2.0.0b75), OpenThread Border Router (2.3.2), Piper (1.4.0), Whisper (1.0.0), Vaultwarden (Bitwarden) (0.20.1), openWakeWord (1.8.2), Google Assistant SDK (2.5.0), Docker Wyze Bridge (2.5.1), TubesZB Silicon Labs FW Flasher (0.2.2), DeepStack (CPU) (2021.09.1), SSH Tunnel (1.0.6), CodeProject AI.Server (CPU) (2.3.4.1), Double Take (1.13.11.8)

Dashboards

dashboards | 7 -- | -- resources | 61 views | 15 mode | storage

NextDNS

can_reach_server | ok -- | --

Recorder

oldest_recorder_run | May 28, 2023 at 4:00 AM -- | -- current_recorder_run | November 23, 2023 at 4:17 PM estimated_db_size | 10815.00 MiB database_engine | mysql database_version | 10.6.12

Spotify

api_endpoint_reachable | ok -- | --

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @boswelja, mind taking a look at this issue as it has been labeled with an integration (starlink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `starlink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign starlink` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

starlink documentation starlink source _{^{(message by IssueLinks)}}

[LordNex]

I figured it out. Don’t know why but I had to create specific routes from each subnet HA is in and statically route that port to the correct interface. The core team really needs to fix the ability to select the default outgoing adapters as many of us use segmented VLANd networks.