-
-
Notifications
You must be signed in to change notification settings - Fork 380
Open
Description
The issue we are experiencing is that the downlink is never sent to the end-device, and this seems to occur on ChirpStack V4 only. Our setup includes a gateway running the UDP packet forwarder and the packet multiplexer. The packet multiplex configuration links two ChirpStack servers: one is V4 and the other is V3. On the V3 server, the downlink works fine, although a few downlink packets may be lost occasionally. However, on the V4 server, all the downlinks we created in the Enqueue list are completely ignored, even though the V4 server is still receiving uplinks.
we disabled the frame-counter validation since end device is ABP:

and this is the EU868 device profile:


and here is the chirpstack-multiplexer config:
[general]
# Log level
#
# debug=5, info=4, warning=3, error=2, fatal=1, panic=0
log_level=5
[packet_multiplexer]
# Bind
#
# The interface:port on which the packet-multiplexer will bind for receiving
# data from the packet-forwarder (UDP data).
bind="0.0.0.0:1700"
# Backends
#
# The backends to which the packet-multiplexer will forward the
# packet-forwarder UDP data.
#
# Example:
[[packet_multiplexer.backend]]
# Chirpstack V4 on rpi
host="10.2.13.28:1700"
uplink_only=false
gateway_ids=[
"E45F01FFFEB94911"
]
# Chirpstack V4 on rpi
[[packet_multiplexer.backend]]
host="10.2.13.31:1700"
uplink_only=false
gateway_ids = [
"E45F01FFFEB94911"
]
Metadata
Metadata
Assignees
Labels
No labels
