TheThingsArchive / ttn

The Things Network Stack V2
https://www.thethingsnetwork.org
MIT License
463 stars 276 forks source link

Remove scheduled downlink #697

Closed sukoy closed 6 years ago

sukoy commented 6 years ago

Hi!

There is a way to remove a scheduled downlink from queue? Our devices use OTAA and after reset cnt goes to 0, is there a way to remove previous scheduled downlink? to avoid twice received message.

Thanks

johanstokking commented 6 years ago

@sukoy atm there's no way to clear the queue, apart from replacing it with a new value. This will be added in V3.

sukoy commented 6 years ago

ok Thanks

haorfani commented 5 years ago

I am still having trouble with this issue. If I schedule a downlink message from an application, it is being sent every time I sent an uplink one. Is there a way to stop it, to be sent only once or being sent only if there is a specific payload.

johanstokking commented 5 years ago

@haorfani that should not happen. Are you sending confirmed downlink and is the downlink not confirmed by the end device, by chance? Because in that case it works as expected.

haorfani commented 5 years ago

By this you mean that the end device should send a ACK packet back to the GW right?

haorfani commented 5 years ago

OK I fixed it, it was my own bug after all. Thanks for the response though!

pradeeka7 commented 4 years ago

I have the same issue with my RAKwireless 7205 tracker. This happened from the second day. First day it worked well. I haven't yet restarted the tracker.

I'm sending UNCONFIRMED messages. I can't send confirmed messages because the latest firmware has a bug (I guess).

image

jpmeijers commented 4 years ago

Downlinks on port 0 are mac commands. Most likely what you are seeing is the ADR downlinks telling your device to go to a faster datarate and/or lower output power.