Skip to content
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

chip-tool commands time out and fail on sleepy end devices #22213

Closed
bluebin14 opened this issue Aug 27, 2022 · 0 comments · Fixed by #22269
Closed

chip-tool commands time out and fail on sleepy end devices #22213

bluebin14 opened this issue Aug 27, 2022 · 0 comments · Fixed by #22269
Assignees

Comments

@bluebin14
Copy link
Contributor

Problem

chip-tool commands time out and fail on slower devices such as SED. It happens randomly, sometimes there is only 1 second missing but it's enough to fail. Certain commands especially in administrator commissioning and operational credentials areas have more complexity and need more time to execute than just 10 seconds.

Proposed Solution

In ModelCommand.h change:

chip::System::Clock::Timeout GetWaitDuration() const override { return chip::System::Clock::Seconds16(mTimeout.ValueOr(10)); }

so it uses default timeout of 20.

bzbarsky-apple added a commit to bzbarsky-apple/connectedhomeip that referenced this issue Aug 30, 2022
10s is not enough for a typical CASE establishment plus command
execution on less-high-powered devices.

Fixes project-chip#22213
bzbarsky-apple added a commit that referenced this issue Aug 31, 2022
10s is not enough for a typical CASE establishment plus command
execution on less-high-powered devices.

Fixes #22213
isiu-apple pushed a commit to isiu-apple/connectedhomeip that referenced this issue Sep 16, 2022
…#22269)

10s is not enough for a typical CASE establishment plus command
execution on less-high-powered devices.

Fixes project-chip#22213
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants