Hello,

Following our previous communication in ticket #116453 - resolved by enabling TLS SNI. 

We are now working on implementing Network Geolocation for our end-devices via our gateways.

Currently, we are facing an issue where we do not receive any coordinates (location data) from the devices in the ThingPark console.

System Configuration Details:

1. Gateway: Jooby Outdoor Gateway LoRaWAN 400 EU

Platform: ThingPark Community

Model: Generic Basics Station packet forwarder (EU868)

LRR-UUID: 0016C0-001A79FFFE3F410C

Software: Basics Station 2.0.6 (mbedTLS 2.28.0)

Built with options: make platform=corecell variant=std

Status: GPS is ON, PPS is ON, Fine Timestamping is Supported and active(SX1303).

2. End-devices: Jooby Ephir RMS 100 EU

LoRaWAN Version: 1.0.2 revB (Class A)

Activation: OTAA with local Join Server

Location Mode: Network geolocation (TDOA/RSSID) enabled in ThingPark settings.

Issue description:

Both the gateway and devices are successfully connected and transmitting data. However, the metadata for the uplink packets does not seem to trigger the geolocation solver, and no coordinates are appearing in the device's location tab.

We would appreciate your guidance on the following:

Are there any specific server-side settings or parameters in ThingPark Community required to activate the geolocation solver for "Generic" models?

Does the "Network Geolocation" feature in the Community version support TDOA (Fine Timestamp) from this specific gateway model?

Is it possible/recommended to use the classic Semtech UDP Packet Forwarder instead of Basics Station to connect to ThingPark Community for better geolocation compatibility?

Looking forward to your recommendations.

Best regards.