Feature Discussion #9 (git-14750) - Expose CoAP ACK_TIMEOUT and MAX_RETRANSMIT for High-Latency Networks #14904
Replies: 1 comment
-
|
Thank you for opening this discussion. I need to stress that for anyone using Cellular IoT (LTE-M or NB-IoT), this is not a "nice-to-have" feature—it is a mandatory requirement to make the CoAP transport usable at all. The Physics of the Problem: The current hardcoded default in the Monolith (ACK_TIMEOUT = 2000ms) is physically incompatible with cellular network standards in real-world conditions: LTE-M: In scenarios with weak signal or cell-edge conditions, Round Trip Times (RTT) frequently reach 3-5 seconds. NB-IoT: This is critical. NB-IoT uses "Coverage Enhancement" (ECL levels). In ECL1 or ECL2 (deep indoor/basement), the transmission time for a single packet can physically take 10 to 20 seconds due to standard-defined repetitions. The Consequence: With the current hardcoded 2-second timeout: -ThingsBoard sends a request. -ThingsBoard guarantees a timeout failure after 2 seconds. -The device actually receives the message 5 seconds later and processes it. -The device sends an ACK. -ThingsBoard has already closed the context and ignores the ACK. Result: 100% Error rate and unnecessary retransmissions that drain the battery, despite the device working perfectly. Why this forces us to bypass ThingsBoard: If this parameter remains unconfigurable in the Monolith, the native ThingsBoard CoAP Transport is effectively broken for the entire Cellular IoT sector. We are currently forced to consider building a custom CoAP Proxy in front of ThingsBoard just to handle the timeouts correctly. This defeats the purpose of using ThingsBoard's native transport layer. Parity Issue: Please note that Microservice users can already configure this via tb-coap-transport.conf. We are simply asking for the same capability in the Monolith (thingsboard.yml) to make the platform viable for professional Cellular IoT deployments. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Thingsboard Community, We've created a new Idea discussion for the previously suggested feature from GitHub issue #14750. Please vote on whether to add this feature so we can understand the community's reaction to this improvement. Even if the feature request is rejected, this information will still be useful for further planning the platform's development, and the decision may be reconsidered in the future.
Beta Was this translation helpful? Give feedback.
All reactions