Gateways locations information in the payload header

Gateways
21

Take a look in the Raw Payload that it is coming from TTN to the TagoIO. My point is that in the “gateway_ids” I just can see one of my two gateways (RAK7249 and RAK7258).

Maybe I am wrong but I was expecting to see both gateways. Is it correct?

image
image1920×1080 353 KB 

{
        "variable": "ttn_payload_v3",
        "value": "{\"end_device_ids\":{\"dev_eui\":\"AC1F09FFFE08E7AF\",
										\"device_id\":\"eui-ac1f09fffe08e7af\",
										\"application_ids\":{\"application_id\":\"rakwireless-field-tester\"},
					\"join_eui\":\"AC1F09FFF9150701\",
					\"dev_addr\":\"260BED93\"},
					\"uplink_message\":{\"frm_payload\":\"0D8MnssBBBYLCQ==\",
										\"f_port\":1,
										\"f_cnt\":2793,
										\"session_key_id\":\"AYb+daPeaUVdGsjZkawKGQ==\",
										\"rx_metadata\":[{\"gateway_ids\":{\"gateway_id\":\"brrjnasondasgw01\",
																		   \"eui\":\"60C5A8FFFE74D380\"},
															                \"time\":\"2023-03-20T21:48:56.559190034Z\",
															\"timestamp\":2370786211,
															\"rssi\":-12,
															\"channel_rssi\":-12,
															\"snr\":8.75,
															\"location\":{\"latitude\":-22.998018054874855,
																		  \"longitude\":-43.38812005529691,
																		  \"altitude\":5,
																		  \"source\":\"SOURCE_REGISTRY\"},
															 \"uplink_token\":\"Ch4KHAoQYnJyam5hc29uZGFzZ3cwMRIIYMWo//5004AQo6e96ggaCwjJqeOgBhC0lqcVILjp+u7//Bc=\",
															 \"received_at\":\"2023-03-20T21:48:56.945147562Z\"}],
										\"settings\":{\"data_rate\":{\"lora\":{\"bandwidth\":125000,
																			   \"spreading_factor\":7,
																			   \"coding_rate\":\"4/5\"}},
													  \"frequency\":\"915800000\",
													  \"timestamp\":2370786211,
													  \"time\":\"2023-03-20T21:48:56.559190034Z\"},
										\"received_at\":\"2023-03-20T21:48:57.045688303Z\",
										\"confirmed\":true,
										\"consumed_airtime\":\"0.061696s\",
										\"locations\":{\"frm-payload\":{\"latitude\":-22.9978493,
																		\"longitude\":-43.3880212,
																		\"altitude\":26,
																		\"source\":\"SOURCE_GPS\"}},
										\"network_ids\":{\"net_id\":\"000013\",
														 \"tenant_id\":\"ttn\",
														 \"cluster_id\":\"eu1\",
										\"cluster_address\":\"eu1.cloud.thethings.network\"}},
					\"correlation_ids\":[\"as:up:01GW0FYCH621SCR0GMK9KSW3CW\",
										 \"gs:conn:01GVXBC8B0QFV2NPXRAPDVGQA1\",
										 \"gs:up:host:01GVXBC8B8F09AXT49NENTJ3QQ\",
										 \"gs:uplink:01GW0FYCAMH9CVH4K5KBG5267Y\",
										 \"ns:uplink:01GW0FYCANERHAW7GD81CTJ48Y\",
										 \"rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01GW0FYCAN3XRDCD33256TH4KE\",
										 \"rpc:/ttn.lorawan.v3.NsAs/HandleUplink:01GW0FYCH57Y0DDFKER059PXSW\"],
					\"received_at\":\"2023-03-20T21:48:57.254112409Z\"}",
        "group": "1679348937325"
    }
22

You are wrong, sorry for been so blunt, we have dealt more times than you had breakfast with this issue, and it is 99% chance this is the issue.

Follow the advise on the RSSI, then we can look and see if anything else is wrong. (this is for your equipment sake)

And by having very fast browse, your one gateway ID is brrjnasondasgw01, may I ask the other gateways ID? As I don’t pick up one in the close vicinity (except if its location is not set, then I will not pick it up)

23

Can you also please dial back on those messages? On every 15 sec you are exceeding the FUP. You are only aloud for total uplink time per day 30sec.

“consumed_airtime”:“0.061696s” x 5760 messages per day = 355,36896 sec per day

Your gateway “rxRate”:240.90814 per hour, equites to a message every 15 sec

24

Looking at the console screen shot that clearly has another gateway in the meta data but is not on view and taking the description of:

and the change in format of the JSON in the quoted message, perhaps the issue isn’t that both gateways aren’t appearing in the meta data (hard to tell without seeing the entire of the console event details) but that the original opening description was referring to the data as it appears in TagoIO.

As this has only just come to light and because the device is hammering TTN way beyond anything reasonable for the Fair Use Policy, I’m closing this thread because it has, as a notable Python would say, got silly.

@claudiormrosa, can you look at how you originally presented the information, what we asked you to try that as yet hasn’t been actioned, read up on the Fair Use Policy and look at the entire of the device JSON. It is still not clear to us if both gateways are on TTN, if only one is, then you should only expect to see data for one.

If it transpires that both gateways are on TTN and being heard as seen in the device meta data, you’ll have to take up the issue about why they only keep the first gateway entry with TagoIO. This is a common JSON processing error - device health & mapping is all about having more than one gateway hearing a device.

After you have reduced uplink interval inline with FUP and the RSSI to a reasonable level as detailed above, if you are still only getting one gateway entry in the TTS meta data, then please open a new fresh topic with a more considered description, copy & paste text carefully formatted, only use screen shots when you can’t, show both gateway logs, both gateway console entries, the device console JSON and the TagoIO JSON for the same point in time - this takes a few minutes to setup the browser windows but if your device is only uplinking every 3 minutes, you will have about 90 minutes to capture all the information before it all scrolls off the end.

1 Like