Shubham Patil

I tried on ESP32-DevKit-V4 with SHA e556daac2e1ed3a141034a6dcc7e410e4cd1f8f6 (branch:sve) and 608b143300dd46ab3948ade6dcdbb40aa4206cdb(branch:master), I was able to commission device without the above mentioned error. Can you please share the specific steps to recreate...

I copied the UserLabel implementation bits from `examples/providers/DeviceInfoProviderImpl.[cpp,h]` rather than extending it because it was in `examples/` directory. Any suggestion regarding reducing this code duplication?

I tried on 608b143300dd46ab3948ade6dcdbb40aa4206cdb with all-clusters-app and I was able to recommission the device again. Could you share the complete log capture?

Logs shows commissioning was successful > I (100760) chip[SVR]: Commissioning completed successfully and > I (100790) app-devicecallbacks: Commissioning complete Also, there were at least three type of actions were performed:...

@dhrishi tried with `examples/temperature-measurement-app/esp32` with manual code and commissioning completed with success. [temp-app-esp32.log](https://github.com/project-chip/connectedhomeip/files/9110631/temp-app-esp32.log) [chip-tool.log](https://github.com/project-chip/connectedhomeip/files/9110633/chip-tool.log)

@twlawrenceko are you looking for Matter support on ESP32 or RainMaker + Matter support on ESP32? We support Matter on ESP32 chips and you can try the [lighting app](https://github.com/project-chip/connectedhomeip/tree/master/examples/lighting-app/esp32) example...

@jonsmirl Agreed on the fixed attributes part, they has to be the part of code and OTA-able. Will see how this can be sorted.

I have raised a PR https://github.com/project-chip/connectedhomeip/pull/32893/files which adds few APIs to set that fixed data. In esp-matter, we'll hide the one level complexity through cluster::create() and take these strings as...

Hi @jonsmirl, here's how we can update the fixed type attributes in device info provider, https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/esp32/providers.md#example. I'm checking how this can be handled/consumed when creating the esp-matter data model.

AFAIK, the names you're seeing are not something you can change in the firmware. They are automatically assigned based on the device type present in the endpoint composition. So, if...