Hey everyone,
Thanks for the replies.
@Jeff-UK I tried putting some distance between my device and the gateway, moving the gateway to a lab down the hall and putting about two wall’s worth of distance between. I also tried removing the antennas from both the gateway and the device, running several tests with the device or gateway or both antennas removed and also trying in both short range (on my desk) and long range (lab mentioned above) conditions. I saw no changes or traffic on my gateway.
As of right now, this is the only traffic I’ve seen on my gateway. No traffic is being observed or sent back to the device. Does this mean that the OTAA request being sent out by the device isn’t being received at all? That is that in the link:
Device sends OTAA -> OTAA Request received by gateway -> Gateway links device and sends (something?) back to device to acknowledge
That this process is getting stopped at the first step?
@kersing I’m in the process of ordering a Things Uno and a RAK-7201 to try and test another device on the gateway. I’m using The Things Kickstarter Gateway for this project. You may be right that its a gateway issue.
One thing I also ran across in another forum Migration Procedure | V2 to V3 Update | V3 Steps was the following line:
Create a new application on the v3 stack.
Create an incoming MQTT endpoint wired to the v3 stack for data ingestion into your system.
Start creating new devices on the v3 stack.
This is something I haven’t done, but also haven’t seen any documentation for. Is this specifically a V2 issue, or is there a link to a thread for how to do this? I haven’t been able to find anymore information. I know this is a community forum and I’ve really tried to find my answers on my own, so I hope its not some simple thread I’ve missed, but I do really appreciate the help from all TTN volunteers.