starlink_grpc documentation doesn't appear to match get_status response about starlink-grpc-tools HOT 2 CLOSED

The documentation strings in starlink_grpc.py don't directly document the raw grpc structure, they document the cooked values returned by the status_data function (and similar). That being said, for status data, it's mostly just passing along what is in the raw data and just formatting it a little differently.

I don't believe there is much, if any, difference between the square and round (which I have) residential service dishes with respect to data returned via grpc, but there have been some changes over the past year, or so, that I have not incorporated. As far as I know, only 2 items (snr and seconds_obstructed) have been removed from status, and those are marked obsolete in the docs. The other items that don't show up in the get_status output are probably just reporting default values. grpc allows for default values for a type (usually something like 0 or false) to be omitted from the wire protocol and grpcurl won't show them in its output. For example, fractionObstructed doesn't show up in your get_status output because you have no obstructions reported, as evident from the wedge data.

If someone requests addition of some of the newer items (gps_stats and later in the above, as well as a few others that don't show up), I will add them, but I don't even know what some of them mean. The ones where the meaning is obvious don't seem all that useful to me to track over time, but then again, I don't track status myself, so that's not saying much.

from starlink-grpc-tools.

Ah I see, seems like I was also calling get_status rather than status_data which explains a lot of my problems 😆
Thanks for your help! I'll close this for now

from starlink-grpc-tools.