Skip to content

Conversation

@manup
Copy link
Contributor

@manup manup commented Dec 11, 2025

Firing all unicast requests with APS ACKs doesn't scale well. This PR makes a balance to send a failed requests again when the first one yields a APS confirm error.

This only raises the chance the request goes through within the timeout. Later on more logic needs to be added to enable APS ACKs for more requests while not clocking the queue with it. E.g if the queue is almost empty it's safe to use APS ACKs for N requests.

Firing all unicast requests with APS ACKs doesn't scale well. This PR makes a balance to send a failed requests again when the first one yields a APS confirm error.

This only raises the chance the request goes through within the timeout. Later on more logic needs to be added to enable APS ACKs for more requests while not clocking the queue with it. E.g if the queue is almost empty it's safe to use APS ACKs for N requests.
@Koenkk Koenkk merged commit aaddbc8 into Koenkk:master Dec 13, 2025
1 check passed
@Koenkk
Copy link
Owner

Koenkk commented Dec 13, 2025

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants