Hello, everyone! I’m currently working on testing Matter OTA updates using the OTA provider. I followed the instructions from the nRF Connect examples, but I’m noticing that the OTA process is significantly slower than expected. I’m wondering if this is normal behavior or if there might be something I can adjust to improve the speed.
Looking at the logs, I see that there’s a lot of retransmission activity. For example, the provider logs show frequent messages like Msg Retransmission to 1:0000000000000002 scheduled for 3269ms from now. On the device side, similar retransmission messages are present. This makes me think that the communication between the provider and the device might be experiencing some delays or packet loss, leading to these repeated attempts.
I’ve also reviewed my configuration settings, and I’m curious if there’s anything in there that might be contributing to the slower speeds. For instance, I have CONFIG_OPENTHREAD_DEFAULT_TX_POWER=0 set, which I believe is the default transmit power. Could adjusting this value help improve the communication speed or reliability?
Another thing I’m considering is the impact of the network topology. I’m testing this in a controlled environment, but I’m not sure if there are any external factors, like interference or physical obstructions, that might be affecting the Thread network performance. Has anyone else encountered similar issues or found specific optimizations that made a difference?
I’m really interested in getting Matter to work smoothly for my project, so any insights or suggestions from the community would be greatly appreciated! Let’s see if we can troubleshoot this together and find a way to speed up the OTA process.