-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[ota] OTA requestor does not try another OTA provider when the current is down #22233
Comments
@tcarmelveilleux @carol-apple @selissia I'm not sure what's severity of this. IMHO it's not critical, but I would love to hear your opinions. |
This issue impacts the SU-2.8 Certification test. |
@Damian-Nordic I'd say this issue is a matter of choice, but if integrators "blindly" use the SDK version, without doing sufficient failure trials, they may not realize that they have a less effective strategy |
Thanks, test plan issue created: https://github.com/CHIP-Specifications/chip-test-plans/issues/2148, so I'll mark this as post 1.0. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Problem
https://github.com/project-chip/connectedhomeip/pull/16153/files has added the logic to re-try
QueryImage
in the case of timeout (which may be due to a lost CASE session), but there's no code to try another OTA Provider if the currently selected one is down or cannot be discovered at all 0. That is, OTA requestor will try another OTA Provider only after the query period (for example, 24 hours).The behavior seems to be allowed by the spec (see below), but I wonder if it's intuitive and user-friendly:
Proposed Solution
Pick another OTA provider on connection failure.
The text was updated successfully, but these errors were encountered: