FiPy: could not handle packet: gateway: unknown packet type: PullACK

ChirpStack Gateway Bridge
#1

I am using pycom.

I got a fipy running nano gateway and lopy as node.

I get connected and I can receive messages on my mqtt rx channel.

But when I try so send message back to node I have estrange behavior.

Some times I get the message (1 of 10) and other times I get ACK on mqtt ack channel but no message arrive to node.

In bridge log I see this:

Mar 20 16:14:54 loraserver.dmz.redcumbre.cl lora-gateway-bridge[30749]: time=“2019-03-20T16:14:54-03:00” level=info msg=“backend: downlink packet received” topic=gateway/30aea4fffe7907ec/tx

Mar 20 16:14:54 loraserver.dmz.redcumbre.cl lora-gateway-bridge[30749]: time=“2019-03-20T16:14:54-03:00” level=error msg=“gateway: could not handle packet: gateway: unknown packet type: PullACK” addr=“10.0.51.115:49154” data_base64=“AutmBDCupP/+eQfseyJ0eHBrX2FjayI6IHsiZXJyb3IiOiAiTk9ORSJ9fQ==”

Pycom nano-gateway packet-forwarde issue
#2

This looks like an issue with the nano gateway packet-forwarder not implementing the UDP protocol properly.

#3

Hello Brocaar. I like to add that with TTN work no problems. using I’m using the legacy packet forwarder

Any idea?

#4

Any help you can give me?
Any idea to affront this problem.

Nanogateway work no problem with TTN in legacy mode

#5

I test Pycom nano-gateway with TTN using the legacy packet forwarder and work TX and RX.

With loraserver only TX message are send RX message drop 90% of messages.

I see on console this log:
In bridge log I see this:

Mar 20 16:14:54 loraserver.dmz.redcumbre.cl lora-gateway-bridge[30749]: time=“2019-03-20T16:14:54-03:00” level=info msg=“backend: downlink packet received” topic=gateway/30aea4fffe7907ec/tx

Mar 20 16:14:54 loraserver.dmz.redcumbre.cl lora-gateway-bridge[30749]: time=“2019-03-20T16:14:54-03:00” level=error msg=“gateway: could not handle packet: gateway: unknown packet type: PullACK” addr=“10.0.51.115:49154” data_base64=“AutmBDCupP/+eQfseyJ0eHBrX2FjayI6IHsiZXJyb3IiOiAiTk9ORSJ9fQ==”

#6

I don’t own that gateway so can’t be sure, but maybe this could help you: https://forum.pycom.io/topic/2812/nanogateway-downlink-problems-ttn-and-loraserver/2.

#7

This is probably nothing more than an annoyance - that base64 decodes to a tx ack, which should be ignorable.

Whatever your actual problem is, it is not this. This is merely noise in the logs.

#8

I got the same error in the log at gateway bridge. For me after changing the packet type from PULLACK to TXACK in packet forwarder solved the problem.