From db93ce0ea4dc5f3756ce8083d8cd2561de6099e8 Mon Sep 17 00:00:00 2001 From: Boris Zbarsky Date: Wed, 31 Aug 2022 19:59:02 -0400 Subject: [PATCH] Increase the chip-tool timeout for data model commands. (#22269) 10s is not enough for a typical CASE establishment plus command execution on less-high-powered devices. Fixes https://github.com/project-chip/connectedhomeip/issues/22213 --- examples/chip-tool/commands/clusters/ModelCommand.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/chip-tool/commands/clusters/ModelCommand.h b/examples/chip-tool/commands/clusters/ModelCommand.h index fa77620f8812e0..3a20da0e182f7c 100644 --- a/examples/chip-tool/commands/clusters/ModelCommand.h +++ b/examples/chip-tool/commands/clusters/ModelCommand.h @@ -54,7 +54,7 @@ class ModelCommand : public CHIPCommand /////////// CHIPCommand Interface ///////// CHIP_ERROR RunCommand() override; - chip::System::Clock::Timeout GetWaitDuration() const override { return chip::System::Clock::Seconds16(mTimeout.ValueOr(10)); } + chip::System::Clock::Timeout GetWaitDuration() const override { return chip::System::Clock::Seconds16(mTimeout.ValueOr(20)); } virtual CHIP_ERROR SendCommand(chip::DeviceProxy * device, std::vector endPointIds) = 0;