starlink-grpc-tools VS starlink-cli

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

If you're still digging into that, this might help: https://github.com/starlink-community/starlink-cli They figured out a lot of stuff, but sadly not raw gps data which I'm interested in 🤣

The router service serves up the "extra" ping stats such as CS:Go ping times, here's a tool to poll these: https://github.com/starlink-community/starlink-cli

This is because those stats are exposed from the grpc API on the wifi router, not dishy. Since you are not using the router, that API is not available to the web interface to use. This command line client demonstrates what I mean.