No GPS in Metadata but GPS set in Location of the gateway

9

Privacy settings of the gateway in the TTN console.

10

Thank you for your answhere.
Is this correct?
image

11

Go to the settings, privacy and set location to private,

12

Why privat? then nobody see the location?!

13

And the location will not be sent in the metadata of packets… Wasn’t that what you are looking for?

14

I wisht that the location is in the data that are send.

15

I will see the gateway in ttntracker.

16

I have the same problem. Location ist set on the TTN console and privacy is set to public but

wget -O - http://noc.thethingsnetwork.org:8085/api/v2/gateways/eui-58a0cbfffe800f38

shows

“location”:{}

17

I also have the same problem. All privacy settings are pubic.

http://noc.thethingsnetwork.org:8085/api/v2/gateways/eui-58a0cbfffe80101b

timestamp “2019-09-04T16:23:58.609642718Z”
uplink “262”
downlink “262”
location {}
frequency_plan “EU_863_870”
gps {}
time “1567614238609642718”
rx_ok 262
tx_in 262

Why?

18

This seems to be a serious firmware bug. See my current postings.

19

I have the same “issue”.
Gateway location is set in TTN and privacy marked as ‘public’.
And no location information in packet metadata.
Gateway I use is Laird RG186 and it has no internal options for location.

20

I have the same issue

21

Hello,

My TTIG gateway doesn’t report latitude and logitude too.
All my settings are public. I will follow this thread if a solution is found.

Thx,

22

I have the same issue
Gateway = Mikrotik wAP lora8

23

Same issue here… but only since 10 Feb 2020 13h00. Before the location metadata has been sent.
Gateway: LorixOne

24

Same Problem with Mikrotik Gateway.

1 Like
25

Same here, RAK831

26

Same here with indoor TTN gateway from RS components / Gemtek.

1 Like
27

This probleem occurs random over time and type of gateway connectivity (Semtch UDP, MQTT, Basic station). I even see difference per API over which I query data. Ttnctl ptesents different information on opennetwork server and eu. This nondeterministic behaviour is characteristic for the state in which TTN public network is at this moment.

2 Likes
28

I have got the same problem with the TTN indoor gateway. But I think there is a workaround by searching the gateway id at TTN.
arjanvanb explained it here: Determine which gateway is used by a given node
So you put the gateway-id in the url and get all JSON data including the position. Example: https://www.thethingsnetwork.org/gateway-data/gateway/eui-0000024b080606d8
https://www.thethingsnetwork.org/gateway-data/gateway/YOUR-GATEWAY-ID