You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A little late, but I was running into this error and for a while couldn't understand what was going wrong. In my case, I found that the Heltec example code defaults to the first sub band for US915, which is 902.3 - 903.7MHz and on channels 0-7. The arduino code shows:
A lot of gateways default to the second sub band which is used by TTN. That is why your gateway might receive a request, because it is listening, not necessarily "connecting" to a device, send an accept, but the accept is out of scope for the node to receive back. At least that's my understanding, probably not fully correct. To fix this, you can either change your gateway to sub band 1, or the code to support subband 2, or whatever sub band you are using.
I'm attempting to join an HTCC-AB01 Cubecell node to a private gateway. I've successfully joined a Heltec esp32 to this gateway.
With the CubeCell device I'm unable to successfully join (according to the node) and send an uplink packet. Below is the output from serial:
On my gateway I see successful joins:
In AWS IoT Core, I see successful joins too:
Why am I seeing successful joins on the gateway and LNS, but not the device?
The text was updated successfully, but these errors were encountered: