-
Notifications
You must be signed in to change notification settings - Fork 174
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
Energy Management Application (CON-1299) #1048
Comments
Try
Please share what you have done, in detailed steps. and which device type are you building using zap-light? |
Yeah, But for some reason, the fields are greyed out (as in unable to edit) as you see in the below image.
|
It looks like it's an error with connectedhomeip SDK. |
@jadhavrohit924 - For the zap? |
No for the For zap, can you please share with me which attributes you are trying to update? |
@svn-matterize Can you please provide the requested information |
@svn-matterize This can be the issue with the zap-tool. I failed you open your .zap on release/v1.3 branch in the zap-tool as there is some problem with your zap. Can you please tell me which zap-tool you are using I mean the connectedhomeip commit id and the zap release. Does all the attributes of |
I am using Issue |
@svn-matterize Thanks for the detailed explanation. If you see the storage type for these attributes is |
Is it the case for all |
Yes. External means it is configured externally. |
Gotcha, let me give it a try and let you know. |
Alright. This worked. However, in a meantime, I've leveraged something without the help of the .zap implementation. On that when I try to write to ElectricalEnergyMeasurement::Structs::MeasurementAccuracyRangeStruct::Type energyAccuracyRanges[] = {
{ .rangeMin = 0,
.rangeMax = 1'000'000'000'000'000, // 1 million Mwh
.percentMax = chip::MakeOptional(static_cast<chip::Percent100ths>(500)),
.percentMin = chip::MakeOptional(static_cast<chip::Percent100ths>(50)) }
};
ElectricalEnergyMeasurement::Structs::MeasurementAccuracyStruct::Type accuracy = {
.measurementType = chip::app::Clusters::detail::MeasurementTypeEnum::kElectricalEnergy,
.measured = true,
.minMeasuredValue = 0,
.maxMeasuredValue = 1'000'000'000'000'000, // 1 million Mwh
.accuracyRanges = chip::app::DataModel::List<
const ElectricalEnergyMeasurement::Structs::MeasurementAccuracyRangeStruct::Type>(
energyAccuracyRanges)
};
arr_val = esp_matter_array((uint8_t *)&accuracy, sizeof(arr_val), 1);
err = attribute::set_val(attribute, &arr_val);
if (err != ESP_OK) {
ESP_LOGE(TAG, "Updated EnergyAccuracy failed");
} It gets success in writing, however when reading the same from the [1725372167.731751][7535:7537] CHIP:DMG: Endpoint = 0x1,
[1725372167.732217][7535:7537] CHIP:DMG: Cluster = 0x91,
[1725372167.732742][7535:7537] CHIP:DMG: Attribute = 0x0000_0000,
[1725372167.733015][7535:7537] CHIP:DMG: }
[1725372167.733128][7535:7537] CHIP:DMG:
[1725372167.733303][7535:7537] CHIP:DMG: StatusIB =
[1725372167.733342][7535:7537] CHIP:DMG: {
[1725372167.733367][7535:7537] CHIP:DMG: status = 0x89 (RESOURCE_EXHAUSTED),
[1725372167.733502][7535:7537] CHIP:DMG: }, Is there something not right in writing to the attributes? If you want me to open this as a separate issue, I'm happy to. |
@svn-matterize Please open a separate issue with all the code that you have added, I mean your delegate implementation. Also, add device and chip-tool logs in separate files to analyze. Please close this issue as your original problem is resolved. |
Okay, I have created as a new issue refer |
Hi,
I would like to put together an application which measure the power consumption and provide the forecast with the previous data.
I've started with light and mostly assembled the pieces.
For convenience, I wanted to work zap, so tried with zap_light and unable to write to the attributes (fields are greyed out) and reading the attribute from the
chip-tool
lead to failure even when it's enabled.What might be the issue?
The text was updated successfully, but these errors were encountered: