When I run gateway-config on my gateway and choose “Edit packet forwarder config”, it references the file located at /opt/ttn-gateway/packet_forwarder/lora_pkt_fwd/global_conf.json. When I view the contents of that file there is a section at the bottom that has a couple of URLs in it. That section is as follows.
Is that the referenced URL to which you are referring? The examples seemed to indicate that the URL is from a node configuration. I don’t have that set up yet.
This is bizarre. These are my coordinates, but not my EUI. Not sure how that happened.
{“eui-b827ebfffee6cbe6”:{“id”:“eui-b827ebfffee6cbe6”,“location”:{“latitude”:41.56465148925781,“longitude”:-90.51200103759766,“altitude”:206},“country_code”:“us”,“attributes”:{“brand”:“Raspberry Pi based”,“frequency_plan”:“US_902_928”},“last_seen”:“2020-07-20T14:52:32Z”}}
Hmmm, the one in your conf file returns no info on the gateway-data url but there is that other one in the database for your location. Clearly the server has had a ‘moment’.
I think we need to get @arjanvanb to page the back room wizards to de-borf the entries so you can try again with a clean slate.
Beware: we cannot be sure that eui-b827ebfffee6cbe6 is not someone else’s, especially as it’s clearly connected. But eui-b827ebfffeb39eb3 surely seems to be in some troubled state within TTN.
Did you restart the gateway recently? Does the 6cbe6 one go offline when you switch off yours? (Aside: its coordinates and altitude seem to be changing a bit over time, suggesting a GPS.)
Those GPS coordinates point to my house. That is one heck of a coincidence. I think I would know if someone was breaking into my house and setting up a TTN gateway. I will power mine down to see if that change is reflected in the console. Thank you!
Now I have the power - if you’ve got a cheat sheet on the URLs you use for diagnosis, it would save me trawling through previous posts to make sure I’ve got them all!
Whilst it fills me with a random range of uncomfortableness but given that the EUI is generated from the Pi’s MAC address so isn’t a “real” one and if you change Pi, it won’t change in the config, let’s try changing your EUI on the device to the one that TTN thinks you have.
Or, if you have the patience, re-install the whole gateway just in case you have multiple Pi’s and we have some re-generation of the EUI issue going on.
@descartes@arjanvanb I powered the device back on. Then I updated the global configuration and restarted the packet forwarder. I noticed the device started updating again. I then went to register a gateway with b827ebfffee6cbe6 as the EUI and this time it accepted it without issue. The gateway is now showing up in the console with EUI of b827ebfffee6cbe6 and it shows as connected. I also still have the old not connected gateway too. I figure I will just leave that one in case it somehow one day magically reverts to that value. I believe I do have both Ethernet and WiFi configured on that pi. I didn’t realize the EUI was based on the interface’s MAC address. I am betting that is how I got one EUI registered and another one that was actually working based on how traffic was routed. Thank you both for all of your help! I guess I am going to move on to configuring my node and learning how to use the MQTT API. Thank you again, it is much appreciated!
Yes, you’re showing info. But the following, using the undocumented status (which can often be used when TTN Console shows gateways as being disconnected), still fail for me:
Ah, I see. I misread your command the first time. I am also getting failed when I run the status command. Does the status command require that ports are forwarded or anything like that for the gateway to respond? I don’t have any of that setup at this time. Thank you.