What is the ACK mechanism of the "confirm" message in ChirpStack? Why is my LoRaWAN gateway very close to my LoRaWAN node, with an RSI of around -50, and why did the server still return "unconfirm" when I sent the "confirm" message to it? I don't understand this. Logically speaking, this shouldn't happen.
1 Answers
Can the LoRaWAN data frame be expanded, one field is used to indicate Confirmed or Unconfirmed.
Related
SQLite backend: join requests and DeviceService.Create fail with "database is locked" (busy_timeout not applied to read-then-write transactions)
1 answers
Device Profile: Supported data-rates and ADR
2 answers
v4.11.1 – Device Profiles page fails: "Error deserializing field 'relay_cad_periodicity': Received more than 2 bytes while decoding an i16"
1 answers
Feature suggestion : show ack=true a different color
ADR never sends LinkADRReq despite good SNR margin (stuck at DR0/SF12 for months) - ChirpStack v4.16.2
2 answers
The device data rate dropped significantly 4.18 to 4.19.1