Just got an email from Starlink saying “We are updating how location data is accessed on Starlink terminals. Effective May 20, dish location will no longer be available via the local device gRPC API.”
Will this affect Pepwave getting GPS location data from a Starlink?
Weird. I haven’t received the email yet. Might it be plan specific? Or terminal specific? Is there more than one way to extract the location data from a Starlink terminal?
I have the “Standard v4” terminal and a residential plan if it matters.
That’s just it. Starlink says they’re “updating how location data is accessed”, and that it “will no longer be available via the local device gRPC API.”
They didn’t say they’re removing access, and the way they phrased it leaves room that they might be “updating” with a different method of getting it. Figured since Peplink is a “Starlink Authorized Technology Provider”, someone here may know more about it.
I use the Starlink GPS, but I only use it as a secondary source. It’s more reliable to use the Peplink GPS antenna, especially when you pair the Starlink with a mobile SIM for backup WAN.
If no dedicated GPS on the device why not try a network GPS.
Devices like the B One 5G appear to have this capability…
Doing this for devices that don’t have a GPS. Eg wireless Mesh Devices that don’t have GPS which is essential. for mobile. network RF mapping…
Here I’ve run up a Pi with USB GPS and configured an onboard GPS server using a simple Node Red implementation - serial in (GPS) - TCP out (listen on port 10110)
I then point the device without GPS to the RPi IP address on port 10110 and the device pulls the GPS location.
GPS is a Ublox 7 magbase mouse cheap n nasty for like $10-$20…
Just ran this config on my B One 5G…
In InControl I edited my previous starlink obtained position so it reflected a location 100km away… Hit save changes and it slewed back to the Pi GPS location… So a simple albeit clunky way of providing GPS location to my router…
That’s amazing that they would build a Mini that didn’t have a GPS port. I’m not sure what Peplink was thinking on that, especially for a device that is specifically designed for mass deployment on mobile applications. I had no idea.