我的matter程序是从example中的light复制过来修改的,能正常的进行配对和调试,但是监控错误信息时,发现有一个错误提示:
错误1:
chip [DMG] Endpoint 0 , Cluster 0x0000_0031 not found in IncreasecluscerDataversion!
请问这是什么问题呢,应该如何处理呢?
我用有启用这个集群,Network Commissioning这个集群.
错误2:
chip[sc]: The device does nossupport GetClock RealTimeMS() API: 6cEalling back to last Known cood Urc Time
请问这个错误应该怎么禁用呢,我们不需要去获取UTC时间
ESP32H2 Matter 回报的一些错误
ESP32H2 Matter 回报的一些错误
- Attachments
-
- 1730427308184.png (541.07 KiB) Viewed 575 times
-
- 1730427293068.png (1015.56 KiB) Viewed 575 times
Re: ESP32H2 Matter 回报的一些错误
问题2:这个并不是ESP32的问题,而已matter协议在进行CASE认证时需要的。
Code: Select all
CHIP_ERROR CASESession::SetEffectiveTime()
{
System::Clock::Milliseconds64 currentUnixTimeMS;
CHIP_ERROR err = System::SystemClock().GetClock_RealTimeMS(currentUnixTimeMS);
if (err == CHIP_NO_ERROR)
{
// If the system has given us a wall clock time, we must use it or
// fail. Conversion failures here are therefore always an error.
System::Clock::Seconds32 currentUnixTime = std::chrono::duration_cast<System::Clock::Seconds32>(currentUnixTimeMS);
ReturnErrorOnFailure(mValidContext.SetEffectiveTimeFromUnixTime<CurrentChipEpochTime>(currentUnixTime));
}
else
{
// If we don't have wall clock time, the spec dictates that we should
// fall back to Last Known Good Time. Ultimately, the calling application's
// validity policy will determine whether this is permissible.
System::Clock::Seconds32 lastKnownGoodChipEpochTime;
ChipLogError(SecureChannel,
"The device does not support GetClock_RealTimeMS() API: %" CHIP_ERROR_FORMAT
". Falling back to Last Known Good UTC Time",
err.Format());
VerifyOrReturnError(mFabricsTable != nullptr, CHIP_ERROR_INCORRECT_STATE);
err = mFabricsTable->GetLastKnownGoodChipEpochTime(lastKnownGoodChipEpochTime);
if (err != CHIP_NO_ERROR)
{
// If we have no time available, the Validity Policy will
// determine what to do.
ChipLogError(SecureChannel, "Failed to retrieve Last Known Good UTC Time");
}
else
{
mValidContext.SetEffectiveTime<LastKnownGoodChipEpochTime>(lastKnownGoodChipEpochTime);
}
}
return CHIP_NO_ERROR;
}
Re: ESP32H2 Matter 回报的一些错误
谢谢你的帮助。
请问第一个问题你有什么思路吗?
请问第一个问题你有什么思路吗?
Re: ESP32H2 Matter 回报的一些错误
问题一:
我没有遇到这个问题,按照我的理解,应该是这个自定义Cluster 0x0000_0031, 它没有在 网关/配网者 中实现导致。
在github有相关的问题可以看看。
[ESP32 bridge-app] Endpoint 0 not found in IncreaseClusterDataVersion
我没有遇到这个问题,按照我的理解,应该是这个自定义Cluster 0x0000_0031, 它没有在 网关/配网者 中实现导致。
在github有相关的问题可以看看。
[ESP32 bridge-app] Endpoint 0 not found in IncreaseClusterDataVersion
Who is online
Users browsing this forum: No registered users and 189 guests