Hi @Aathithan,
Sorry, I assumed you were using a Blues-branded gateway! No worries as we can still debug this:
-
We need to first confirm that your gateway is online and receiving uplink messages from the Notecard LoRa. As depicted in the image below, you should be able to verify that your Gateway is receiving uplink messages with a Join EUI of
6E 6F 74 65 63 61 72 64, which is the application identifier of the Blues Managed LoRaWAN application server. If you do not see the messages below, you need to confirm 1) That your Gateway is provisioned in your Things Network Account and online and 2) That your Notecard LoRa is on and a Product UID has been set as the Notecard will not attempt a sync without this. -
Once you have confirmed that your Gateway is online and uplink messages are being received, the next step is for you to configure Packet Broker. Those steps are listed in this document, and will differ depending on what type of account you have.
Note: In addition to Packet Broker being enabled, it is also important that the routing configuration is set to “Forward traffic to all networks registered in Packet Broker” as can be seen from the images below. -
Once packet broker is configured, you will need to manually trigger a
syncwith the Notecard LoRa, and it might even require a power-cycle, but after a few minutes, the LoRa Notecard should appear online in our Things Stack Tenant and traffic should flow to Notehub. If you still don’t see the device appear in Notehub after confirming all of the above, please let us know.
