Unable to join from Heltec ESP32 LoRa V2. (TTN Working)

Hi everyone,

I managed to set up a test node and gateway forwarding to and from TTN. I then installed Chirpstack v3 (and later V4) on a local RPi and can see the join request (see screenshot). The Heltec ESP never seems to receive the accept though.

Gateway is a Mikrotik LR8 and the Heltec is using a test sketch from the MCCI LMIC library. OTTA keys are being produced by Chirpstack.

I know this topic has been mentioned a few times. Is there any obvious reason why TTN should work and Chirpstack not?

Any help gratefully received.

Have you checked the events tab of the device? Does it contain any log information?

Hi, thanks for the reply. This is the output from the events tab:

Please let me know if you need any further information.

BTW, this if the Activation tab:

I’m experiencing the same issue. If there is any information to solve this i’d like to know.

Could it be that the gateway never acknowledged the downlink transmission? In this case ChirpStack does not show the downlink as it doesn’t know if it was sent using RX1 or RX2 parameters.

Things to look into:

MQTT message logs, you should see something like:

  • eu868/gateway/…/event/up
  • eu868/gateway/…/command/down
  • eu868/gateway/…/event/ack

As well you might want to look into the ChirpStack server logs.

Thanks.

This is the output of mosquitto:

1669915913: fbfb179aa7e052a6 0 eu868/gateway/+/event/+
1669915913: Sending SUBACK to fbfb179aa7e052a6
1669915913: Received SUBSCRIBE from b1cf0323dab646f8
1669915913: application/+/device/+/command/+ (QoS 0)
1669915913: b1cf0323dab646f8 0 application/+/device/+/command/+
1669915913: Sending SUBACK to b1cf0323dab646f8
1669915913: Received SUBSCRIBE from 407ba7a9875b9685
1669915913: eu433/gateway/+/event/+ (QoS 0)
1669915913: 407ba7a9875b9685 0 eu433/gateway/+/event/+
1669915913: Sending SUBACK to 407ba7a9875b9685
1669915924: Received PUBLISH from auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/stats’, … (29 bytes))
1669915924: Sending PUBLISH to fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/stats’, … (29 bytes))
1669915944: Received PINGREQ from b1cf0323dab646f8
1669915944: Sending PINGRESP to b1cf0323dab646f8
1669915944: Received PINGREQ from fbfb179aa7e052a6
1669915944: Sending PINGRESP to fbfb179aa7e052a6
1669915944: Received PINGREQ from 407ba7a9875b9685
1669915944: Sending PINGRESP to 407ba7a9875b9685
1669915947: Received PINGREQ from auto-CEB97979-4677-A3C6-0631-5054FD7A3E19
1669915947: Sending PINGRESP to auto-CEB97979-4677-A3C6-0631-5054FD7A3E19
1669915954: Received PUBLISH from auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/stats’, … (27 bytes))
1669915954: Sending PUBLISH to fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/stats’, … (27 bytes))
1669915961: Received PUBLISH from auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/up’, … (107 bytes))
1669915961: Sending PUBLISH to fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/up’, … (107 bytes))
1669915961: Received PUBLISH from fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/command/down’, … (278 bytes))
1669915961: Sending PUBLISH to auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/command/down’, … (278 bytes))
1669915961: Received PUBLISH from b1cf0323dab646f8 (d0, q0, r0, m0, ‘application/e65da3f7-f29f-40f7-b4c2-53f6130f4089/device/70b3d57ed0057458/event/join’, … (438 bytes))
1669915974: Received PINGREQ from 407ba7a9875b9685
1669915974: Sending PINGRESP to 407ba7a9875b9685
1669915977: Received PINGREQ from b1cf0323dab646f8
1669915977: Sending PINGRESP to b1cf0323dab646f8
1669915982: Received PUBLISH from auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/up’, … (108 bytes))
1669915982: Sending PUBLISH to fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/up’, … (108 bytes))
1669915982: Received PUBLISH from fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/command/down’, … (278 bytes))
1669915982: Sending PUBLISH to auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/command/down’, … (278 bytes))
1669915982: Received PUBLISH from b1cf0323dab646f8 (d0, q0, r0, m0, ‘application/e65da3f7-f29f-40f7-b4c2-53f6130f4089/device/70b3d57ed0057458/event/join’, … (438 bytes))
1669915984: Received PUBLISH from auto-CEB97979-4677-A3C6-0631-5054FD7A3E19 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/stats’, … (83 bytes))
1669915984: Sending PUBLISH to fbfb179aa7e052a6 (d0, q0, r0, m0, ‘eu868/gateway/50313953331b4750/event/stats’, … (83 bytes))

Does this help?

Andy

After that down command, an eu868/gateway/50313953331b4750/event/ack is expected but I do not see it in your logs.

Without this ack (note that this is the gateway acknowledgement that the downlink was successfully enqueued, it is not related to confirmed downlink), ChirpStack considers the downlink to be unsent.

That feels like we’re making progress at least. The obvious question is then, why does the setup work with TTN and not with Chirpstack? I just switched over to TTN to test again and the join worked immediately. Could Mosquitto be causing the problem?

There seem to be very few parameters to choose when defining the server on the Mikrotik gateway.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.