After noticing that the Liverpool community had no gateways listed, but not really understanding what had happened, the Leeds and Bradford community pointed out that the lat and lon settings were transposed and placed the Liverpool community over towards the Seychelles!
But the reason that I didn't see this straight away, was the communities page and the gateways array information in the MQTT messages seemed to be coming from different sources. The mis-placed gateway had the location set incorrectly in the packet forwarder local_conf.json, but set correctly in the gateways console.
This meant that:
- MQTT messages through the gateway had the lat/lon taken from the gateways console settings,
- gateway locations in the communities page were taken from the gateway fake gps report.
Is this part of removing reliance on the fake gps figures for gps-less gateways?
