Issues Connecting Dragino LHT65N

[Xavier_Lopez]

Hello All,
I am trying to connect a Dragino LHT65N to my Chirpstack server using a Tektelic Kona Micro gateway. The issue I have been running into is that the device successfully goes through the Join-Request and Join-Accept process, but never sends any uplink packets (I understand that the device will show a “Last Seen: Never” until it sends its first uplink packet) The expected behavior of the device is that it immediately sends an uplink packet after successfully joining and then sends an uplink packet every five minutes. I know this behavior works because on myDevices the device behaves as normal.

I’ve read that this issue usually boils down to three things:

• The device profile is configured wrong
• The region isn’t enabled in the Chirpstack.toml
• The Gateway Bridge / MQTT Forwarder is sending the wrong topic-prefixes

My gateway is configured to be on US915_0 and can successfully send MQTT topics between my gateway and the server. Also, here is my device profile for my LHT65N

Here is my chirpstack-mqtt-forwarder.toml file from the Kona Micro gateway as well as my config.json file.

Here is my docker-compose.yml file and my chirpstack.toml file

When I perform a

tail -f -n 100 /var/log/messages |grep chirpstack-mqtt-forwarder

command on my Kona Micro and observe the moment I connect my LHT65N to my gateway and it successfully joins, this is what I see.

As well as the logs from Docker

At this point, I am very lost on how to show successful uplink packets on the device. If I change the Region Configuration on Device Profiles to US915_1 (while the gateway is on US915_0), then a Join-Accept never happens, only a Join-Request. If I change the docker-compose.yml file and the chirpstack-mqtt-forwarder.toml file to publish a US915_1 topic as well as the device profile to US915_1 then I’ll get a Join-Accept, but still no uplink packets. If there are any more configuration files that I need to send, please let me know. Thank you for your time and help.

[Liam_Philipp]

@Xavier_Lopez

I’ve read that this issue usually boils down to three things:

• The device profile is configured wrong
• The region isn’t enabled in the Chirpstack.toml
• The Gateway Bridge / MQTT Forwarder is sending the wrong topic-prefixes

Must’ve been some wise man who said this

But there’s actually one missing here: band mismatch between device/gateway/server.

Maybe these are just photos from different time points, but your server and MQTT forwarder are configured for us915_0 while you gateway channel card is configured for 903.9MHz - 904.6MHz which is us915_1. Could that be your issue?

[Xavier_Lopez]

Those pictures are from different time points, but nothing really changed in between when the pictures were taken. Thank you for the advice.

I do recall changing my server and MQTT forwarder to us915_1 and getting the exact same effect as I did on us915_0 where it would do the Join-Accept then never send an uplink. I totally didn’t think of to look at the config to see that my GW was on us915_1 because I have pretty much exclusively worked on us915_0 devices. I’ll try it again when I get to the office in the morning. To my knowledge (I do NOT have a UART cable to verify) the LHT65N is transmitting at us915_1 so I would have initially thought if they were the same it would’ve worked, but that made me surprised it didn’t. Thank you for your advice though, I’ll make sure to try it in the morning.

[dtuando]

I had this same device same issues. chagning the mqtt forwarder to us915_1 fixed it.

where can i find more information about the us915_0 and us915_1.