Downlink not getting an ack on the 470-510 band

ChirpStack Gateway Bridge
1

I have set up a US 915 server and a Chinese 470 server
My issue is i am not seeing ack to the downlink being sent on the 470 band

On the 915 i can see in the gateway bridge sending the downlink then an ack for that message

Aug 20 11:19:21 ip-172-31-28-195 US_GatewayBridge[27643]: time=“2020-08-20T11:19:21Z” level=info msg=“integration/mqtt: downlink frame received” downlink_id=98a8dbe7-6f2f-4968-88fc-30a2fed51eb7 gateway_id=GATEWAY ID

Aug 20 11:19:21 ip-172-31-28-195 US_GatewayBridge[27643]: time=“2020-08-20T11:19:21Z” level=info msg=“integration/mqtt: publishing event” downlink_id=98a8dbe7-6f2f-4968-88fc-30a2fed51eb7 event=ack qos=0 topic=us915/gateway/GATEWAY ID/event/ack

However on the 470 server i can see the down link but no ack

Aug 20 10:43:57 ip-172-31-28-195 CN_GatewayBridge[27643]: time=“2020-08-20T10:43:57Z” level=info msg=“integration/mqtt: downlink frame received” downlink_id=649c53bd-337b-4da0-b5d2-3459bd2ba93e gateway_id=GATEWAY ID

Should i be seeing an error here because it seems the downlink never gets an ack or is there something i have configured wrong for the 470 band ?

Update from the device log i can see the downlink reaching the device and the device acknowledging it. Is there some delay i have to configure on the loraserver to wait for this ack back up

2

The downlink ack (the ack sent by the gateway) comes from the packet-forwarder :slight_smile: If it does not send an ack, then things could still work. Only ChirpStack is missing the confirmation that the gateway transmitted the downlink.

3

@brocaar Is this an issue with the gateway or the server do you reckon For me not to see the unconfirmed data up ?
Also as you saw things still work only i am not seeing this unconfirmed data up at any time

I have however in the mean time tested using a very old version of the loraserver version 2.6 which i previously used and i can see this unconfirmeddatadown in the live lorawan frames and the correct logs in the gateway bridge

4

Is this an issue with the gateway or the server

It is something which the gateway needs to send to the NS.

I have however in the mean time tested using a very old version of the loraserver version 2.6 which i previously used and i can see this unconfirmeddatadown in the live lorawan frames and the correct logs in the gateway bridge

This is because in older versions, the NS made the assumption that the downlink was sent by the gateway. It did not wait for the ack.