-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pre-sve] NotifyUpdateApplied fails if triggered before the node joins the fabric #19192
Comments
I think it'd be tricky to figure out how long to delay. There are no timestamps in your log snippet. How long between the first failed |
Several seconds, I don't have a more specific info than that. But this will vary between devices and network conditions anyway. |
Hi! I'm seeing this after trying to increase OT baud rate to 921600. Seems like the call to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale issue has been automatically closed. Thank you for your contributions. |
Hi all, I think I am seeing this problem here, I found another issue that is related but my code has already implemented that change Is there any further update for the OTA state machine for this? |
Problem
When a node reboots after a successful OTA update the sending NotifyUpdateApplied might get triggered before the Node re-joins the fabric. In this case the command fails to be transmitted. This fails the TC-SU-2.6 test case
For example, in case of Thread transport re-joining the Thread network takes some time, see attached log snippet.
Proposed Solution
OTARequestor class should delay sending NotifyUpdateApplied until the device has joined the fabric.
The text was updated successfully, but these errors were encountered: