Gateway never seen using Raspberry Pi

ChirpStack Gateway OS
1

Hi,
I am using Cirpstack v4
I have installed Chirpstack at Raspberry Pi. Now the issue is, it is not appearing to be seen at Chirpstack > gateways.
Also my applications (End Device).
Please anyone help me in this?

2

Have you found any solution ?

3

Not yet.
My issue is, gateway is not showing last seen. Same for application devices.

4

Have you installed chirpstack-gateway-bridge and opened port UDP/1700?

Or are you using ChirpStack MQTT forwarder?

5

Thanks for your response.
Let me tell you the steps I am following:

  1. First of all, this is the url Introduction - ChirpStack open-source LoRaWAN® Network Server documentation I downloaded Full Image for Raspberry Pi 4B.
  2. I downloaded Full Image and make a bootable sd card using Balena Ethcer.
  3. After that I restarted my Raspberry Pi and it starts work with Chirpstack.
  4. Then I opened my Raspberry Pi’s ip (http://GATEWAY-IP-ADDRESS) at browser and it shows me Chirpstack interface.
  5. There I clicked on Chirpstack > Concentrated > SX1302/SX1303 (I have SX1302) and choose Shield model as Waveshare Lorawan Hat (Gateway I have) and choose it’s Channel as 8. (I don’t know that I need to click on GNSS and USB or not.)
  6. In Chirpstack > UDP Forwarder I set my http://GATEWAY-IP-ADDRESS/ and port remain at 1700.
  7. After that I opened http://GATEWAY-IP-ADDRESS:8080 and then I added my devices in it.

Please let me know if I am doing something wrong there.

6

Step 6 & 7 are not required. If your Concentratord configuration is correct, then you should see the Gateway ID in the footer of the web-interface. Do you see that?

7

Yes, I see that Gateway Id at footer. But at http://GATEWAY-IP-ADDRESS:8080 i did not see frames.

8

Ok, then at least the Concentratord is properly communicating with your shield. Then probably what is missing is configuring the correct channel-plan.

As well, please inspect the LoRaWAN frames received by your gateway in the ChirpStack interface. If you see the uplinks there, but not on the device page in the web-interface, then you probably misconfigured your device.