Hello, i have a Vicki from MClimate und the rx1 in cs is confied to 5s.
If i send a downlink directly (10ms or somemthing) after uplink fom device, to cs => The downlink is in the Queue till next uplink.
why cs dont send the downlink (there are 5s).
Is there something i missed?
Edit:
I was able to further narrow down the problem.
If there is already something in the queue, then any new data sent after the uplink is also sent directly to the device as a downlink.
If there is nothing in the queue at the time of the uplink, it seems that the RX1 window for sending is not opened at all; instead, the whole thing is postponed to the next cycle.
Is it possible to schedule the check to determine whether there is something in the queue at the time of the RX1 window and not at the time of the uplink?
We have an application that sends a downlink to cs exactly when uplink is received.
Maybe you can also check in the time between uplink and rx1 whether a downlink comes in, because as I said, if there is already something in the queue, it works too.
You have to load the DownLink in the queue Before the UpLink, if you want to be sent at that exact received UpLink.
The server has to know that there is DownLink for sending on next received UpLink.
This is not an issue, this is the defined behaviour in the LoRaWAN documentation.
If you want the device to receive a DownLink generated after received UpLink, then the device should work in Class B or C, not A.
OK, I also noticed that the crucial time is the incoming uplink. I thought that would give you the RX1 time to send something to the queue.
I’ve adjusted my application accordingly so that it sends a message to Chirpstack earlier.
i think i’ve been doing exactly what you’re after - via NodeRed as integrated in the Gateway OS.
When the node sends the uplink, i put together the downlink and push it into the downlink queue.
When i was developing this, the downlink queue was “constantly empty” …
Checking today, i currently see a packet waiting - not what i intended.
Maybe something changed recently … i’ll have to investigate …