Hardware Version Not Updating from sdkconfig After Enabling Custom DAC

[mohankumar2000]

• When using Test DAC and Test Vendor ID, the hardware version updates correctly from sdkconfig (CONFIG_DEFAULT_DEVICE_HARDWARE_VERSION=1).
• After enabling the custom vendor DAC, the hardware version and hardware version string is not updated from sdkconfig, and the configured value is not reflected in the device and tested with chiptool.

SDK changes did for custom DAC:

#CONFIG_ENABLE_TEST_SETUP_PARAMS is not set
#CONFIG_EXAMPLE_DAC_PROVIDER is not set
#CONFIG_CUSTOM_DAC_PROVIDER is not set
#CONFIG_EXAMPLE_COMMISSIONABLE_DATA_PROVIDER is not set
#CONFIG_CUSTOM_COMMISSIONABLE_DATA_PROVIDER is not set
#CONFIG_EXAMPLE_DEVICE_INSTANCE_INFO_PROVIDER is not set
#CONFIG_CUSTOM_DEVICE_INSTANCE_INFO_PROVIDER is not set
#CONFIG_NONE_DEVICE_INFO_PROVIDER is not set
#CONFIG_CUSTOM_DEVICE_INFO_PROVIDER is not set

CONFIG_ENABLE_ESP32_FACTORY_DATA_PROVIDER=y
CONFIG_ENABLE_ESP32_DEVICE_INSTANCE_INFO_PROVIDER=y
CONFIG_ENABLE_ESP32_DEVICE_INFO_PROVIDER=y
CONFIG_FACTORY_PARTITION_DAC_PROVIDER=y
CONFIG_FACTORY_COMMISSIONABLE_DATA_PROVIDER=y
CONFIG_FACTORY_DEVICE_INSTANCE_INFO_PROVIDER=y

Build Details:

ESP-Matter SDK: release/v1.4.2
ESD-IDF version: v5.4.1
SoC: ESP32-S3
MTH Version: v2.13+summer2025

[shubhamdp]

This is expected behavior when using the factory data provider.

When you enable CONFIG_FACTORY_DEVICE_INSTANCE_INFO_PROVIDER, the device instance info (including hardware version) is read from the factory NVS partition, not from sdkconfig.

Since you've programmed your factory partition with manufacturing data, I'd suggest you to include hardware version and hardware version string in them.

Set the hardware version when generating your factory partition using the manufacturing tool:

esp-matter-mfg-tool ... --hw-ver 1 --hw-ver-str "v1.0"

references:

• Factory Data Providers
• Using esp_secure_cert partition (shows the --hw-ver and --hw-ver-str parameters)

[mohankumar2000]

Thanks @shubhamdp for your support.

As we are planning to use pre-provisioned modules from Espressif with factory data (DAC) already programmed.

May be during field trials or later product revisions, if there is a hardware/board update requires change in hardware version also.

• Is it possible to update hw-ver and hw-ver-str in already provisioned modules?
• Can the factory NVS partition be updated safely in production or field conditions?
• Or previously provisioned modules are unusable?

We would like to understand the recommended approach for handling hardware version updates in such scenarios.

[mohankumar2000]

Hi @shubhamdp,

Can you please us to proceed further?

[shubhamdp]

Is it possible to update hw-ver and hw-ver-str in already provisioned modules?

Yes it is, they are just interfaces and we have implemented it in a way that it reads from the factory partition, if going ahead you bump the hw-version and use the same module, then I guess you will either have to bake that in the firmware or write some code which updates these values in the fctry partition.

Can the factory NVS partition be updated safely in production or field conditions?

Yes, but I'd suggest against that since it's treated as read-only and shall be only updated when it's really required, btw it's safe.

Or previously provisioned modules are unusable?

They will be usable even with/without hardware version being present in them.

--
The hardware version is read through the DeviceInstanceInfoProvider interface, and we have a default implementation which reads it from the NVS partition. (ref: https://github.com/project-chip/connectedhomeip/blob/master/src/platform/ESP32/ESP32FactoryDataProvider.cpp#L208)

But, it is overridable, you can extend ESP32's default impl and implement the APIs that you'd like the custom behaviour, eg: in this case you want to read the values through kconfig's then you return those values from there.

Then before calling esp_matter::start() you create an object of that class and register the custom device instance info provider with esp-matter core layer.

You can find the relevant documentation below:

• https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html#factory-data-providers
• https://docs.espressif.com/projects/esp-matter/en/latest/esp32/developing.html#custom-providers
• https://github.com/project-chip/connectedhomeip/blob/master/docs/platforms/esp32/providers.md

[mohankumar2000]

@shubhamdp Thanks for your support. Will reopen if any clarification requires in future.