Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starlink Integration uses extreme data even with only one binary entity enabled #139779

Closed
TexasFlyer opened this issue Mar 4, 2025 · 7 comments

Comments

@TexasFlyer
Copy link

The problem

After extensive testing, I found that the Starlink Integration was using about 40MB per hour or ~29GB per month. And that's after disabling every entity except for one binary sensor showing Obstructions. I could understand this amount of data if I had download speeds, etc enabled which update frequently, but they were all disabled. I'm guessing this is either a bug (ie, disabling in HA is not disabling in the Integration) or the Starlink HA Core is eating up a ton of data. Since I use Starlink for my data plan, using this integration with only a single binary entity would cost me about $360/year to use :-( I disabled, re-enabled, and disabled and the ~40MB data usage followed the Starlink Integration. Can you please look into this?

What version of Home Assistant Core has the issue?

System Information version | core-2025.2.5 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.13.1 os_name | Linux os_version | 6.6.73-haos arch | x86_64 timezone | America/Denver config_dir | /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 5000 Installed Version | 2.0.5 Stage | running Available Repositories | 1567 Downloaded Repositories | 18
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 14.2 -- | -- update_channel | stable supervisor_version | supervisor-2025.03.0 agent_version | 1.6.0 docker_version | 27.2.0 disk_total | 30.8 GB disk_used | 5.1 GB healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | oracle board | ova supervisor_api | ok version_api | ok installed_addons | Terminal & SSH (9.16.0), File editor (5.8.0)
Dashboards dashboards | 3 -- | -- resources | 12 views | 2 mode | storage
Network Configuration adapters | lo (disabled), enp0s3 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth419316f (disabled), veth014793c (disabled), veth685a239 (disabled), veth0303681 (disabled), vetha4cca0b (disabled), vetha53e8b7 (disabled), veth530165e (disabled) -- | -- ipv4_addresses | lo (127.0.0.1/8), enp0s3 (192.168.50.230/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth419316f (), veth014793c (), veth685a239 (), veth0303681 (), vetha4cca0b (), vetha53e8b7 (), veth530165e () ipv6_addresses | lo (::1/128), enp0s3 (fe80::8a1f:d4db:1928:41b8/64), docker0 (fe80::42:e0ff:fea1:e90d/64), hassio (fe80::42:64ff:fe50:3ab3/64), veth419316f (fe80::50d2:aaff:feee:5e4c/64), veth014793c (fe80::cc1e:2cff:fe0e:28cd/64), veth685a239 (fe80::48:e2ff:fef3:ac37/64), veth0303681 (fe80::3476:3fff:feb8:c8ae/64), vetha4cca0b (fe80::584c:3eff:fe0e:7d28/64), vetha53e8b7 (fe80::2489:49ff:fe61:bbfb/64), veth530165e (fe80::14c2:fff:fe64:db25/64) announce_addresses | 192.168.50.230, fe80::8a1f:d4db:1928:41b8
Recorder oldest_recorder_run | February 22, 2025 at 3:38 AM -- | -- current_recorder_run | March 3, 2025 at 1:15 PM estimated_db_size | 523.36 MiB database_engine | sqlite database_version | 3.47.1

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

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Mar 5, 2025

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)

@mib1185
Copy link
Contributor

mib1185 commented Mar 5, 2025

how exactly do you determine the data consumption of a single integration in HA?

@boswelja
Copy link
Contributor

boswelja commented Mar 5, 2025

Not sure what would be consuming actual data, we use https://github.com/sparky8512/starlink-grpc-tools which handles everything. From an integration perspective, we can't selectively include what data we want, so it is all or nothing.

How are you measuring this? You should only see traffic to and from your dishy, not beyond

@boswelja
Copy link
Contributor

boswelja commented Mar 5, 2025

@home-assistant add-label needs-more-information

@TexasFlyer
Copy link
Author

TexasFlyer commented Mar 5, 2025 via email

@boswelja
Copy link
Contributor

boswelja commented Mar 5, 2025

Your router sits between dishy and your home network. If you are pinging dishy, it will record that as "data transferred", but it's likely not actually pinging any remote hosts.

It would be more accurate to use dishys data monitoring, so that you get a measure of outgoing and incoming data, rather than traffic to and from dishy itself

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants