internet-pi VS starlink-grpc-tools

I use this to monitor my internet connection, it's originally designed for a raspberry pi but it will run on any Linux machine thanks to docker https://github.com/geerlingguy/internet-pi

For example, you’re probably receiving bad service from your provider. Run fast.com and post the results (run the “show more info” option). You may also consider running ongoing monitoring to compare over time. I use this app on a Raspberry Pi: https://github.com/geerlingguy/internet-pi

i am having issue with when i am using my rpi4 (where pihole is installed) as my DNS server, it shows only my ISP's DNS on the clients side when i checked it with websites like https://www.top10vpn.com/tools/what-is-my-dns-server/. Where in my pihole settings, i set it to be using DNS's google, in the query log i can see the status shows that is answered by google#53 . but when i change my client's DNS server directly to google DNS, it shows both my ISP's DNS and Google DNS on the DNS checker website. i followed the link here to install pihole https://github.com/geerlingguy/internet-pi , which i believe is installing pihole and grafana inside a docker. Above also attached some screenshots from my pihole GUI.

hi there i forgot to tell u that i might be installing the pihole inside a docker, i followed the steps here https://github.com/geerlingguy/internet-pi . when i use "dig" command on my client terminal it shows the DNS ip address "127.0.0.1" is this what might be affecting my DNS config?

https://github.com/sparky8512/starlink-grpc-tools - Cant seem to get this to work with docker-compose and influxdb2.8

I'm guessing you've already looked at the debug in the SL app. This is a good reference on what the debug lines mean. https://github.com/sparky8512/starlink-grpc-tools/blob/main/starlink_grpc.py

If you want to get really detailed there's a gRPC endpoint in Dishy with a whole lot of debug data you can look at. See these dashboards for instance. I set all this up a long while back but stopped using it, partly because it's not easy and partly because a Ubiquiti bug makes it hard for me to get at the data.

BoresightAzimuth&Elevation in the debug data are not virtual. That's where your dish points physically. I was told in the beginning (2020 - early 2021) dish shared via grpc the serving satellite number and it showed if the connection was prescheduled or fallback but they hid that api from public access. The only way to see what satellites dish connects to is to observe obstruction map filling up after a cold start. The dish doesn't know about obstructions after a cold start though.

You can use Starlink's API to pull data and statistics, you can find some tools at https://github.com/sparky8512/starlink-grpc-tools/

I found a good one on GitHub. https://github.com/sparky8512/starlink-grpc-tools/blob/main/starlink_grpc.py

Have a look at https://github.com/sparky8512/starlink-grpc-tools