starlink-grpc-tools VS Mosh

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 haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.